What is 404 Forbidden Error
403 Forbidden error occurs when the web page (or other resource) you are trying to open in your web browser is a resource that you are not access to allowed .This is called a 403 error because it is the HTTP and HTTPS status code that the web server uses to describe such errors.
You usually get this error for one or two and more reasons.The first is that the owners of the web server have properly set up access permissions and you are not really allowed access to the source. The second reason is that the web server owners have set up permissions incorrectly and you really shouldn’t have when you are denied access.
Causes of 404 Forbidden
Often, HTTP 403 blocking errors are caused by incorrect configuration of client-side access, which means you can usually fix the problem yourself.
A common cause of these errors is the permissions of a file or folder, which controls who can read, write, and execute the file or folder.
There are two possibilities: either the website owner has edited the settings so that you cannot access the resources, or they have not set the correct permissions.
Another common cause is malicious or incorrect settings in the .htaccess file. This can happen after you make changes to the file. Fortunately, it is easier to fix the problem by creating a new server configuration file.
Aside from these two common causes, here are some possible triggers for the error:
Missing index page – The homepage name of the website is not index.html or index.php.
Defective WordPress Plugin – If a WordPress plugin is not configured correctly or is not compatible with other plugins, it can trigger 403 errors.
Incorrect IP address – The domain name indicates an incorrect or outdated IP address that now hosts a website that blocks your access.
Malware Infections – A malware infection can cause the .htaccess file to be constantly corrupted. You need to remove the malware before you can recover the file.
New web page link – The site owner may have updated the page link, which is now different from the cached version.
How to fix 403 Forbidden Error
Since the HTTP 403 Forbidden Error is closely related to file access permissions, the following methods will be the main focus for resolving it. That said, there are other ways to fix this problem, such as clearing the browser scanning or cache for malware.
Now we are discourses 4 error in bellow :
- Check the .htaccess File
- Disable WordPress Plugins
- Reset File and Directory Permissions
- Edit File Ownership
1. Check the .htaccess File
Since the HTTP 403 Forbidden Error is closely related to file access permissions, the following methods will be the main focus for resolving it. That said, there are other
- Disable WordPress Plugins
If you have come this far and none of the previous methods work, the error is likely to be caused by an inappropriate or defective plugin. In this step, we will try to disable the plugins to check if the 403 fixes the bug error.
We recommend disabling all plugins at once instead of going through the process one by one. By following this procedure, you will be able to identify the problem and work towards a solution. Here’s what you need to do:
Access your hosting account via FTP or use the hosting account’s file manager and go to the public_html -> wp-content folder.
Locate the plugin folder.Try accessing the website again. If the error is no longer there, a problematic plugin is the actual source of the error.
Rename the folder to Plugins again. Now you need to deactivate the plugins one by one from your WordPress dashboard and check if the site is still working. This way, you will be able to detect defective plugins.
Once you find it, update or delete the plugin if necessary. However, if the error still appears, you may need to contact your hosting provider for assistance.
- Reset File and Directory Permissions
Another possible reason for triggering HTTP 403 errors is incorrect permissions for files or folders. In general, when files are created, they come with specific default file permissions, which control how you can read, write, and run.
- Edit File Ownership
If you use Linux or VPS hosting, incorrect file ownership can trigger a 403 Prohibition Error.
Typically, files and folders can be assigned to an owner, a group, or both. Note that you need SSH access to change ownership in this environment. You will also need an SSH terminal to connect to the VPS server.
Once you’ve connected SSH to your web server, verify ownership using this SSH command:
ls -1 [file name]
The results will look something like this:
-rwxrw-rw- 1 [owner] [group] filename.txt
Look at the owner and group part. Proper ownership should be the username of your hosting account. If you see a different ownership, use the chown Linux command to change the ownership of the file. Here are the basic syntax for chown:
chown [owner] [: group] [file name]
For example, if your username is Hostinger, use syntax like:
chown Hostinger filename.txt
How To Fix 403 Forbidden Error In WordPress
To help you fix the 403 Forbidden Error on your WordPress site, we’ll cover five individual troubleshooting steps in detail:
- File permission
Each folder and file on the server of your WordPress site has its own unique file permissions which can be controlled by:
Read – View the data in the file / View the contents of a folder.
Write – Modify / add or delete files inside a folder
Execute – Run the file and / or run it as a script / Access a folder and execute functions and commands.
These permissions are indicated by a 3-digit number, each number indicating the permissions level for each of the 3 sections abo
Typically, these permissions “work” for your WordPress site. However, if something goes wrong with the file permissions on your WordPress site, it could be a 403 blocking error.To view and change your site’s file permissions, you need to connect via FTP / SFTP.
For the screenshots in the tutorial below, we will use the free FileZilla FTP program. The basic principles will apply to any FTP program, though – you just need to apply them to a different interface.
Once you are connected to your server, you can right-click on it to see the permissions of a file or folder:
Of course, manually checking permissions for each file or folder is not really an option. Instead, you can automatically apply file permissions to all files or folders inside a folder.
According to the WordPress Codex, the standard file permissions for WordPress are:
File – 644 or 640
Directory – 755 or 750
One exception is that your wp-config.php file should be 440 or 400.
To set these permissions, right-click on the folder that contains your WordPress site Then, select File Properties:
Enter 755 or 750 in the numeric value box. Then, select Rickers in the subdirectory and apply to the directory only:
Once you have applied the correct permissions to the directories, you will repeat the process for the files. Only this time:
Enter 644 or 640 in the numeric value box
Select Rickers in the subdirectory
Select Apply to files only
To finish the process, you just need to manually adjust the permissions on your wp-config.php file to 440 or 400:
If file permission issues caused 403 blocking errors, your site should start working again now.
- htaccess file
A 403 error can be the result of improper .htaccess file configuration. The .htaccess file controls the website configuration file.
However, if you are hosting elsewhere and your host uses an Apache web server, a common cause of 403 blocking errors is a problem with your site’s .htaccess file.
The .htaccess file is a basic configuration file used by the Apache web server. You can use it to set up redirects, restrict access to all or some of your sites, and so on.
Because it is so powerful, even if the slightest mistake can cause a big problem like 403 bans error.
Instead of trying to fix the .htaccess file problem, a simple solution is to force WordPress to create a new, clean .htaccess file.
To do this:
Connect to your server via FTP
Find the .htaccess file in your root folder
Download a copy of the file to your computer (it’s always a good idea to keep a backup in case)
Once you have a secure backup copy on your local computer, delete the .htaccess file from your server.
Now, if your .htaccess file is a problem you should be able to access your WordPress site.
To force WordPress to create a new, clean .htaccess file:
Go to Settings → Permalink in your WordPress Dashboard
Click Save Changes at the bottom of the page (you don’t need to make any changes – just click the button)
And that’s it – WordPress will now create a new .htaccess file for you.
- Disable and then reactivate your plugins
If your site file permissions or .htaccess files are not a problem, the next place to look is your plugins. This could be a bug in a plugin or a compatibility issue between different plugins
Whatever the problem, the easiest way to find the problematic plugin is with a little trial and error. Specifically, you need to deactivate all your plugins and then reactivate them one by one until you find the culprit.
If you can still access your WordPress dashboard, you can perform this process from the general plugin area.
If you can’t access your WordPress dashboard, you’ll need to connect to your WordPress site’s server via FTP / SFTP instead.
Once you are connected to your server via FTP:
Browse to the wp-content folder
Find the Plugins folder inside the wp-content folder
Right-click the Plugins folder and select Rename
Rename folder. You can rename it, but we recommend disabling plug-ins to make it easier to remember.
By renaming the folder, you have effectively disabled all plugins on your site
Now, try accessing your site again. If your site works, you know that one of your plugins is causing a 403 ban error.
To find the culprit, reactivate your plugins one by one until you find out which plugin is causing the problem.
After renaming the file in the Plugins folder, when you visit the Plugins area on your site you will see a number of errors that the plugin file does not exist:
To resolve this issue and restore your ability to manage plugins, use your FTP program to rename the folder to Plugins. So, if you rename it and disable plugin, change it to plugins again.Once you do this, you will again see a complete list of all your plugins. Only now, they will all be disabled:
Use the active button to reactivate one by one
Once you’ve found the plugin causing the problem, you can either contact the plugin developer for help or choose an alternative plugin that performs the same thing (we’ve collected
- Disable CDN temporarily
Still having problems? Contact your hosting provider
If any of the above solutions do not work for you, we suggest contacting your hosting provider. They can probably help you identify the problem and get you back up and running.