CheckWebsiteNow

Server errors (5xx)

500 Internal Server Error

Something went wrong on the website server.

Quick answer

A 500 is a general server error. The server hit a problem it could not handle, often a bug or a broken configuration. It is not caused by your device.

When to wait: Often yes. Many 500 errors are fixed within minutes once the owner notices.

If you are visiting the website

  1. Wait and reload Wait a few minutes, then reload the page once. Short problems often fix themselves when the server restarts.
  2. Reload without the cache A reload that skips the cache (saved copies) makes sure you see the newest answer from the server, not an old error page.
    Windows
    Chrome: press Ctrl + Shift + R, or Shift + F5.
    Linux
    Chrome: press Ctrl + Shift + R, or Shift + F5.
    macOS
    Chrome: press Command + Shift + R.
  3. Check the service's status page Big services often publish an official status page that lists known problems.
  4. Try a different page If only one page or one action fails, such as search or checkout, use the rest of the site. Telling the owner which part breaks helps them a lot.
  5. Do not pay or submit twice If the error appeared right after you paid or sent a form, check your email, bank app or account first. The action may have gone through even though the page failed.
  6. Tell the website owner If the problem stays, contact the website through another channel (email or social media) and tell them the exact error, the address and the time.

If you run the website

  1. Check server error logs Look at your web server and application logs for the exact time of the error. They usually name the failing file, line or service.
  2. Review recent changes Think about what changed recently: a deployment, plugin update, configuration edit or DNS change. Roll back with your tested procedure if needed.
  3. Test configuration files A single typo in a server config or .htaccess file can cause a 500. Run sudo nginx -t or apachectl configtest after every edit, then reload.
  4. Check the database and resources Make sure your database is running and reachable. Also check free disk space and memory, because a full disk or memory limit can crash the application.
  5. Keep detailed errors private Show full error details only in logs or a test copy, never on the public site. Public stack traces (detailed error reports) can leak file paths or secrets.

Is it the website or me?

It is the website. A 500 is created by the server when its own software fails. Changing your browser, device or network rarely helps.

The only things worth trying on your side are a short wait and one reload.

What this error is not

A 500 does not mean the site is gone for good, or that your account was deleted. It also does not point to overload; that is more often a 503.

It is a general "something broke" answer, so the real reason is only visible to the owner.

For developers: what happens technically

The server hit an error it had no more specific code for, so it sent the generic 500. Typical sources are an unhandled exception (a crash in the code), a bad configuration line or a lost database connection.

The real reason is almost always written in the application or web server error log at the same second.

Common questions

Can a 500 error come from my computer?

Almost never. The server creates this error itself. Your device only shows the page it got back.

I paid and got a 500. Was I charged?

Maybe. Check your email, bank app or account before paying again. If you were charged, contact the shop with the time of the error.

How long do 500 errors last?

There is no fixed time. Some disappear within minutes after a restart or rollback, others need a code fix. If it lasts more than an hour, tell the site.

Why do I see a 500 on one page but not on others?

Each page can run different code. A bug in one feature, such as search or checkout, can break only that part.

Likely causes

  • Common A bug or crash in the website software. (Website side)
  • Common A broken configuration or plugin update. (Website side)
  • Sometimes The database is unavailable. (Website side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: