Update further than version 0.4.3 breaks teddycloud

Hello there,

first of all I would to thank you all for this awesome piece of software which gives me the possiblility to manage the Toniebox of my kids locally and in a very flexible way. Thank you!

Sadly I’ve discovered issues due updating my teddycloud docker container from 0.3.5 to the latest version 0.5.2.
After the update the container stucks after reading the certificates.

Is there any further logfile where I can find details about the “crash”?

So I tried to figure out at which point the problems starts and pull version after version.
The first problems occur from V0.4.3 to V0.4.4 that the WebUI responds with 404 , because the Callback seems to be missing:
teddycloud | WARN |server_helpers.c:0792:httpServerUriNotFoundCallback| >> 404 /api/stats

More Details:

teddycloud    | TeddyCloud v0.4.4 (0f57f75) - 2024-04-09 05:16:38 +0000 linux-x86_64
teddycloud    | 
teddycloud    | INFO |settings.c:0700:settings_load_ovl| Load settings from /teddycloud/config/config.overlay.ini
teddycloud    | INFO |tls_adapter.c:0208:read_certificate| File '/teddycloud/certs/server/ca-root.pem' assumed PEM style
teddycloud    | INFO |tls_adapter.c:0205:read_certificate| File '/teddycloud/certs/server/ca-key.pem' detected as DER style RSA PRIVATE KEY
teddycloud    | INFO |tls_adapter.c:0208:read_certificate| File '/teddycloud/certs/server/teddy-cert.pem' assumed PEM style
teddycloud    | INFO |tls_adapter.c:0205:read_certificate| File '/teddycloud/certs/server/teddy-key.pem' detected as DER style RSA PRIVATE KEY
teddycloud    | INFO |tls_adapter.c:0201:read_certificate| File '/teddycloud/certs/client/ca.der' detected as DER style CERTIFICATE
teddycloud    | INFO |tls_adapter.c:0201:read_certificate| File '/teddycloud/certs/client/client.der' detected as DER style CERTIFICATE
teddycloud    | INFO |tls_adapter.c:0205:read_certificate| File '/teddycloud/certs/client/private.der' detected as DER style RSA PRIVATE KEY
teddycloud    | INFO |settings.c:0700:settings_load_ovl| Load settings from /teddycloud/config/config.ini
...
teddycloud    | INFO |cloud_request.c:0311:web_request| HTTP code: 302
teddycloud    | INFO |cloud_request.c:0324:web_request| Redirecting to: https://raw.githubusercontent.com/toniebox-reverse-engineering/tonies-json/release/tonies.json
teddycloud    | INFO |cloud_request.c:0161:web_request| Connecting to HTTP server raw.githubusercontent.com:443...
teddycloud    | INFO |cloud_request.c:0211:web_request|   trying IP: 185.199.110.133
teddycloud    | INFO |cloud_request.c:0038:httpClientTlsInitCallbackBase| Initializing TLS...
teddycloud    | INFO |cloud_request.c:0073:httpClientTlsInitCallbackBase| Initializing TLS done
teddycloud    | INFO |cloud_request.c:0311:web_request| HTTP code: 200
teddycloud    | INFO |cloud_request.c:0374:web_request| Content-Type is text/plain; charset=utf-8
teddycloud    | WARN |server_helpers.c:0792:httpServerUriNotFoundCallback|  >> 404 /api/stats
teddycloud    | INFO |cloud_request.c:0452:web_request| Connection closed
teddycloud    | INFO |toniesJson.c:0118:tonies_update| ... success updating tonies.json from api.revvox.de, reloading
teddycloud    | INFO |toniesJson.c:0196:tonies_readJson| Trying to read /teddycloud/config/tonies.custom.json with size 2
teddycloud    | INFO |toniesJson.c:0196:tonies_readJson| Trying to read /teddycloud/config/tonies.json with size 4846542
teddycloud    | INFO |server.c:0612:server_init| 1 open HTTPS connections
teddycloud    | WARN |server_helpers.c:0792:httpServerUriNotFoundCallback|  >> 404 /api/stats
teddycloud    | WARN |server_helpers.c:0792:httpServerUriNotFoundCallback|  >> 404 index.shtm

Did I miss anything e.g. breaking changes or manual settings?
Also the V0.4.3 shows only the old WebUI and not the nice new one, maybe something is broken in general. (in my setup)

Could you give me any hint where I can search for the root cause?

Setup: teddycloud operates inside of Proxmox as Docker Container on a Intel NUC with Debian 12

Any help will be appreciated.
Thanks in advance.

Phoeniix

are you using https to access the pages?

Access is restricted to http by default since 0.4.4

oh, ok. I’ve missed that…how it seems. My bad.

After enableing of the http port the application works with version 0.5.2.

Thanks a lot for the hint!