Chrome HTTP Error 500: What It Means and What to Do

HTTP error 500 means the website’s server ran into a problem and could not finish your request. Chrome is only showing you the reply, so the fault is not in your browser. Load a different site to check your side, press Reload once, then wait a while and try again. If it keeps happening, tell the site’s owner.

Applies to: Google Chrome on any device. Not version-specific. No account or setting is involved.

What does “HTTP ERROR 500” mean in Chrome?

The page has a plain heading, “This page isn’t working,” with a line under it saying the site “is currently unable to handle this request.” Near the bottom you will see HTTP ERROR 500 and a Reload button.

Chrome uses that wording for the whole family of server-side errors. The 500 itself is the website’s answer. MDN describes it as the server hitting an unexpected condition that stopped it from fulfilling the request. It is the catch-all code a server sends when it has nothing more specific to say.

Here is the part that surprises people. Because a reply came back at all, your connection did its job. You reached the site. The site then tripped over its own problem.

How can I tell if the problem is the site or me?

Look at what else is happening. These three patterns cover most cases.

Other sites load, this one shows 500. The server behind that site is failing. Nothing on your end is involved.
The site works until you do one thing. Checkout, a file upload, or a login breaks and the rest of the site is fine. One function on the server is failing while the rest keeps running.
Nothing loads, or the error is an ERR_ code. That is not a 500. It points to your connection or a security problem. Start with the guides on ERR_EMPTY_RESPONSE or ERR_SSL_PROTOCOL_ERROR.

What should I do when I see a 500 error?

If the error appeared right after you clicked Pay or Submit, check your email or bank app before you try again. The server may have finished part of the job before it failed, and a second attempt could repeat it.

Open a different website in a new tab. If it loads, your connection is fine.
Go back to the broken page and press Reload once. A short hiccup on the server can clear on its own.
Give it a few minutes, then try again. Fixing a 500 is the site owner’s job, and it can take them a while.
Open the same page on another device or in another browser. If it fails there too, you have confirmed it is the server.
Contact the site’s support team. Tell them the page address and the time it happened. If the error page shows a request ID, include that. MDN notes that it helps administrators find the matching entry in the server log.

A good report is short: “The page at this address showed HTTP error 500 around this time when I tried to log in.” That gives the owner something concrete to search for in their logs. You do not need to explain how Chrome works or what you already tried.

What does not fix a 500 error?

Most of the usual Chrome fixes are aimed at problems on your computer. A 500 did not start there, so they have nothing to act on.

Clearing the cache and cookies. The failure happened on the server, not in files Chrome stored. Chrome’s own error page offers only a Reload button, which tells you where the problem sits.
Changing your DNS. DNS only finds the site’s address. A 500 reply proves you already got there.
Resetting or reinstalling Chrome. No Chrome setting changes what the server sent back.
Reloading over and over. One reload tests whether the hiccup passed. Ten more reloads cannot repair the server’s configuration.

Frequently asked questions

Is a 500 error my fault?

No. MDN says these errors need investigation by server owners or administrators, and a visitor cannot fix the cause.

Why does the page work for my friend but not for me?

A server can fail on some requests and not others. MDN lists causes such as a misconfigured server, running out of memory, an unhandled exception, or wrong file permissions. Any of those can hit one page or one action and skip the rest.

What is the difference between a 500 and other server errors?

A 500 is the general-purpose code. Servers use it when no more specific 5xx code fits. Chrome shows the same “This page isn’t working” heading for all of them.

How long should I wait before trying again?

MDN gives no set time, and neither does Chrome. A few minutes is a fair first gap. If the page is still down later in the day, assume the owner does not know yet and send a report.

I run the site. Where do I start?

Start with the server’s error log for the time of the failure. If your error page shows a request ID, search the log for it.

A 500 is the website’s problem, and the quickest check is whether other sites still load. Reload once, wait, and try again later. If the page matters to you, send the owner the address and the time.