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?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $200 of credit to try our products over 60 days!