About Contact Careers Launching Soon System Status Legal

Guide · Troubleshooting

Website Errors Explained: 404, 403 and 500

An error number on a web page looks scary, but each number has a plain meaning and a short list of likely causes. This guide explains the three you are most likely to meet, what you can try yourself, and when to ask for help.

Before you start

  • The exact address that shows the error, and a screenshot of the message.
  • Time: about ten minutes. Difficulty: beginner.

What the three errors mean

Error What it means Usually fixed by
404 Not Found The server cannot find that page Correcting the link or restoring the page
403 Forbidden The server understood but refuses access Fixing permissions or a blocking rule
500 Internal Server Error The server hit an unexpected problem The site owner or the host investigating

These meanings follow Mozilla's documentation for 404, 403 and 500.

Step 1: Fix a 404

By the end of this step the page will load, or you will know it must be restored.

  1. Check the address for typing mistakes, extra slashes or a missing ending.
  2. Open your home page and click through to the page, to see if the link is broken.
  3. If you renamed or moved the page, set up a redirect from the old address to the new one.

Check: the page loads, or you know exactly which page is missing.

Step 2: Fix a 403

By the end of this step you will know whether you are blocked or a rule is.

  1. Make sure you are signed in if the page needs it.
  2. If you recently installed a security plugin or firewall rule, switch it off for a moment and test again.
  3. If you manage files, check that the permissions on the folder or file were not changed by an update or an upload.

Check: the page opens, or you know which setting blocks it. MDN notes that signing in again will not help when the refusal is tied to what the visitor is allowed to do.

Step 3: Handle a 500

By the end of this step you will have narrowed the cause, or know what to send us.

  1. Reload once in case it was brief.
  2. Think about what changed just before the error: a plugin or theme update, a new code snippet, a PHP version change.
  3. Undo that change, or restore a recent backup. See why website backups matter.
  4. If it persists, contact our team with the address, the time and what you changed.

MDN says a 500 is a catch-all response that usually needs investigation by the people running the server. It lists causes such as a faulty configuration, running out of memory and wrong file permissions.

Check: the page loads, or our team has the details to find the cause in the server logs.

What success looks like

You know which error you are looking at, you have tried the quick fixes, and if you still need help you can describe the problem clearly. Start from is my website down if the whole site fails.

Common problems

Every page shows a 404 except the home page. This is often a permalink or rewrite setting. Re-save your site's permalink settings.

A 403 appears only on one page. Check whether that page or folder has a rule or permission of its own.

A 500 appears after an update. The update is the likely cause. Undo it first, then try again with one change at a time.

FAQ

Are these errors bad for search results?

A page that shows 404 can disappear from search over time if it is truly gone. Redirect it if it moved.

Is a 500 error my fault?

Not always. It can come from your code or settings, or from the server. We can tell from the logs.

How fast should I act?

A 500 on your whole site needs quick attention. A single 404 can wait until you fix the link.

Related reading

Guide Troubleshooting

Is Your Website Down? How to Check in 5 Minutes

Not sure if your website is down for everyone or only for you? Follow these simple checks to find out, and learn what to do next in each case.

Guide Troubleshooting

How to Clear Your Browser Cache and DNS Cache

Site not updating after a change, or still showing the old page? Clear your browser cache and flush your DNS cache with these simple steps.