πŸ“„
Webhosting

Resolving the 403 Forbidden error: causes and fix

πŸ“… 15 October 2026 ✏️ 15 October 2026 ⏱ 4 min leestijd

Getting a 403 Forbidden error message on your website? Read here about the most common causes and how to solve them step by step.

A 403 Forbidden error message means that the server understands your request but refuses to show the page. This is usually caused by incorrect file permissions, a faulty .htaccess file, a missing index page, or a security rule blocking your IP. In this article, you’ll walk step by step through the most common causes and solutions.

What exactly does a 403 Forbidden error mean

The HTTP status code 403 indicates that the web server has received your request but deliberately refuses to show the requested page or file. This differs from a 404 error, where the page simply doesn’t exist. With a 403, the page often does exist, but you (or the server) don’t have permission to view it.

Common causes

There are a few causes you’ll encounter in almost all cases:

  • Incorrect file permissions: folders and files need specific permissions to be read by the web server.
  • Missing or faulty index page: without an index.php or index.html in a folder, the server can’t display anything if directory listing is disabled.
  • Faulty .htaccess file: an incorrect rule in your .htaccess can block access to an entire folder.
  • IP block or firewall rule: security software may have incorrectly blocked your IP address.
  • Plugin or security rule in WordPress: some security plugins block access based on user-agent or referrer.
πŸ’‘ Tip: First, look closely at the error message. If it says “Forbidden” without further explanation, it often points to permissions or .htaccess. If there’s a message from a security module, it’s usually a blocked IP.

Step-by-step solution

1

Check file and folder permissions

Folders should usually have permissions of 755 and files 644. Adjust this via the file manager in your hosting panel or via FTP.

2

Check whether an index file is present

Make sure there’s an index.php or index.html in the folder, or explicitly enable a start page for the folder in question.

3

Temporarily rename your .htaccess file

Rename .htaccess to, for example, .htaccess_old and reload the page. If it now works, the error is in those rules and you can restore them step by step.

4

Check for IP blocks

Check the security settings or firewall of your hosting panel to see if your IP address has been accidentally blocked, and remove the block if needed.

5

Temporarily deactivate security plugins

If you use WordPress, temporarily deactivate security plugins to test whether they’re causing the block.

If you work with Plesk, you’ll find file permissions, .htaccess settings, and firewall rules clearly organized in the panel, without needing to use the command line.

Preventing 403 errors

A few habits will prevent you from running into a 403 error again in the future:

  • Only adjust file permissions via your hosting panel or FTP client, not manually via unreliable scripts.
  • Always make a backup before making changes to your .htaccess file.
  • Keep security plugins and firewall rules up to date, but regularly check that they aren’t blocking legitimate traffic.
  • Maintain an up-to-date backup of your website, so you can quickly revert if a change still goes wrong.

If you’re unsure whether the problem lies with your domain settings or webhosting, also check whether your DNS settings and nameservers are correct. If you’re considering switching to another hosting provider due to recurring problems, read more about switching to Tandata.

Frequently asked questions

Is a 403 error the same as a 404 error?

No. A 404 means the page doesn’t exist, while a 403 means the page exists but access is being denied.

Can an incorrectly configured SSL certificate cause a 403 error?

Not directly, but an incorrect redirect rule that’s often added together with SSL settings in .htaccess can cause a 403.

Why do I only get a 403 error on my own computer?

This usually points to an IP block by a firewall or security module. Check whether your IP address has been blocked in the security settings.

Does it help to re-upload the folder?

Sometimes, especially if file permissions were set incorrectly during upload. Always check the permissions of folders and files after re-uploading.

Conclusion

You usually resolve a 403 Forbidden error by checking file permissions, the .htaccess file, the presence of an index page, and any IP blocks one by one. By systematically going through these steps, you’ll quickly find the cause and your website will be accessible again.

View webhosting β†’

Was dit artikel nuttig?