HTTP error code

Error HTTP 404:

Typically 404 errors are caused by a missing file or a non-existent page. So check if the file is present on the hosting. (You can check by FTP or from the file manager in cPanel)

In addition, if you are contacting a file containing a capital letter, make sure the capitalization is also present in the query. (It’s “Case Sensitive”)

It is also possible that a rewrite rule causes a problem with the “.htaccess” which will make the resource unavailable. In order to test, rename the “.htaccess” file temporarily.

If you have 404 errors on all pages of a site, but not on the home page, this indicates a problem with URL rewrite, as the CMS expects to receive a URL of some sort way and he receives it in another form.

WordPress Tip: Add the following code to your “.htaccess”.

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPres

In summary, The 404 are caused by: 1. Missing file 2. Non-existent page 3. Sensitive to the box 4. Rewriting rule

Error HTTP: 403

403 errors are usually caused by a file rights issue.

They will often be caused by a 0777 right on shared servers and HybridCloud servers using SuPHP.

The files must use the right 0644 and the folders 0755

Binary files or files that use a handler other than PHP (example: python, SH, Perl, etc.) must use 0755 rights.

It is also possible that the 403 error is caused by rules in a .htaccess file, in order to validate this, you can rename the .htaccess files temporarily from the folder that contains the source to 403 error and get off a folder both to determine the .htaccess that causes the problem.

Please note that .htaccess rules will affect all child folders where the file is located. So it's important to check all the parent .htaccess right down to the root of the hosting / home / UsernameCpanel.

Les bons droits à utiliser:

Fichiers: 0644

Dossiers: 0755

Binaires ou autres: 0755

Error HTTP :501

The 501 errors are encountered when a feature is unsupported by the server or when a ModSecurity rule is triggered. In order to determine the exact reason, you can try to check the error log apache.

If you have no errors, it is probably ModSecurity that is triggered by one of your scripts. To determine if ModSecurity is causing a problem. You can disable it temporarily into your cPanel.

However, be aware that ModSecurity is set up to add an additional layer of security. So if you disable it, you reduce the level of protection. If the error is returned by ModSecurity. You can contact support so that it determines which rule is triggered to disable it. Here’s how to disable a mod_security rule in the .htaccess:

#Désactiver une règle seulement.
SecRuleRemoveById 123456

#Désactiver ModSecurity complètement
SecFilterEngine Off
SecFilterScanPOST Off

Error HTTP: 500

Our servers are configured to maximize your security and that of your data. We have set up servers with SUPHP. If you get a 500 error, we invite you to change the CHMOD of your files: 755 for the files and 644 for the PHP files. You can do this very easily with the FileZilla FTP software (available for free) or via your cPanel (with the file manager).

Generally, 500 errors are server errors due to the configuration of this one and in 90% of the cases, the configuration error comes from a .htaccess file.

So you can test by renaming the .htaccess file to the root and going down into folders until scripting.

Updated on 18 August 2021

Was this article helpful?

Related Articles