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
When starting another container that uses nginx-proxy and nginx-letsencrypt, for about 20-30 seconds while either the container starts or nginx-proxy generates the config, users see a error 500 page. This can be alarming to end users and doesn't look very professional.
Is there a way to prevent this from happening, or is there a way to override this? I've tried adding a custom error 500 but since the error itself is within nginx-proxy while either generating configs or when contacting the upstream, I can't find a way to override this or prevent it.
Any help is much appreciated. Thank you.
EDIT: I'm aware I could fiddle with nginx.tmpl but having to re-apply this change every time this file is updated in the repository is extremely cumbersome.
Info: running acme-companion version v2.2.10-13-gb22b6ef
Hi, this was fixed in #1157 : acme-companion no longer generate a default certificate for nginx-proxy, which mean you should no longer get the 500 error if you remove default.crt and default.key from /etc/nginx/certs and use the latest tag of acme-companion (a new version with the fix will be released soon).
Bug description
When starting another container that uses
nginx-proxy
andnginx-letsencrypt
, for about 20-30 seconds while either the container starts ornginx-proxy
generates the config, users see a error500
page. This can be alarming to end users and doesn't look very professional.Is there a way to prevent this from happening, or is there a way to override this? I've tried adding a custom error
500
but since the error itself is withinnginx-proxy
while either generating configs or when contacting the upstream, I can't find a way to override this or prevent it.Any help is much appreciated. Thank you.
EDIT: I'm aware I could fiddle with
nginx.tmpl
but having to re-apply this change every time this file is updated in the repository is extremely cumbersome.nginx-proxy's Docker configuration
docker-compose.yml
error_pages.conf
nginx-custom.conf
Docker host
The text was updated successfully, but these errors were encountered: