Skip to content
This repository has been archived by the owner on Mar 27, 2022. It is now read-only.

Fix "502 Bad Gateway" message from nginx #663

Closed
seven1m opened this issue Apr 8, 2017 · 2 comments
Closed

Fix "502 Bad Gateway" message from nginx #663

seven1m opened this issue Apr 8, 2017 · 2 comments

Comments

@seven1m
Copy link
Owner

seven1m commented Apr 8, 2017

When OneBody is restarted, nginx by default will return "502 Bad Gateway" to the user while the backend process is coming back online. I think there must be a setting in nginx to make it wait for the backend service to come online.

@seven1m
Copy link
Owner Author

seven1m commented Apr 8, 2017

This makes me think the built-in proxy_pass in nginx can't do it:

http://serverfault.com/questions/259665/nginx-proxy-retry-while-backend-is-restarting

😞

@seven1m
Copy link
Owner Author

seven1m commented Aug 19, 2017

I cannot find a solution for this. Closing.

@seven1m seven1m closed this as completed Aug 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants
@seven1m and others