Question

CentOs reboot killed Web2py site.

I powered down our CentOS droplet for backup/snapshot. When I powered it back on the Web2py site did not come back up. We just get a 502 Bad Gateway nginx response. Nothing changed in the configuration or files that we are aware of prior to the shutdown. I have gone through the https://www.digitalocean.com/community/tutorials/how-to-deploy-web2py-python-applications-with-uwsgi-and-nginx-on-centos-7 and verified that everything is still setup as shown, but still no joy. Web2py is running as expected. (I’m currently hosting the site for our client on port 8000 via Web2py) The uWSGI per the instructions is hosting the http test as expected. I’m not seeing any errors that are helping me at this moment. But I think I’ve gone over this to many times to see this objectively and am asking for any guidance/help.


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

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.

Rebuilt site on new droplet using Ubuntu 20.04.

Hello,

I could suggest checking your Nginx error log so that you could see the actual error rather than the generic 502 error:

tail -100 /var/log/nginx/error.log

If you get a file not found when running the above, you would need to check the exact location of your error log by running:

grep -r error /etc/nginx/*

Feel free to share the output of the error log here.

Also, it would help if you could share the Nginx reverse proxy rule that you have in place.

Best,

Bobby