This code means “Forbidden”. This means the server understood the request, but is refusing to fulfill it. This usually occurs due to some type of permissions issues in your server.


Your site is returning a 403 error because of corrupted .htaccess file. Your site is returning a 403 error because file permissions are not correct on your index files. This users meant to requesting access to something but the server recognizes it as something they’re forbidden from and as a result, the server is refusing their request.

If you see a 403 on your site, you would want to make sure that you have a valid index file. This file usually exist in the public_html in the root of your server. If the 403 error continue to occur then it is a best idea to contact your Hosting Support.



This code means “Not found”. That’s it. It’s simple. Whatever you’re looking for isn’t in the location you are looking. If you see this error all you need to do is check the URL being requested and see if the file being requested exists.


If you see this error when browsing to any of your WordPress pages, something like yourdomain.com/contact-us, then you need to make sure that the page is really exist in the list of your pages. You can check it by going through yourdomain.com/wp-admin/edit.php?post_type=page.

Problems with .htaccess files
This is a configuration file used by the Apache web server in the root directory which can, amongst other things, control redirections, protect your directories and rewrite URLs.
In many cases, 404 errors can be resolved by regenerating this file. One easy fix for this by reflushing the permalinks by going through yourdomain/wp-admin/options-permalink.php. If this error / issue continue to occur then it is the best idea to contact a support group, that’s why Personalwphelper (us) is here to help you to investigate further :).


This means “Internal Server Error”. This might sound scary, but it’s actually pretty simple. This does not mean there is a problem with the web server itself. If we break it down into simpler to understand context then it sounds something like this. The server was unable to complete the task being requested of it. Typically this is because the your website has some invalid
code that is confusing the server. 500 errors will look different depending on the type of web server and hosting provider. Some people customize these pages and others do not. The important part is the status code, aka 500.

The most common cause of a 500 error is a .htaccess file that is not coded properly. How do you know if a .htaccess is coded properly? The answer is simple. You just have the disable the file by changing it’s name to anything other than .htaccess. This file usually exist in the root of your server along with WordPress core files and folder (wp-content , wp-admin, wp-include inside the public_html directory.

Using an FTP Client
An FTP client allows you to access and edit your site’s files. You can use the File Manager your host uses, of course, but an FTP client of your choosing is often easier to use.

Once you find your .htaccess file, right-click it, and rename it “.htaccess.bak”. This essentially deletes your site’s .htaccess file, so we need to create a new one. Go into your WordPress admin area. Hover over Settings, and select Permalinks. Scroll down to the bottom of the page, and click Save Changes.

Default PHP Memory Limit in WordPress
PHP memory limits are set by your host and WordPress. WordPress will attempt to increase your limit if you begin exceeding it, but it can only go as high as the limit your host has placed on your server. This limit is often lower for shared hosting plans. You need to increase your PHP memory limit in WordPress and refresh your site to test whether or not this is causing your 500 internal server error.

Once again open your root directory of your server usually /public_html, and locate your wp-config.php file. Right-click on it and select Download to download it to your computer. Open the file in your preferred text editor, and add this bit of code under the opening PHP tag:


define(‘WP_MEMORY_LIMIT’, ‘128M’);
Save the file, and re-upload it to your root directory, overwriting the original file. Refresh the client, and refresh your site. If you still see the error, you are not having PHP memory limit issues. Remove the above code from the wp-config.php file on your computer, save it, and re-upload it to your root directory. The the corrupted .htaccess file and increasing a site’s PHP memory limit are 2 most common to fix this error but we can still go by investigating further. Needing our help? you can contact us here.