{"id":16014,"date":"2021-08-20T17:11:45","date_gmt":"2021-08-20T14:11:45","guid":{"rendered":"https:\/\/vipestudio.com\/?p=16014"},"modified":"2021-08-20T17:11:45","modified_gmt":"2021-08-20T14:11:45","slug":"fixing-a-403-wordpress-error-is-as-easy-as-1-2-3","status":"publish","type":"post","link":"https:\/\/vipestudio.com\/en\/fixing-a-403-wordpress-error-is-as-easy-as-1-2-3\/","title":{"rendered":"Fixing a 403 WordPress Error Is as Easy as 1-2-3!"},"content":{"rendered":"

It\u2019s a bright sunny day. Your coffee is hot and you are in a good mood to make some changes to your fantastic WordPress site. But then bam! You see this default boring page showing \u201c403 Forbidden\u201d<\/strong> instead.<\/p>\n

Now, now, there is no need to panic or get frustrated. Vipe Studio<\/a>, as one of the best WordPress agencies for development, will help you to troubleshoot this error<\/strong> and get your website back working again.<\/p>\n

\"\"<\/p>\n

Knowing What 403 Forbidden Error Is<\/h2>\n

When you see this error instead of the lovely homepage of your WordPress site, it indicates that your web server acknowledges your browser request to view the website, but, alas, this will not be fulfilled. In another way, the 403 Forbidden error basically means that your server fully understands what you are trying to do, but it \u2018forbids\u2019 you to do it<\/strong> because you lack the necessary permission to do so.<\/p>\n

It\u2019s as if you\u2019re attempting to get into an awesome (yet, private) party, but somehow your name was mistakenly erased off the attendee list. Imagine how bummed you\u2019ll be!<\/p>\n

\"\"<\/p>\n

So What Is the Reason for This Unpleasant Error?<\/h2>\n

The two most common causes for the 403 Forbidden Error in WordPress are:<\/p>\n

    \n
  1. A misconfigured\/corrupt .htaccess file.<\/li>\n
  2. The incorrect website file and\/or folder permissions.<\/li>\n<\/ol>\n

    Now that you understand the error and the possible culprits that are causing it, here comes the fixing part!<\/strong><\/p>\n

    \"\"<\/p>\n

    1. File and Folder Permissions<\/h2>\n

    According to WordPress Codex, it\u2019s recommended to set your file permissions to 644 or 640<\/strong> and your website directories to 755 or 750<\/strong>. However, please keep in mind that we have an exception to this rule which applies to your wp-config.php file that should be set to 440 or 400.<\/p>\n

    Now let\u2019s make sure your WordPress files and directories are set to the correct permissions as above.<\/p>\n

    Normally, you can access your files using an FTP\/SFTP connection. In this case, we will use Filezilla as it is one of the most common FTP clients.<\/p>\n

    To set the proper permissions<\/strong>, right-click on the folder where your WordPress site is located (often, it\u2019s set to public_html). Then, choose \u201cFile Attributes\u201d. Fill in \u201c755\u201d or \u201c750\u201d in the numeric value field. Don\u2019t forget to also choose \u201cRecurse into subdirectories\u201d (so that you don\u2019t have to apply this change to every folder within your site) and \u201cApply to directories only\u201d.<\/p>\n

    Yay!<\/strong> One step down, and now we move on to set the File permissions. Click on any file in your site directory. Again, fill in \u201c644\u201d or \u201c640\u201d in the numeric value field. Tick the \u201cRecurse into subdirectories\u201d option but this time choose \u201cApply to files only\u201d.<\/p>\n

    Last but also the most important part, you will need to manually adjust the permissions for your wp-config.php file<\/strong> to make it \u201c440\u201d or \u201c400\u201d. This will help to keep your site safe from any naughty attempts to hack your site.<\/p>\n

    That\u2019s all there is to it; If the incorrect file permissions were indeed the culprit of the 403 error, your WordPress site should be back to normal again.<\/p>\n

    \"\"<\/p>\n

    2. Broken or Corrupt .htaccess File<\/h2>\n

    If your hosting is using the Apache web server<\/strong>, then you will find an .htaccess file as a basic configuration file on your WordPress site folder. It is such a vital part of your site and if the file is not configured properly, even a minor typo can result in a major problem, such as the 403 Forbidden message.<\/p>\n

    The easiest way to solve the 403 issues<\/strong> caused by .htaccess file misconfiguration is to do the following:<\/p>\n

      \n
    1. Access your files using FTP\/SFTP.<\/li>\n
    2. Navigate to your root folder and locate the .htaccess file.<\/li>\n
    3. Keep a backup of the file, just in case, and download it to your local computer.<\/li>\n
    4. Delete the current .htaccess file from your server.<\/li>\n<\/ol>\n

      If your .htaccess file is the one that’s causing the 403 error, your WordPress site should now be loading again.<\/p>\n

      Now we will need to replace the deleted .htaccess file by forcing WordPress to create a brand new one. The steps are:<\/p>\n