HTTP_502_BAD_GATEWAY appears in Chrome when the a reverse proxy or CDN received an invalid or no response from the origin server, the origin server crashed or ran out of resources, a firewall between proxy and origin blocks the connection, or DNS changes have not propagated and the proxy routes to an old server IP. This error prevents the page from loading entirely and requires troubleshooting on either the client or server side.
Common causes include a reverse proxy or CDN received an invalid or no response from the origin server, the origin server crashed or ran out of resources, a firewall between proxy and origin blocks the connection, or DNS changes have not propagated and the proxy routes to an old server IP. Most of these issues resolve with client-side fixes that take under five minutes.
What Causes HTTP_502_BAD_GATEWAY
This error triggers when the network connection between your browser and the remote server fails at a specific stage. The most frequent triggers are misconfigured network settings on your device, overactive security software intercepting connections, stale DNS cache entries, and server-side issues beyond your control. Identifying whether the problem is local or remote is the first diagnostic step.
Refresh the Page
Press Ctrl+F5 to hard refresh. 502 errors are frequently temporary, lasting seconds to minutes while a server recovers from a crash or load spike. Wait 30 seconds between attempts. If the error persists beyond 5 minutes, proceed to other fixes.
Clear Browser Cache
Your browser may cache the 502 error response. Press Ctrl+Shift+Delete, clear all cached data, and reload. Some CDNs like Cloudflare cache error pages briefly, so clearing both browser and CDN cache (if you manage the site) resolves stale 502 errors.
Try a Different Browser or Device
If the site loads in another browser or on mobile data, Chrome-specific settings cause the issue. If it fails everywhere, the server is genuinely returning 502 to all visitors and requires server-side intervention.
Check DNS Configuration
If you recently changed hosting providers or DNS records, propagation delays can route traffic to an old server that no longer exists. Use dnschecker.org to verify your domain points to the correct IP worldwide. DNS propagation takes up to 48 hours.
Disable CDN Temporarily
For site owners: if Cloudflare or another CDN shows 502, pause the CDN to let traffic hit your origin server directly. If the site works without CDN, the CDN cannot reach your origin. Check your origin server’s firewall allows CDN IP ranges.
Check Server Error Logs
For site owners: check /var/log/nginx/error.log or /var/log/apache2/error.log for upstream connection failures. Common fixes include increasing PHP-FPM workers (pm.max_children), raising PHP memory_limit, or restarting the PHP service with systemctl restart php-fpm.
Frequently Asked Questions
Does HTTP_502_BAD_GATEWAY mean my computer has a virus?
HTTP_502_BAD_GATEWAY is a standard browser diagnostic error, not a sign of malware. However, malware that modifies your network settings, DNS configuration, or proxy settings can indirectly trigger this error. If the error persists after all troubleshooting steps, run a full system scan with Windows Defender or Malwarebytes to rule out malware interference.
Why does HTTP_502_BAD_GATEWAY appear on only some websites?
When HTTP_502_BAD_GATEWAY affects specific sites, the cause is usually server-side: that particular server may be down, misconfigured, or blocked by your ISP. It can also result from DNS issues specific to that domain or cached entries for that site. Clearing your DNS cache and trying a different DNS server typically resolves site-specific occurrences of this error.
