HTTP 301 after restarting proxied service

[warnspread]

Describe the bug
tsdproxy is running with the latest version.

A new service is deployed, i authenticate it and it's correctly working.

The new service (docker-compose) needs an adjustement, is edited and restarted (tsdproxy settings stay the same)

After that it's not possible anymore to visit the service, the log and curl show HTTP Code 301. It's working again when tsdproxy is restarted.

Expected behavior
The service should be available even if it's restarted

Send config
No config touched, just labels, for example:
labels:
tsdproxy.enable: "true"
tsdproxy.name: "heimdall"
tsdproxy.port: "80"
tsdproxy.ephemeral: "false"

Logs
This is repeating 10 times for each request:
7:47AM INF request host=heimdall.my-awesome.ts.net method=GET module=proxymanager proxyname=heimdall status=301 url=/settings/edit/2
7:47AM INF request host=heimdall.my-awesome.ts.net method=GET module=proxymanager proxyname=heimdall status=301 url=/settings/edit/2

curl when it's broken:
curl -I https://heimdall.my-awesome.ts.net/
HTTP/1.1 301 Moved Permanently
Content-Length: 162
Content-Type: text/html
Date: Sat, 05 Jul 2025 07:52:27 GMT
Location: https://heimdall.my-awesome.ts.net/
Server: nginx

curl when tsdproxy was restarted and it's working again:
curl -I https://heimdall.my-awesome.ts.net/
HTTP/1.1 200 OK
Cache-Control: no-cache, private
Content-Type: text/html; charset=UTF-8
Date: Sat, 05 Jul 2025 07:53:36 GMT
Server: nginx
Set-Cookie: XSRF-TOKEN=SOMETOKEN; expires=Sat, 05 Jul 2025 09:53:36 GMT; Max-Age=7200; path=/; secure
Set-Cookie: heimdall_session=SOMESESSION; expires=Sat, 05 Jul 2025 09:53:36 GMT; Max-Age=7200; path=/; httponly
X-Powered-By: PHP/8.3.15