PH-
Welcome to PHCorner Forums! Sign up for free to unlock full access and exclusive privileges, including:
- Asking questions about computer and mobile issues
- Discovering internet tips for your mobile network and computer
🔒 Closed Ano po bang pwedeng gawin dito para maopen yung site?
- Thread starter Schneizel12
- Start date
-
- Tags
- learner
Cause of 502 Bad Gateway Errors
1) Domain name not resolvable
The domain name is not pointing to the correct IP or it does not point to any IP this problem may happen. Also, DNS propagation could take some time to make changes in DNS setting. It may take 24 to 48 hours to make reflect which is dependent upon the TTL defined per record on the DNS.
2)server down
The origin server is not reachable, this may due to the server is down for some reason or there is no communication to the server given.
3) Firewall blocks
A firewall interrupts the communication between the edge servers and the origin server. This may be caused by security plugins of your CMS.As a part of DDOS protection and mitigation process or due to some strict firewall rules servers can be blocked from accessing the original server.
What to do after getting 502 Bad Gateway error
1)If you got 502 bad gateway error you should check your IP address in the zone management, click on setting and make sure that the given IP is correct or not. If the IP address incorrectly, you need to update the origin IP in the Pull Zone Configuration to match the new IP, clear your zone cache. This should fix the problem.
2) By using a ping test or trace-route, verify if your server is reachable or not.
3) If the IP address is correct to check your firewall rules if you are seeing unusual drops.
Errors Like 502 Bad Gateway
Error messages are related to the “502 Bad Gateway error” is given below:
500 Internal Server Error
503 Service Unavailable
504 Gateway Timeout
If you need any further help please do reach our support department.
1) Domain name not resolvable
The domain name is not pointing to the correct IP or it does not point to any IP this problem may happen. Also, DNS propagation could take some time to make changes in DNS setting. It may take 24 to 48 hours to make reflect which is dependent upon the TTL defined per record on the DNS.
2)server down
The origin server is not reachable, this may due to the server is down for some reason or there is no communication to the server given.
3) Firewall blocks
A firewall interrupts the communication between the edge servers and the origin server. This may be caused by security plugins of your CMS.As a part of DDOS protection and mitigation process or due to some strict firewall rules servers can be blocked from accessing the original server.
What to do after getting 502 Bad Gateway error
1)If you got 502 bad gateway error you should check your IP address in the zone management, click on setting and make sure that the given IP is correct or not. If the IP address incorrectly, you need to update the origin IP in the Pull Zone Configuration to match the new IP, clear your zone cache. This should fix the problem.
2) By using a ping test or trace-route, verify if your server is reachable or not.
3) If the IP address is correct to check your firewall rules if you are seeing unusual drops.
Errors Like 502 Bad Gateway
Error messages are related to the “502 Bad Gateway error” is given below:
500 Internal Server Error
503 Service Unavailable
504 Gateway Timeout
If you need any further help please do reach our support department.
down po yun site, antay mo magresume para makapasok kaSchneizel12
Honorary Poster
Thank you thankyou sa mga replies. Big help. Sensya na haha
- Status