A 403 error is frustrating because your website is online, yet a page refuses to open. Visitors may see “403 Forbidden,” “Access Denied,” or “You don’t have permission to access this resource.” The good news is that when you know how to fix a 403 forbidden error on your website, the problem is usually traceable to a small number of access settings – not a lost website or a major rebuild.
A 403 status code means the server understood the request but is refusing to allow it. That can happen when files have the wrong permissions, a security rule blocks a visitor, or the server cannot find a permitted default page in a folder. Start with the simplest checks and make one change at a time.
What a 403 Forbidden Error Usually Means
Your hosting server uses rules to decide who can view each file and folder. Those rules protect sensitive content, but they can also block legitimate visitors after a site migration, plugin update, permission change, or security configuration change.
Before changing anything, check whether the error affects your entire website or only one page. Open the site in a private browser window and test a few URLs. If possible, test from a phone using cellular data as well. This helps separate a browser, cookie, or IP-address issue from a site-wide server issue.
If only the WordPress admin area or a single directory returns 403, focus on that location. If every page is blocked, begin with your domain settings, main folder permissions, and the site’s configuration file.
1. Confirm You Are Opening the Right Website Version
Try both the www and non-www versions of your domain, plus HTTP and HTTPS if your site recently received an SSL certificate. A redirect or domain mapping issue can occasionally send visitors to a folder that does not have a public homepage.
In cPanel, open File Manager and confirm that your site files are in the correct document root. For a primary domain, this is commonly the public_html folder. Addon domains and subdomains often use their own assigned folders. If an index file is sitting in the wrong directory, the server may refuse to display a folder listing and return a 403 error instead.
Look for a valid homepage file such as index.html or index.php. If you recently uploaded a new site, make sure the file name uses lowercase letters. On most hosting servers, Index.html and index.html are different files.
2. Check File and Folder Permissions in cPanel
Incorrect permissions are one of the most common reasons for a 403 error. Permissions determine whether the server can read a file or enter a folder.
In cPanel File Manager, right-click the affected folder or file and choose Permissions. For most shared hosting websites, these settings are a safe starting point:
- Folders: 755
- Standard website files: 644
- Configuration files that require tighter access: often 600 or 640, depending on the application
- PHP scripts: usually 644
Do not set files or folders to 777 as a quick fix. While it may appear to solve an access problem, it creates a serious security risk and can cause your host’s security system to block the file. Shared hosting environments are designed to work with secure, standard permissions.
Check the main public_html folder first, then the specific folder showing the error. If every page is affected, also inspect the permissions on index.php, index.html, and any application entry file your site uses.
3. Test Your .htaccess File Carefully
The .htaccess file controls many useful website behaviors, including redirects, WordPress permalinks, password protection, and access restrictions. One incorrect rule can generate a 403 error for an entire site or a specific section.
In File Manager, enable the option to show hidden files. Locate .htaccess in your site’s main folder, then download a backup copy before editing it. For a quick test, rename the file to something like .htaccess-old and reload your website.
If the 403 error disappears, the issue is inside that file. You can then create a new .htaccess file or review the old one for rules that deny access. Common troublemakers include IP blocks, outdated rewrite rules, directives copied from another server, and password-protection rules left behind after a test.
For WordPress websites, log in to the dashboard if you can, then go to Settings and Permalinks and click Save Changes. WordPress will generate fresh permalink rules. If the dashboard is also blocked, restore only the standard WordPress rules after confirming a backup is available.
4. Review WordPress Plugins and Security Settings
A firewall, login protection plugin, or security plugin can block traffic when it detects suspicious activity. This is useful when the block is real, but it can also happen after repeated login attempts, a changed IP address, or an overly strict rule.
If your WordPress site shows a 403 error after installing or updating a plugin, temporarily disable that plugin. When you cannot access the WordPress dashboard, open File Manager and go to wp-content/plugins. Rename the suspected plugin folder by adding “-disabled” to its name. WordPress will deactivate it automatically.
If you do not know which plugin is responsible, temporarily rename the entire plugins folder. If the site begins working, rename it back and disable plugins one by one until you find the cause. This takes a little longer, but it avoids deleting settings unnecessarily.
Also check whether your site uses a web application firewall, content delivery network, or external security service. These tools may block a country, browser, IP address, or request pattern before traffic reaches your hosting account. Review the service’s activity log and allowlist legitimate IP addresses only when you recognize them.
5. Check Password Protection and IP Blocking
cPanel includes tools that can intentionally restrict access to a directory. They are helpful for private files, staging sites, and client portals, but they can cause confusion when enabled on a public website folder.
Review Directory Privacy settings to confirm that public folders are not password-protected. Then check IP Blocker for entries that could include your own address, your office network, or a service that needs access to the site.
Be cautious with broad IP blocks. Blocking a range can accidentally deny access to many real visitors, especially when mobile providers and offices use shared or rotating addresses. Remove only rules you understand, and document the change so you can reverse it if needed.
6. Look for Missing Index Files and Empty Folders
If a 403 error appears only when opening a directory, the server may be doing exactly what it should. Most hosting accounts disable directory browsing to keep files private. Without an index file, visitors cannot see the contents of the folder.
The fix depends on what the folder is for. A public page folder needs an index.html or index.php file. A folder meant only for images, downloads, or application files may not need direct browser access at all. In that case, do not enable directory listing just to remove the error. Keeping the directory private is usually the safer choice.
7. Rule Out a Temporary Server or Account Restriction
Less often, a 403 response comes from account-level protection rather than your site files. A malware scan, resource limit, ownership mismatch after a migration, or server security rule may prevent access. You may see a custom error page, or the problem may begin suddenly without any file changes.
Check your hosting account notifications and recent activity. If you recently moved files using FTP, restored a backup, or changed DNS, tell support exactly when the issue started and which URL returns the error. Include a screenshot, the affected page, and whether the problem happens for all visitors or only one network.
For Visiba customers, cPanel access and support can make this process faster: you can verify the common settings yourself, then provide support with the details needed to check server-side rules without guesswork.
When to Restore a Backup
Restore a backup when the 403 error began immediately after a known change and you have a clean copy from before that change. This is often practical after a failed plugin update, a broken .htaccess edit, or accidental file deletion.
Avoid restoring the whole account before checking permissions and configuration files. A full restore can overwrite newer posts, orders, form submissions, or emails. When possible, restore only the affected file or folder first. A backup is a safety net, not the first tool to use for every access error.
Prevent the Next 403 Error
Keep a recent backup before updating WordPress, plugins, themes, or site rules. Use standard permissions, avoid copying server directives from random tutorials, and record changes to security settings. If you use several tools – a WordPress firewall, a CDN, and hosting security – review their logs in the order a visitor reaches them.
A 403 error can feel like a locked door, but it is usually a clear signal that one access rule needs attention. Work from the simple checks upward, protect your backups, and ask for help before making broad permission or security changes that could create a bigger problem.