Error 502 after creating a new droplet

Posted February 21, 2019 1.1k views
DebianConfiguration ManagementDeployment

Hi! I’m created new droplet via snapshot, but after binding the domain to the new IP, i see 502 error.

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.

Submit an Answer
1 answer

Hey friend,

I’m assuming you are referring to the 502 Bad Gateway error. This happens when a web server fails to connect to a back-end service that it is configured to pull data from when a page is requested. Most commonly this refers to reverse proxy setups or php-fpm, where either the service being proxied to or php-fpm is not running.

It may be that your web server calls a back-end app that was not configured to start at boot time, or that it has an error starting. Checking the web server logs may help you to identify what that app is, but from there it’s hard to advise further as that app could be almost anything and I’m not sure what it is.


  • Thank you for answer!
    I have Flask app on my original droplet.
    Can you tell me what settings (may be nginx) need to be changed on my new droplet created via snapshot?