-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 500 On Service Start #2419
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: