Open BHMath opened 10 months ago
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Actually, with the latest version it seems to be working now.
I'm seeing this issue with Caddy and another lsio container (Kavita). It seems to wait about 10 seconds, then the container is stopped and restarted in a loop.
I have the same problem with Sablier 1.7. It was working with Traefik, but not with Caddy. Is there anything I can do to help track this down @acouvreur ?
If you encounter this issue with your setup, can you please share your setups specifics ?
How is Caddy configured ?
For every reverse-proxy using auto-discovery (discovering containers via the socket API) we might have a different latency.
It's possible that Sablier detects a worklaod as ready before the reverse-proxy itself created the route.
One option to mitigate that could be to configure an extra waiting time once the workload is ready on Sablier.
E.g.:
provider:
extra-waiting-duration: 5s
...
This means that once the workload is ready, you'll still wait 5s to make sure all other components properly register the workload startup event.
I think this should stabilize the responses a lot.
What do you think ?
Describe the bug When I configure the blocking strategy, my prowlarr container starts and then stop immediately while when dynamic strategy is configured, the container starts well and the login page appears.
Context
Expected behavior When blocking strategy is set I want my container to starts fully and reach login page when possible
Additional context Here the logs
Prowlarr logs when Blocking Strategy (it fails to start)
Sablier logs:
Router configuration
Traefik plugin blocking configuration per label
Prowlarr logs when Dynamic Strategy (it works to start)
Sablier logs:
Router configuration
Traefik plugin dynamic configuration per label