Komoot/Manual .gpx upload not working

[Lorondos]

What happened?

Hey there, I have two issues that have pretty much persisted for a few versions and was hoping the latest would fix it, both relate to getting completed trails uploaded from Komoot, via the integration or a manual upload of the .gpx file, both fail for me at the moment.

I did manage to get the 3 latest of my trails uploaded via the Komoot integration but after that, no more uploads and everytime I try to change a komoot setting on the integration, it errors out.

The error occurs on every setting I change, tried updating the login details but still continously produces this error no matter what.

The second issue is a manual upload of the Komoot .gpx instead:

May 11 01:56:51 wanderer bash[362]: at file:///opt/wanderer/source/web/build/server/chunks/gpx-MEoo5tio.js:569:13
May 11 01:56:51 wanderer bash[362]: at Parser. (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:308:18)
May 11 01:56:51 wanderer bash[362]: at Parser.emit (node:events:519:28)
May 11 01:56:51 wanderer bash[362]: at SAXParser.onerror (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:123:26)
May 11 01:56:51 wanderer bash[362]: at emit (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:745:35)
May 11 01:56:51 wanderer bash[362]: at error (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:831:5)
May 11 01:56:51 wanderer bash[362]: at strictFail (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:858:7)
May 11 01:56:51 wanderer bash[362]: at SAXParser.write (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:1771:13)
May 11 01:56:51 wanderer bash[362]: at exports.Parser.Parser.parseString (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:323:31)
May 11 01:56:51 wanderer bash[362]: at Parser.parseString (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:5:59)
May 11 01:56:54 wanderer bash[362]: TypeError: Cannot read properties of undefined (reading 'gpx')
May 11 01:56:54 wanderer bash[362]: at file:///opt/wanderer/source/web/build/server/chunks/gpx-MEoo5tio.js:569:13
May 11 01:56:54 wanderer bash[362]: at Parser. (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:308:18)
May 11 01:56:54 wanderer bash[362]: at Parser.emit (node:events:519:28)
May 11 01:56:54 wanderer bash[362]: at SAXParser.onerror (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:123:26)
May 11 01:56:54 wanderer bash[362]: at emit (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:745:35)
May 11 01:56:54 wanderer bash[362]: at error (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:831:5)
May 11 01:56:54 wanderer bash[362]: at strictFail (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:858:7)
May 11 01:56:54 wanderer bash[362]: at SAXParser.write (/opt/wanderer/source/web/node_modules/sax/lib/sax.js:1771:13)
May 11 01:56:54 wanderer bash[362]: at exports.Parser.Parser.parseString (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:323:31)
May 11 01:56:54 wanderer bash[362]: at Parser.parseString (/opt/wanderer/source/web/node_modules/xml2js/lib/parser.js:5:59)
lines 38-100/100 (END)

I might attempt a fix if I have the time and can locate the root cause but maybe a fresh install might be an option at this point but if you have any ideas in the mean time, that would be much apperciated, thanks!

Version

0.19.0

[slothful-vassal]

Hi,

sorry to hear you’re having trouble with the komoot integration.

Could you please provide a sample GPX file so we can reproduce the issue?

Many thanks.

[Lorondos]

gpx example.zip

Thanks for getting back to me, attached the .gpx file, had to zip it, the good news is, the Komoot upload is working, it has now gone beyond 3 completed Komoot hikes and now has my history back as far as 2022, still missing a few more so will see what happens overnight etc, erroring everytime I try to change a setting on the integation for Komoot still though for some reason.

[Flomp]

Thanks for the GPX. I cannot reproduce the upload locally or on demo.wanderer.to. Both uploads go through without issues and the trail is displayed.

Are there any other steps we need to take to reproduce the issue? Otherwise, this is most likely a problem with your specific setup.

[Lorondos]

Thanks for checking, yeah, I suspected as much, seeing as nobody else has reported it, it was installed via proxmox helper scripts: https://community-scripts.org/scripts/wanderer?id=wanderer&category=Gaming%20%26%20Leisure, when I get around to the weekend, I might have a poke if I can find anything obvious.

[Lorondos]

So I have attempted a fresh install and not sure why this particular package ends up as missing, will see if I can resolve it manually and confirm if the issue still persists, included some detail on my Proxmox setup.

💡 PVE Version 9.1.9 (Kernel: 7.0.0-3-pve)
🆔 Container ID: 119
🖥️ Operating System: debian (13)
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 4096 MiB
🚀 Creating a Wanderer LXC using the above default settings

✔️ Storage local (Free: 116.5GB Used: 93.8GB) [Template]
✔️ Storage data-2 (Free: 3.3TB Used: 359.8GB) [Container]
✔️ Storage 'data-2' (lvmthin) validated
✔️ Template storage 'local' validated
✔️ Template search completed
✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local]

--- Last 20 lines of log ---
│
5 │ import openapiPlugin from 'sveltekit-openapi-generator';
│ ──────────────┬──────────────
│ ╰──────────────── Module not found, treating it as an external dependency
───╯

failed to load config from /opt/wanderer/source/web/vite.config.ts
error during build:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@sveltejs/enhanced-img' imported from /opt/wanderer/source/web/node_modules/.vite-temp/vite.config.ts.timestamp-1778953763180-d82ca0eb09425.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
at packageResolve (node:internal/modules/esm/resolve:768:81)
at moduleResolve (node:internal/modules/esm/resolve:855:18)
at defaultResolve (node:internal/modules/esm/resolve:985:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
code: 'ERR_MODULE_NOT_FOUND'
}
[2026-05-16 18:49:23] [ERROR] in line 29: exit code 1 (General error / Operation not permitted): while executing command npm run build

✖️ Installation failed in container 119 (exit code: 1)

Maybe an issue within the proxmox helper script, not dug into it, I have kept the container for debugging, will see if I can resolve the issue or if it runs okay.

[Lorondos]

The issue above, looks like its due to the proxmox helper script having omit-dev as part of its ci command, will run a modified build script without it and see what happens.

[Lorondos]

Raised the issue here on the proxmox helper script side: community-scripts/ProxmoxVE#14525 in the meantime.

[Lorondos]

community-scripts/ProxmoxVE#14525 was fixed, Thanks @MickLesk 🙂

[Lorondos]

So managed to get another wanderer install up and running, all fresh, made an account, exact same issue with manual uploads:

The Komoot intergration however, appears to be working without erroring now. I will see if it picks up trails and see if I can get anything from the logs.