Explore information related to 502 bad gateway aws
Vestacp 502 bad gateway error
This article will guide you on common causes for #Vestacp #502 bad gateway #error and different methods to fix this error.
A 502 Bad Gateway 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).
Server software timeouts: This error can also occur when a web server takes more time to complete and a caching tool reaches its timeout values that time. Slow queries can also cause this problem too.'
To fix Error 502 Gateway:
1. Refresh the page.
2. Start a new browser session or load the site on a different browser.
3. Restart your computer and networking equipment.
4. Clear your #cache and cookies.
5. Change your #DNS server.
