Here are the different reasons why you get 502 bad gateway error:

502 bad gateway nginx beheben. Check the load on the server and fix it if there is a high load. A 502 bad gateway error indicates that the edge server (server acting as a proxy) was not able to get a valid or any response from the origin server (also called upstream server). How to increase request timeout in nginx.

Sometimes, 502 bad gateway errors are caused by dns problems. The internet engineering task force (ietf) defines the 502 bad gateway error as: Configuration file /etc/nginx/nginx.conf test is successful joilson september 1, 2016 hello friend a nginx is with normal setting, but i think that’s a bug, because so far i haven’t found anything that solves

Check if the port 80 / 443 is blocked in firewall; Check the dns is propagating properly. Try again later (to see if the web site administrators or your isp have fixed the problem) if possible include links to problem websites with your questions, so that we can visit.

It can also happen if your server. Threats include any threat of suicide, violence, or harm to another. The configuration file /etc/nginx/nginx.conf syntax is ok nginx:

Your dns servers are most likely set by your isp. Check and confirm is there is any connection timeout error on the nginx. I posted a few topics to the mailing list through this forum and i get a 502 bad gateway message from nginx when i try to view the topic.

Check the nginx error logs. What causes 502 bad gateway error. Harassment is any behavior intended to disturb or upset a person or group of people.