A 502 Bad Gateway error means that one server act as a gateway or proxy received an invalid response from another server then it come across the 502 Bad gateway. Simply saying, when your reverse proxy (like Nginx) tried to connect to the backend service or web application (like Apache, Node.js, or a Docker <\/a>container), but the communication failed and it could not connect. It doesn’t always mean your backend is down. The proxy just doesn\u2019t know how to talk to it correctly due to misconfigurations.<\/p>\n\n\n\n So the reason why it Works on IP but Not on Domain :<\/strong><\/p>\n\n\n\n If your website works using the server\u2019s IP address (like http:\/\/192.168.50.12) but not with your domain name (like https:\/\/example.com), so it usually means:<\/p>\n\n\n\n So below are the steps to follow to fix this issue one by one. <\/strong><\/p>\n\n\n\n Step 1: Check If Domain Resolves Correctly<\/strong><\/p>\n\n\n\n From your reverse proxy server, test if your domain resolves to the correct IP:<\/p>\n\n\n\n ping example.com <\/p>\n\n\n\n or<\/p>\n\n\n\n nslookup example.com<\/p>\n\n\n\n If the IP shown doesn\u2019t match your server\u2019s IP, then DNS is the issue.<\/p>\n\n\n\n You need to update your DNS records to fix it (A or CNAME) or by adding a temporary entry in \/etc\/hosts like this:<\/p>\n\n\n\n 192.168.50.12 example.com<\/p>\n\n\n\n Save and try again. <\/p>\n\n\n\n Step 2: Check Reverse Proxy Configuration<\/strong><\/p>\n\n\n\n If you\u2019re using Nginx as a reverse proxy, you need to open your site configuration file (for example, \/etc\/nginx\/sites-available\/example.com):<\/p>\n\n\n\n #sudo nano \/etc\/nginx\/sites-available\/example.com<\/p>\n\n\n\n You will see the code like below <\/p>\n\n\n\n server_name example.com;<\/p>\n\n\n\n location \/ {<\/p>\n\n\n\n proxy_pass http:\/\/example.com:8080;<\/p>\n\n\n\n }<\/p>\n\n\n\n }<\/p>\n\n\n\n <\/p>\n<\/blockquote>\n<\/div>\n\n\n\n So the problem could be here, the proxy is trying to reach example.com again, which causes a loop.<\/p>\n\n\n\n You should replace it with your backend IP address instead domainname like below :<\/p>\n\n\n\n <\/p>\n\n\n\n server {<\/p>\n\n\n\n server_name example.com;<\/p>\n\n\n\n location \/ {<\/p>\n\n\n\n proxy_pass http:\/\/127.0.0.1:8080;<\/p>\n\n\n\n proxy_set_header Host $host;<\/p>\n\n\n\n proxy_set_header X-Real-IP $remote_addr;<\/p>\n\n\n\n }<\/p>\n\n\n\n }<\/p>\n\n\n\n <\/p>\n<\/blockquote>\n\n\n\n Save the file and test your Nginx configuration using command below :<\/p>\n\n\n\n #sudo nginx -t<\/strong><\/p>\n\n\n\n #sudo systemctl reload nginx<\/strong><\/p>\n<\/blockquote>\n\n\n\n Now, try to access the domain again. If it works, the issue was a proxy loop.<\/p>\n\n\n\n Step 3: Check for SSL\/HTTPS Issues<\/strong><\/p>\n\n\n\n If your site uses HTTPS, you need to make sure both your proxy and backend are handling SSL correctly.<\/p>\n\n\n\n Sometimes, you only need SSL on the proxy, not on the backend.<\/p>\n\n\n\n For example, if Nginx handles HTTPS, and your backend only runs HTTP, your configuration should be like:<\/p>\n\n\n\n server {<\/p>\n\n\n\n listen 443 ssl;<\/p>\n\n\n\n server_name example.com;<\/p>\n\n\n\n ssl_certificate \/etc\/letsencrypt\/live\/example.com\/fullchain.pem;<\/p>\n\n\n\n ssl_certificate_key \/etc\/letsencrypt\/live\/example.com\/privkey.pem;<\/p>\n\n\n\n location \/ {<\/p>\n\n\n\n proxy_pass http:\/\/127.0.0.1:8080;<\/p>\n\n\n\n proxy_set_header Host $host;<\/p>\n\n\n\n proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<\/p>\n\n\n\n }<\/p>\n\n\n\n }<\/p>\n<\/blockquote>\n<\/div>\n\n\n\n If you mistakenly use proxy_pass https:\/\/example.com;, Nginx might fail to validate the SSL certificate, and it will cause a 502 error.<\/p>\n\n\n\n Step 4: Check Backend Service<\/strong><\/p>\n\n\n\n In some cases , the backend service (like Apache, Gunicorn, or Node.js) isn\u2019t actually responding even though it seems to be running.<\/p>\n\n\n\n You need to check and verify if it\u2019s listening on the correct port:<\/p>\n\n\n\n sudo netstat -tlnp | grep 8080<\/strong><\/p>\n\n\n\n or<\/p>\n\n\n\n ss -tlnp | grep 8080<\/strong><\/p>\n\n\n\n If the service isn\u2019t running, you need to restart it:<\/p>\n\n\n\n sudo systemctl restart apache2<\/strong><\/p>\n\n\n\n # or<\/p>\n\n\n\n sudo systemctl restart your_app<\/strong><\/p>\n\n\n\n Step 5: Look at Logs for More Clues and exact issue tracing<\/strong><\/p>\n\n\n\n In issue investigation, the logs works like your best friends in debugging the any issues error, specially for 502 errors. <\/p>\n\n\n\n Check Nginx error logs:<\/p>\n\n\n\n sudo tail -f \/var\/log\/nginx\/error.log<\/strong><\/p>\n\n\n\n If it shows messages like \u201cconnect() failed\u201d or \u201cbad gateway\u201d, it usually points to a connectivity issue between the proxy and the backend.<\/p>\n\n\n\n You can also check application logs to see if it\u2019s rejecting connections or crashing under load.<\/p>\n\n\n\n Step 6: Restart Services<\/strong><\/p>\n\n\n\n Once the changes are done , restart everything cleanly:<\/p>\n\n\n\n #sudo systemctl restart nginx<\/strong><\/p>\n\n\n\n #sudo systemctl restart your_app<\/strong><\/p>\n\n\n\n Then, test again using using the curl command :<\/p>\n\n\n\n curl -I https:\/\/example.com<\/strong><\/p>\n\n\n\n It it shows 200 OK response if everything is fixed.<\/p>\n\n\n\n Issues like 502 Bad Gateway errors can stem from proxy, DNS, or SSL settings, and our team is available 24\u00d77 to guide you through them. Whether you need quick troubleshooting<\/a>, configuration validation, or hands-on assistance, we\u2019re always here to help. Connect with us anytime through chat or contact us<\/a> directly for immediate support. Partner with SupportPRO<\/strong> for 24\/7 proactive cloud support that keeps your business secure, scalable, and ahead of the curve.<\/p>\n\n\n\n\n
\n
server {<\/p>\n\n\n\n\n
\n
\n
<\/p>\n\n\n\n![\"Contact](\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\")
<\/a><\/span>