See a 502 Bad Gateway error? Learn what it means, why it happens, and follow simple steps to fix it, whether you’re a visitor or a site owner.
You clicked a link, and instead of the page you wanted, you got a wall of text that says “502 Bad Gateway.” No picture, no explanation you can actually use, just a code that looks like it was written for robots, not people.
Here’s the short version: a 502 error means two servers had a conversation, and it didn’t go well. One server was supposed to pass along a response from another server, and instead it got something broken, or nothing at all.
This happens to visitors on ordinary websites and to site owners running their own servers. Below, you’ll learn exactly what causes a 502 bad gateway error, how to fix it depending on which side of the screen you’re on, and how it’s different from similar-looking errors like 500, 503, and 504.
What Is a 502 Bad Gateway Error?
A 502 bad gateway error means a server acting as a middleman — a gateway or proxy — asked another server for information and got back a bad answer. Not a wrong answer. A broken one.
Think of a relay race. One server hands off the request to the next one, expecting a smooth pass. When that handoff fails, the second runner drops the baton, shows up late, or isn’t even on the track, the first server has nothing usable to give back. So it tells your browser: bad gateway.
This is a server-side problem almost every time. Your browser did its job correctly. It sent a normal request. The breakdown happened somewhere behind the scenes, between servers you can’t see and generally can’t control.
That’s also why the fix usually depends on who’s reading this. If you’re a visitor, there’s only so much you can do (though it’s still worth trying). If you run the website, the real fix is on your end.
What Causes a 502 Bad Gateway Error?
A 502 error rarely has one single cause. Here are the usual suspects.
Server Overload
When a server gets more traffic than it can handle, it slows down or stops responding properly. The proxy in front of it waits for an answer, doesn’t get one in time, and reports a 502 instead.
Temporary Server Outage
Sometimes the backend server is simply down, maybe it’s restarting after an update, or it crashed and hasn’t recovered yet. The gateway has nothing to forward, so visitors see the error until the server comes back.
DNS Problems
Domain Name System (DNS) is what translates a website address into the numeric location of a server. If DNS records are wrong, outdated, or slow to update after a server change, the gateway may not be able to find the right destination.
Firewall Blocking Requests
Firewalls are meant to stop harmful traffic, but they can be too aggressive. If a firewall rule mistakenly blocks the connection between the proxy and the backend server, the result looks exactly like a 502.
Hosting Issues
Shared hosting environments sometimes hit resource limits, CPU, memory, or the number of simultaneous connections allowed. When a hosting account is capped out, the server behind it can stop responding correctly.
Reverse Proxy Problems
A reverse proxy sits in front of your web application and routes traffic to it. If it’s misconfigured — pointing to the wrong port, the wrong internal address, or a server that no longer exists — it can’t complete the handoff.
CDN Issues
A content delivery network (CDN) caches and serves your site from locations closer to visitors. If the CDN can’t reach your origin server, or if there’s a hiccup in its own network, it may return a 502 instead of your site.
Cloudflare Issues
Cloudflare is one of the most widely used CDNs, and a “Cloudflare 502 bad gateway” message specifically means Cloudflare couldn’t get a working response from your actual hosting server. The problem is almost always on the origin server’s side, not Cloudflare’s.
Nginx Issues
Nginx is popular web server and reverse proxy software. An “nginx 502 bad gateway” error typically shows up when Nginx is trying to pass a request to an application server (like PHP-FPM or a Node.js process) that isn’t responding.
PHP-FPM Issues
PHP-FPM manages PHP processes for many websites, including most WordPress sites. If it runs out of available workers, times out, or crashes, the web server in front of it has nothing to relay — hence the 502.
Application Errors
Bugs in your website’s code, a bad plugin, a broken theme, or an update gone wrong can all cause the application itself to fail in a way that produces an invalid response upstream.
How to Fix a 502 Bad Gateway Error
For Website Visitors
You didn’t cause this, but a few quick checks can rule out problems on your end:
- Refresh the page. Many 502 errors are brief. A simple reload often works.
- Wait a minute, then try again. Give the server time to recover from overload or a restart.
- Clear your browser cache. Old, stored data can occasionally interfere with loading a page correctly.
- Try a different browser or device. This tells you whether the problem is specific to your setup.
- Disable your VPN or proxy temporarily. These add an extra hop that can sometimes trigger gateway errors.
- Restart your router. Unplug it for about 30 seconds, then reconnect. This clears minor connection issues.
- Check the site’s status. Search for the site’s name plus “down” or check a status page if one exists, to see if others are having the same problem.
Tip: If the site loads fine on another network or device, the issue is almost certainly on the website’s end, not yours.
For Website Owners
If it’s your site throwing the error, work through these in order:
- Check your server logs first. Error logs (like Nginx’s error log or your application’s logs) usually point straight to the failure.
- Restart your web server. A quick restart of Nginx, Apache, or your reverse proxy clears many temporary glitches.
- Restart PHP-FPM (or your app server). If PHP-FPM or a similar process manager has stalled, restarting it often restores service immediately.
- Test your DNS. Confirm your domain points to the correct server IP address, especially after any recent migration.
- Disable plugins and themes one at a time. This isolates whether a specific add-on is causing the malfunction, particularly on WordPress.
- Review your firewall rules. Make sure nothing is blocking legitimate traffic between your proxy and your backend.
- Check your CDN or Cloudflare settings. Confirm your origin server is reachable and that DNS records in your CDN dashboard are current.
- Contact your hosting provider. If you’ve ruled out your own configuration, your host may be dealing with a resource limit or an outage on their infrastructure.
Common 502 Bad Gateway Messages
You might see this error phrased differently depending on the browser, server, or service involved:
- 502 Bad Gateway — the standard, generic version of the message.
- HTTP Error 502 — the same error, just labeled by its status code.
- 502 Proxy Error — usually from Apache, pointing to a failed proxy connection.
- Nginx 502 Bad Gateway — Nginx couldn’t get a valid response from the application server behind it.
- Cloudflare 502 Bad Gateway — Cloudflare couldn’t reach or get a valid reply from your origin server.
All of these describe the same underlying problem. Only the wording changes based on which piece of software is reporting it.
502 vs 500 vs 503 vs 504 Errors
These four error codes look similar but mean different things.
| Code | Meaning | Typical Cause | Who Usually Fixes It |
|---|---|---|---|
| 500 | Internal Server Error | A general failure in the server’s own code or configuration | Website owner or developer |
| 502 | Bad Gateway | A proxy received an invalid response from an upstream server | Website owner or hosting provider |
| 503 | Service Unavailable | The server is temporarily unable to handle requests (overload or maintenance) | Website owner or hosting provider |
| 504 | Gateway Timeout | A proxy didn’t get any response from the upstream server in time | Website owner or hosting provider |
Frequently Asked Questions
Is a 502 error my fault? Almost never. It’s a server-side issue, though a VPN, proxy, or unusual network setup on your end can occasionally trigger it.
Can I fix a 502 error as a visitor? You can often work around a temporary one by refreshing, waiting, or switching networks. But if the cause is on the server, only the site owner can permanently resolve it.
Does a 502 error mean a website is down? Not exactly. It means a part of the server chain failed to communicate properly. The site could come back within seconds, or it could stay broken until someone fixes the underlying issue.
How long does a 502 error last? It varies. Overload-related errors often clear up in minutes. Configuration or outage-related ones can last hours until someone addresses the cause.
Is a 502 error permanent? No. It’s a symptom of a temporary breakdown in communication, not a permanent state. Once the underlying problem is fixed, the site loads normally again.
Does clearing cache fix a 502 error? Sometimes, if the issue was related to stored browser data. It won’t help if the problem is on the server side, but it’s a quick, harmless step to try.
Can Cloudflare cause a 502 error? Cloudflare can display the error, but the root cause is usually the origin server behind it failing to respond — not Cloudflare itself.
What should website owners do first? Check the server error logs. They almost always show exactly where the failure happened, saving time compared to guessing.
Can a 502 error affect my site’s SEO? Yes, if it happens frequently or lasts a long time. Search engines may struggle to crawl and index pages that repeatedly return server errors.
Final Thoughts
A 502 Bad Gateway error is frustrating, but it’s rarely mysterious once you understand what’s happening: one server asked another for a response and got something broken instead.
If you’re a visitor, start simple, refresh, wait, clear your cache, or try another network. If none of that works, the problem is on the site’s end, and there’s nothing more to do but come back later.
If you run the website, go straight to your server logs, restart the services involved (web server, PHP-FPM, or your reverse proxy), and check DNS, firewall, and CDN settings. Most 502 errors trace back to a handful of familiar causes, so a methodical check usually finds the fix quickly.