1.500 Internal Server Error! What Is This?1) Last night you saw that your site was working completely fine. But now, today morning you find error 500. Why this error?
Corrupt.htaccess file is the main reason of a 500 Internal Server Error message. There can be some other additional causes, like conflicting plugin or theme, or even a corrupt WordPress installation. Other than this, PHP memory limits can also be one of the reasons.
Well, check out this easiest way to fix this error- Check your website’s error_log.
For more solutions, you can also enable WP_DEBUG.Procedure:
Open up your wp-config.php file, and write down the following line of code:
And replace it to: define(‘WP_DEBUG’, true);
It is well known that the most likely error cause is .htaccess file, so let’s know how to handle it on the first side.
Get the FTP access on your server
Navigate to the root directory of your WordPress installation
Locate the .htaccess file. Rename the file to .htaccess_old
Reload your website.
Your website will start working! After completing this, now you can generate a new .htaccess file simply by moving on to-
Settings–>Permalinks in your WP admin panel and re-saving the settings.
Moreover, plugins and themes can also get deactivated. You may need to do this also, because sometimes a 500 Internal Server Error can be caused by a faulty plugins or themes.
Apart from all these, you should try increasing your PHP Memory Limit, so that the memory limit should not be the case of this 500 internal error.
For detailed instructions on memory limits, check out the WordPress Codex.What if, this all doesn’t work?
All you have to do than, is to grab a fresh copy of WordPress from the official site, and then re-upload the wp-admin and wp-includes directories.
2)White Screen of Death! Read about this-What is White Screen of Death?
The name indicates that, whenever you open your website, you will find only a blank page on the screen.
Why is it so?
Well reason can be anything! But the most common is the compatibility issue with a plugin or a theme. Incompatibility issue can itself have many different faces. Like-
A plugin may have a disagreement with another plugin, or
The plugin is not compatible with the latest version of WordPress. Likely, the theme will also face compatibility issues with WordPress after an update.The Solution
The first thing you need to do is to isolate your plugins’ directory. To work on this solution, follow the steps below:
Navigate to the root of your WP installation via FTP
Head to /wp-content
Locate the folder named “plugins” and rename it “plugins_old”
Create a new folder named “plugins”.
Doing this, will detach all your plugins, and after this if your website gets started working, then it indicates one of your plugins is at fault. While doing this step, make sure that you do not open your plugins page, otherwise the all plugins will get deactivated.
To know which one plug-in is causing the WSOD, copy individual plugin files from “plugins_old” to plugins”, one by one.
Now to fix the issue for themes, remember these below steps:
Navigate to /wp-content/themes, and then rename the folder of the active theme.
Open up your WP admin panel, and head to the Themes page.
So now, depending on your WP installation version, the issue fixed will cause WP to fall-back to the default theme.
3) Maintenance Mode Error! What Is It?
Maintenance mode error comes every time you update your old WordPress to a newer version. When you update the old version, it makes a temporary .Maintenance file. The issue comes, if you will not be deleting the .Maintenance file after the up-gradation.The Solution-
You will need to login to your WP root directory via FTP. Thereafter, you can locate the .Maintenance file and delete it. This will resolve the error.
4) Error Initializing A Database Connection
This error means, you are trying to access the database and the Wordpress is facing some problem.What Is The Cause?
It can be an issue with the wp-config.php file — the details which you have entered in your database are incorrect.What actually happens?
All the shared web host servers keep limits on the databases, if you ever cross that allotted limit, then of course you will receive this connection error. The other reason than this is, webserver down. Moreover, hacking can be the other issue!if your website gets hacked, it can lead to database connection issues.The Solution
Open wp-config.php file
Locate the file using FTP, and open it
Get ensure that database details are correct. Check for database name, username, password and database host.
5) Oops! Connection Timed Out
This is an error which is received from an overloaded server or the server which is configured badly. This error takes place, when the website’s server is too overloaded and unable to complete its browser’s request.The Solution-
Deactivate your plugins.
If deactivating the plugins solves an issue, try re-activating them all one by one to see which plugin is causing the connection timed out issue. However, if the problem is lying related to the current theme, then the best way to cure is, activate the default WP theme.
Use the wp-config.php file to increase your PHP memory limit. Open up the file, and add the below code given:define(‘WP_MEMORY_LIMIT’, ’64M’);
This will help you to increase maximum of the memory limit, i.e. up to 64 MB. One thing you need to make sure about, if you are on a shared web host, then you may not be allowed to increase your memory limit after a certain point. To overcome from this situation, you need to contact your web host to increase the memory limit for you.
Note- Maximum of the shared hosting providers, keep the PHP memory limit as low as 8 MB.
6) Error 145! This One Is Critical
Error 145 indicates that your WordPress database is damaged or corrupted.The Solution
To fix this error, one of the easiest ways is to repair your WP database using phpMyAdmin.How to Do?
Login to phpMyAdmin
Choose your WP database
Select the checkboxes next to tables that you wish to repair
After selecting, choose the “Repair Table” option from the drop-down menu right below the list of tables.
7) Error 28- Fix it!
This error is all about MySQL error, and has nothing to do with WordPress. Even Drupal, Joomla or other CMS’ websites can this error 28.Why This Error Occur?
Error 28 can come up, if the cache on your web server is full, or you have too many files stored in your /tmp directory.The Solution
To fix this bug, all you have to do is, empty your /tmp directory. Or else, try to get connected with your web host to help you resolve the cache related issues quickly.
8) Warning: Cannot Modify Header Information — Headers Already SentWhat this error mean?
Sometimes, you may face an error that show you the following line-“Warning: Cannot modify header information — headers already sent by (output started at /path-to-something-directory/some-config-file:xyz )”. Why It Occurs?
The reason behind this error is, the un-required spaces in the mentioned WordPress file (generally, it is the wp-config.php file). For this, you need to edit the concerned file to remove the unnecessary whitespaces.The Solution
Download the file that is shown in the error (say, wp-config.php)
Open it using any editor you wish to
Ensure that there are no spaces either before tags.
Overall, the first letters of the file should contain (with absolutely no spaces between ‘?’ and ‘<’ or ‘>’ either).
The main reason of this error is due to spaces in the wp-config.php file. It can be some other file too, but all you need to do is— just read out the error carefully, as it specifies the file name and the path to the concerned file.
9) Warning: File_Get_Contents! Did You Find This Error?Warning: file_get_contents (http://www.url.com/url) [function:file-get-contents]: failed to open stream on line xyz
At most of the time, the reason this error occurs is because your web host has restricted you with strict security settings in the PHP configurationThe Solution
If you wish to access to php.ini file, you can fix this issue on your own. All you need to do is, Open the file and locate the following line:allow_url_fopen = Off
Now change the “off” value to “on”, as follows:allow_url_fopen = On
If you are not willing to access your php.ini file, you are indeed to contact your web hosting provider. So contact him and ask to enable allow_url_fopen. Also, if you found this error like, “failed to open stream: no such file or directory in…”, it indicates that the mentioned file is either missing or not readable.