How do I gracefully reboot with a reverse proxy?

March 30, 2017 287 views
Nginx Ghost Ubuntu

I've got a droplet currently running my website (a Ghost blog) behind an NGINX reverse proxy that handles all the HTTPS redirects, etc. etc.

It's all working really well (thanks to the tutorials and answer writers on here), but my one gripe is that when I run updates and reboot the box, NGINX kicks in before Ghost loads up, meaning that anyone who happens to load my site in that 5-10 second interval gets a nice big 502 Bad Gateway error.

Is there any way to make this work a little more gracefully, so that users that open the site at that point just get put on hold for a few seconds rather than immediately getting booted to the error page and having to refresh?

2 Answers

I have created a spinner for a customer (loading animation) and then the site refreshes every 5 seconds. But I don't have access to their platform right now, so I'll give you a link to a pretty good example in the first answer:


The issue here is the delay with Ghost. There's really no way to preload Ghost so that it comes up at the same time as NGINX as Ghost relies on npm to do its thing before starting up.

If you start Ghost first, there's no web server to handle the requests during the delay and the only way to access Ghost would be using a port, if you've set it to work on a public IP -- you'd still be getting an error since requests on port 80 will fail.

If you start NGINX first, then you're waiting on Ghost, thus since NGINX can't access Ghost right now, you get the 502 since NGINX can't proxy.

Have another answer? Share your knowledge.