Back to BlogServers
Troubleshooting 502 Bad Gateway Errors in Nginx
The most common causes of 502 errors in Nginx and how to identify which one is affecting your server.
A 502 Bad Gateway response from Nginx usually means Nginx could not get a valid response from the upstream application.
Common causes include the application process being down, incorrect upstream ports, timeouts and socket permission issues.
Start with the Nginx error log and the application process status, then verify the upstream configuration.