{"id":42946,"date":"2021-07-06T14:06:19","date_gmt":"2021-07-06T11:06:19","guid":{"rendered":"https:\/\/themeisle.com\/blog\/?p=42946"},"modified":"2023-12-08T14:06:00","modified_gmt":"2023-12-08T14:06:00","slug":"403-forbidden-error","status":"publish","type":"post","link":"https:\/\/themeisle.com\/blog\/403-forbidden-error\/","title":{"rendered":"How to Fix the 403 Forbidden Error (7 Methods That Work)"},"content":{"rendered":"\n

If you encounter the WordPress 403 Forbidden error, you might not be able to log in to the back end of your site or access a specific page. This can be frustrating and prevent you from getting important work done.<\/p>\n\n\n\n

The good news is that there are several easy strategies you can try to resolve this common WordPress error<\/a>. For example, you can clear your browser cache, deactivate your plugins, or turn off your CDN. If none of that works, you can try a more advanced tactic, such as restoring your .htaccess<\/em><\/strong> file or updating your file permissions.<\/p>\n\n\n\n\n\n\n\n

\ud83d\udc49 In this post, we’ll start by introducing the WordPress 403 Forbidden error and what causes it. Then we’ll go over some ways you can troubleshoot this pesky issue. Let’s get to it!<\/p>\n\n\n\n\t\t

<\/div>\n\t\t\t
\n\t\t \t
\n\t\t \t\tHow to fix \ud83d\udc68\u200d\ud83d\udd27 the #WordPress #403 forbidden error \ud83d\udc1e\ud83d\udc1e\ud83d\udc1e<\/a>\n\t\t \t<\/div>\n\t\t \t
\n\t\t \tClick To Tweet \n\t\t \t\t<\/span>\n\t\t \t<\/a>\n\t\t <\/div>\n\t\t<\/div>\n
<\/div>\n\n\n\n

An introduction to the WordPress 403 Forbidden error<\/h2>\n\n\n\n

Before we show you how to fix the WordPress 403 Forbidden error, let’s talk a bit about what it means. As the name suggests, this message displays when you don’t have access to the server you’re trying to reach.<\/p>\n\n\n\n

You’re most likely to encounter this error when trying to log in to your WordPress admin dashboard or when installing the core software for the CMS<\/a>. However, it can also happen on any page or post you’re trying to visit.<\/p>\n\n\n\n

That can make this issue particularly frustrating. Fortunately, you can take action to get rid of it. \ud83d\ude0e<\/p>\n\n\n

<\/div>\n\n\n\n

How to fix the WordPress 403 Forbidden error (7 strategies)<\/h2>\n\n\n\n

Now that you know a bit more about the WordPress 403 Forbidden error, we’ll show some strategies you can try in order to fix it. They’re roughly ordered from easiest to hardest, so it’s best to start at the top with a few proven troubleshooting tricks.<\/p>\n\n\n\n

    \n
  1. Clear your browser cache<\/a><\/li>\n\n\n\n
  2. Deactivate your plugins<\/a><\/li>\n\n\n\n
  3. Turn off your CDN<\/a><\/li>\n\n\n\n
  4. Disconnect from your VPN<\/a><\/li>\n\n\n\n
  5. Remove and restore your .htaccess<\/em> file<\/a><\/li>\n\n\n\n
  6. Update your file permissions<\/a><\/li>\n\n\n\n
  7. Contact your web hosting provider<\/a><\/li>\n<\/ol>\n\n\n
    <\/div>\n\n\n\n

    1. Clear your browser cache \ud83e\uddf9<\/h3>\n\n\n\n

    Let’s begin with one of the simplest ways to fix the WordPress 403 Forbidden error. A corrupt or outdated browser cache can make it impossible for the server to retrieve the content for the web page you’re trying to access properly. In that case, clearing your browser cache may be enough to resolve the problem.<\/p>\n\n\n\n

    The steps to do this will depend on which browser you’re using. For example, in Google Chrome you’ll click on the three dots in the upper right-hand corner of your browser screen:<\/p>\n\n\n

    \n
    \"Google<\/figure><\/div>\n\n\n

    Go to More Tools<\/strong> \u2192 Clear Browsing Data<\/strong><\/em>. You’ll see a pop-up:<\/p>\n\n\n

    \n
    \"Clearing<\/figure><\/div>\n\n\n

    Make sure the box for Cached images and files<\/em><\/strong> is selected. If you don’t want to delete other data, you can uncheck the boxes for Browsing history<\/em><\/strong> and Cookies and other site data<\/strong><\/em>.<\/p>\n\n\n\n

    To be safe, you may want to set the Time Range<\/strong><\/em> to All Time<\/strong><\/em>. When you’re happy with your selections, click on Clear Data<\/strong><\/em>. <\/p>\n\n\n

    \n\n\n\n

    \ud83d\udc49 Here’s a guide on how to clear the browser cache in other browsers<\/a>.<\/p>\n\n\n<\/div><\/div>\n\n\n

    <\/div>\n\n\n\n

    2. Deactivate your plugins \ud83d\udd0c<\/h3>\n\n\n\n

    If you’re still seeing the WordPress 403 Forbidden error after clearing your browser cache, that means the problem is somewhere else. A smart next tactic is to try deactivating your WordPress plugins<\/a>.<\/p>\n\n\n\n

    That’s because an outdated or corrupt plugin could be causing the issue. <\/p>\n\n\n\n

    If you’re still able to access your WordPress dashboard, you can easily deactivate your plugins right from the dashboard. However, if you’re unable to access your dashboard because of the 403 Forbidden error, you can also deactivate plugins via FTP (covered below<\/em>).<\/p>\n\n\n\n

    Deactivate plugins via WordPress dashboard<\/h4>\n\n\n\n

    If you do have access to your admin screen, first create a backup<\/a> of your site, and ideally use a staging site for the following process. Then go to Plugins<\/strong> \u2192 Installed Plugins<\/strong><\/em>:<\/p>\n\n\n

    \n
    \"Deactivating<\/figure><\/div>\n\n\n

    Under each plugin, you’ll see a link labeled Deactivate<\/em>. Now, deactivate one plugin, then return to the page that’s showing the error. If it’s resolved, you’ll know that plugin was the root of the issue.<\/p>\n\n\n\n

    Otherwise, go through your entire plugin list and deactivate them one-by-one, checking your error page each time. If you can pinpoint a plugin that’s causing the 403 error, try deleting it entirely and re-installing it. Also, make sure the plugin is up-to-date. If the issue persists and is caused by an essential plugin, you may need to look for an alternative.<\/p>\n\n\n\n

    If you have a lot of plugins and the above seems too tedious, you can try deactivating them all at once. However, be especially wary of doing this on a live site rather than a testing\/staging copy.<\/p>\n\n\n\n

    Return to Installed Plugins<\/strong><\/em>, and check the box next to Plugins<\/em><\/strong> to select them all. Then open the drop-down menu for Bulk Actions<\/strong><\/em>:<\/p>\n\n\n

    \n
    \"Deactivating<\/figure><\/div>\n\n\n

    Select Deactivate<\/strong><\/em>, followed by Apply<\/strong><\/em>. If the error message goes away, you know that one of your plugins was at fault, and you can follow the process described above to test them one by one.<\/p>\n\n\n\n

    Deactivate WordPress plugins via FTP<\/h4>\n\n\n\n

    If you’re unable to access your WordPress dashboard, you can also deactivate your plugins by connecting to your site’s server via FTP using an FTP<\/a> client such as FileZilla<\/a>.<\/p>\n\n\n\n

    Once you’ve connected to your server, here’s what to do:<\/p>\n\n\n\n

      \n
    1. Find the plugins<\/em><\/strong> folder inside the wp-content<\/em><\/strong> folder.<\/li>\n\n\n\n
    2. Right-click on the plugins<\/em><\/strong> folder and choose the option to rename it.<\/li>\n\n\n\n
    3. Change the name to something like plugins-off<\/em><\/strong>.<\/li>\n<\/ol>\n\n\n
      \n
      \"How<\/figure><\/div>\n\n\n

      Changing the name of the folder will automatically deactivate all of the plugins on your site. You can then try accessing your site’s dashboard to see if the WordPress 403 Forbidden error has disappeared.<\/p>\n\n\n\n

      If the error is gone, you know that there’s an issue in one of your site’s plugins.<\/p>\n\n\n\n

      You can then go back to your FTP client and rename the folder back to plugins<\/em><\/strong> from plugins-old<\/strong><\/em>. As long as you’ve logged in to your WordPress dashboard, the plugins should now appear in the Plugins<\/strong><\/em> list again, but they will rename inactive.<\/p>\n\n\n\n

      You can reactivate them one by one until you find the plugin that’s causing the WordPress 403 Forbidden error on your site.<\/p>\n\n\n

      <\/div>\n\n\n\n

      3. Turn off your CDN \ud83d\udcbb<\/h3>\n\n\n\n

      Implementing a content delivery network (CDN)<\/a> on your website can be an excellent way to ensure that it performs optimally, no matter where your visitors are located. However, if there is an issue with your CDN’s server configuration, this could result in the WordPress 403 Forbidden error.<\/p>\n\n\n\n

      You can turn off your CDN to test this. There are many different CDN providers, but Cloudflare is one of the most popular. So we’ll use it for our example. Log in to your Cloudflare control panel, and go to Overview<\/em><\/strong> in the menu:<\/p>\n\n\n

      \n
      \"Cloudflare<\/figure><\/div>\n\n\n

      After that, scroll to the bottom of the page and find Advanced Actions<\/strong><\/em>. As you can see, you can either pause or completely remove your site from Cloudflare. We recommend just pausing it to start.<\/p>\n\n\n\n

      Then you can test your site to see if the 403 error persists.<\/p>\n\n\n

      <\/div>\n\n\n\n

      4. Disconnect from your VPN \ud83d\udea7<\/h3>\n\n\n\n

      If you use a virtual private network (VPN) to protect your privacy, this could also be causing the issue. So you might need to disconnect it. <\/p>\n\n\n\n

      That process will vary depending on your provider. However, it’s usually simple. It may be as easy as toggling an off switch in your Chrome extension settings. Once you’ve disconnected your VPN, revisit the page that was displaying the error to determine whether this was the issue.<\/p>\n\n\n

      <\/div>\n\n\n\n

      5. Remove and restore your .htaccess file \ud83d\udd04<\/h3>\n\n\n\n

      If none of the above methods have fixed the WordPress 403 Forbidden error, you can try removing and restoring your site’s .htaccess<\/em><\/strong> file. It could be corrupt.<\/p>\n\n\n\n

      However, keep in mind that this method is only suitable for advanced WordPress users. Managing website files is a delicate process, and even a tiny mistake could severely impact the functionality of your website.<\/p>\n\n\n\n

      Even if you’re comfortable moving forward, you’ll still want to begin this process by making a fresh backup of your site. Once that’s done, you’ll want to connect your website to an FTP client such as FileZilla. <\/p>\n\n\n\n

      To do this, you’ll need your FTP credentials from your web host. If you’re not sure what they are, you can find them in your control panel or reach out to your web host’s support team. Once your site is connected, you’ll be able to manage its files remotely:<\/p>\n\n\n

      \n
      \"Connecting<\/figure><\/div>\n\n\n

      Now, locate your root folder, which should be labeled something like public_html<\/em><\/strong>:<\/p>\n\n\n

      \n
      \"Accessing<\/figure><\/div>\n\n\n

      Within this folder, find the .htaccess<\/em><\/strong> file. Before going further, we recommend downloading a copy of this file so that you have a backup of its current configuration.<\/p>\n\n\n\n

      Once you’ve done that, you can Delete<\/em><\/strong> the .htaccess<\/em><\/strong> file.<\/p>\n\n\n

      \n
      \"Deleting<\/figure><\/div>\n\n\n

      Then, revisit the WordPress page that was displaying the 403 Forbidden error. If it’s now working, you’ve identified the problem.<\/p>\n\n\n\n

      Next, you’ll need to generate a new .htaccess<\/strong><\/em> file. To do this, go to Settings<\/strong> ><\/em> Permalinks<\/em><\/strong> in your WordPress dashboard:<\/p>\n\n\n

      \n
      \"Regenerating<\/figure><\/div>\n\n\n

      Scroll down to the bottom of the page and hit Save Changes<\/strong><\/em>. There’s no need to change any settings – just click the Save Changes<\/em><\/strong> button. This will generate a new .htaccess<\/em><\/strong> file for your site.<\/p>\n\n\n

      <\/div>\n\n\n\n

      6. Update your file permissions \ud83d\udd12<\/h3>\n\n\n\n

      Another potential cause of the WordPress 403 forbidden error is incorrect file permissions<\/a>. That means you may need to update those permissions. This method also involves file management, so only proceed if you’re an experienced WordPress user and you’ve backed up your site.<\/p>\n\n\n\n

      Connect your site to an FTP client (as in the previous method). Then, find your public_html<\/em><\/strong> folder and right click on it:<\/p>\n\n\n

      \n
      \"Accessing<\/figure><\/div>\n\n\n

      Select File Attributes<\/em><\/strong>:<\/p>\n\n\n

      \n
      \"Updating<\/figure><\/div>\n\n\n

      In the pop-up window, find the Numeric value<\/em><\/strong> field and input “750” or “755” (depending on what’s already there). Then select the Recurse into subdirectories<\/em><\/strong> box and the Apply to directories only<\/strong><\/em> option, and hit OK<\/strong><\/em>.<\/p>\n\n\n\n

      Next, right click on your public_html<\/em><\/strong><\/em> folder again and open File Attributes<\/strong><\/em>:<\/p>\n\n\n

      \n
      \"Changing<\/figure><\/div>\n\n\n

      This time enter “644” for the Numeric value<\/strong><\/em>, and only select Recurse into subdirectories<\/em><\/strong> and Apply to files only<\/em><\/strong>. Hit OK<\/strong><\/em>, and test your site to see if the 403 error is resolved.<\/p>\n\n\n

      <\/div>\n\n\n\n

      7. Contact your web hosting provider \ud83d\udcde<\/h3>\n\n\n\n

      If none of the above strategies helped you resolve that pesky WordPress 403 Forbidden error, or if you don’t have the technical skills to attempt some of them, you can always contact your web hosting provider for help. <\/p>\n\n\n\n

      Depending on your hosting plan, you may be able to reach out via chat, email or telephone.<\/p>\n\n\n\n

      If you don’t find your host’s support to be very helpful, switching to a high-quality WordPress host<\/a> might be able to help you fix the problem (and prevent issues in the future).<\/p>\n\n\n

      Go to top<\/a><\/div>\n\n\n\n

      Fix the WordPress 403 Forbidden error for good \ud83d\udee0\ufe0f<\/h2>\n\n\n\n\t\t
      <\/div>\n\t\t\t
      \n\t\t \t
      \n\t\t \t\tHow to fix \ud83d\udc68\u200d\ud83d\udd27 the #WordPress #403 forbidden error \ud83d\udc1e\ud83d\udc1e\ud83d\udc1e<\/a>\n\t\t \t<\/div>\n\t\t \t
      \n\t\t \tClick To Tweet \n\t\t \t\t<\/span>\n\t\t \t<\/a>\n\t\t <\/div>\n\t\t<\/div>\n\n\n\n

      Whether you’re a WordPress developer or you run a small online business, facing the WordPress 403 Forbidden error can be a huge inconvenience. That’s because it may mean you’re locked out of the WordPress admin dashboard or you can’t access an important page.<\/p>\n\n\n\n

      Fortunately, there are quite a few ways you can troubleshoot this problem. For starters, you can clear your browser cache, deactivate your plugins one by one, turn off your CDN, and disconnect from your VPN. If the issue persists, you can try restoring your .htaccess<\/strong><\/em> file or updating file permissions. As a last resort, you can get in touch with your hosting provider for assistance.<\/p>\n\n\n\n

      Do you have any questions about fixing the WordPress 403 Forbidden error? Let us know in the comments section below!<\/em><\/strong><\/p>\n\n\n