You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using nginx-proxy and nginx-proxy-acme (along with other services). All services run at startup except for nginx-proxy-acme. To get it running I need to manually run docker compose up on my server (Debian 11). It then runs fine and renews my certs, however 3 months later it becomes an issue again as the certs expire because the service never runs.
Is this the default behaviour? I can't find anything in the docs to explain why it does not run at startup.
I am using nginx-proxy and nginx-proxy-acme (along with other services). All services run at startup except for nginx-proxy-acme. To get it running I need to manually run docker compose up on my server (Debian 11). It then runs fine and renews my certs, however 3 months later it becomes an issue again as the certs expire because the service never runs.
Is this the default behaviour? I can't find anything in the docs to explain why it does not run at startup.
Below is my compose file:
Container logs once manually started:
The text was updated successfully, but these errors were encountered: