Why is my website showing a 403 forbidden error?

Summary

This guide helps you troubleshoot and resolve: Why is my website showing a 403 forbidden error?. Follow the steps below to fix the issue.

Common Causes

A 403 Forbidden error means your web browser can reach the server, but the server is refusing to allow access to the requested page or directory. This is different from a 404 Not Found error, which means the page does not exist. A 403 error usually points to a permission issue, a security rule blocking access, or a missing index file. This guide covers common checks you can perform across most hosting control panels and content management systems.

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Quick Fix Steps

1. Refresh your browser page after waiting a minute to rule out temporary caching.
2. Try accessing the website from a different network, such as mobile data instead of office Wi-Fi.
3. Clear your browser cache and cookies, then revisit the site.
4. Check whether the error occurs on all pages or only specific sections of the website.

Detailed Instructions

Check File and Directory Permissions

Incorrect file permissions are one of the most common causes of a 403 error. The web server needs read access to files and execute access to directories to serve content.

1. Log in to your hosting control panel and open File Manager or connect via FTP/SFTP.
2. Navigate to the public web directory, typically public_html or www.
3. Right-click a folder and select File Permissions or Change Permissions.
4. Set directories to 755 and files to 644.
5. Apply the changes and refresh your website to test.

Verify Index Document Configuration

If a directory does not contain a default index file and directory listing is disabled, the server may return a 403 error.

1. Open File Manager in your hosting control panel.
2. Check that the root directory contains a file named index.html, index.php, or default.aspx.
3. If the file is missing, upload a default index file or contact your developer to restore it.
4. If you recently renamed your homepage, update any internal links or CMS settings to match the new filename.

Review .htaccess Rules

On Apache-based hosting, the .htaccess file can contain rules that block access to specific IP addresses, user agents, or entire directories.

1. Open File Manager and ensure hidden files are visible.
2. Locate .htaccess in your website root directory.
3. Download a backup copy before making changes.
4. Look for directives such as Deny from all, Require all denied, or Order deny,allow.
5. Temporarily rename the file to .htaccess_backup and refresh your site.
6. If the error disappears, the .htaccess rules were the cause. Restore the backup and edit the restrictive rules.

Check IP-Based Access Blocks

Security plugins, firewalls, or server configurations may block your IP address, especially after multiple failed login attempts.

1. Visit an IP lookup site to confirm your public IP address.
2. Log in to your hosting control panel and check IP Blocker, Firewall, or Security settings.
3. Look for your IP address in any deny or block lists.
4. Remove your IP from the block list if it is listed.
5. Test the website again from the affected network.

Content Management System Issues

If your website runs on a CMS, a recently installed plugin, theme, or extension may be triggering security rules that produce a 403 error.

1. Log in to your CMS administration dashboard.
2. Navigate to Plugins, Extensions, or Modules.
3. Deactivate any plugins installed or updated shortly before the error began.
4. Refresh the website frontend to test.
5. Reactivate plugins one at a time to identify the conflicting extension.

When to Contact Support

If you have checked file permissions, index files, .htaccess rules, IP blocks, and DNS caching without resolving the issue, the cause may be server-side configuration, mod_security rules, or file ownership problems that require administrative access.

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?