Backend exiting unexpectedly

[VeloWulf]

Recently the OTR has started reporting "+ HTTP port is in use. Exiting." and the container is terminating. I am at a bit of a loss on what to do to resolve. I have tried changing the local port but the error persists (and nothing has been added to the environment that uses that port that I am aware of). The complete log looks like:

2025/11/11 09:30:44 | stdout | + HTTP port is in use. Exiting.
2025/11/11 09:30:44 | stdout | + HTTP listener started on , with browser-apikey
2025/11/11 09:30:44 | stdout | + connecting to MQTT on XXX.XX.XX.XX:1883 as clientID ot-recorder-owntracks-recorder-7 without TLS
2025/11/11 09:30:41 | stdout | + version 1.0.1 starting with STORAGEDIR=/store

Any help appreciated

[VeloWulf]

Update: Running identical config on a different docker server returns the same result. Adding

OTR_HTTPHOST="0.0.0.0"
OTR_HTTPPORT=8083

to the config file (0.0.0.0 is not a mask for privacy - that is what I used) results in the recorder operating. The new log entries are:

2025/11/11 10:09:08 | stdout | + HTTP prefix is unset
2025/11/11 10:09:08 | stdout | + HTTP listener started on 0.0.0.0:8083, with browser-apikey

The tracks do not appear on the frontend server so I am assuming that something remains problematic

[jpmens]

You write

Recently the OTR has started reporting ...

which makes me think it worked for you before, so you'll have to see what changed. We've not uploaded a new version for some time now.

Might I suggest you downgrade to a previous version to see where the issue arises?