seven1m/onebody

Fix "502 Bad Gateway" message from nginx

seven1m opened this issue · 2 comments

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.

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

😞

I cannot find a solution for this. Closing.