{"id":4192,"date":"2021-01-05T18:36:49","date_gmt":"2021-01-05T18:36:49","guid":{"rendered":"https:\/\/chemicloud.com\/kb\/?post_type=ht_kb&p=4192"},"modified":"2024-10-16T09:37:46","modified_gmt":"2024-10-16T09:37:46","slug":"fix-the-wordpress-white-screen","status":"publish","type":"ht_kb","link":"https:\/\/chemicloud.com\/kb\/article\/fix-the-wordpress-white-screen\/","title":{"rendered":"How To Fix The WordPress White Screen of Doom"},"content":{"rendered":"

You’ve probably seen it before – the dreaded white screen of doom in WordPress and named as such because it’s a white screen and your WordPress site just appears dead.<\/p>\n

\"\"<\/p>\n

On rarer occasions, you may see a critical error message instead of the white screen of doom:<\/p>\n

\"\"<\/p>\n

The error is still the same whether you see a white screen or a critical error message. This can happen for a few reasons, including bad themes and plugins or if there’s an issue with the webserver. Due to the variety of causes for this error, troubleshooting it can take some time.<\/p>\n

Below, our troubleshooting tips should get you up and running quickly if you encounter this error!<\/p>\n

#1 Is the problem happening on other WordPress Sites you have at the same host?<\/h3>\n

Suppose other WordPress sites that are hosted under the same account at your web host are also having this problem. In that case, you should reach out to our Happiness Engineers if you host with ChemiCloud, and if you don’t, you should contact your web host and ask if there are any server-related problems + let them know you’re getting the white screen of doom in WordPress.<\/p>\n

#2 Increase Your Memory Limit<\/h3>\n

Sometimes you might be trying to do too many things at once and exhaust, or use up, all the available memory. For example, if you are trying to upload too many files to your media library at the same time, you may encounter this white screen of doom.<\/p>\n

We have a great guide on how to increase the PHP Memory Limit in cPanel here<\/a>.<\/p>\n

#3 Deactivate All Your Plugins<\/h3>\n

If you’ve previously increased your memory limit to 512M or even 1G or 2 G, and your WordPress site still didn’t back, you need to check, you will need to do some further troubleshooting.<\/p>\n

If you can’t get into your wp-admin because of the ‘white screen of doom’, the steps below will help you. Regrettably, WordPress doesn’t have a way to deactivate all plugins with the click of a mouse.\u00a0 To do this, you’ll need to use the File Manager in your cPanel.<\/p>\n

Step 1:<\/strong> Login to your cPanel. There’s a lot of ways to do this, but the sure-fire easiest way is to login to your Client Area, then open your cPanel.<\/p>\n

\"\"<\/p>\n

Step 2:<\/strong> Once your cPanel is open, look for and open the File Manager under the Files section.<\/p>\n

\"\"<\/p>\n

Step 3:<\/strong> Once the file manager opens, navigate to the directory where your WordPress configuration is installed. This is most likely in your public_html folder.<\/p>\n \t\t

\r\n \t\t\tImportant Tip:<\/span> \t\t\t \t\t\t\t

\r\n \t\t\t\t\tBe sure to click the icons to the left of the files\/folders you wish to open, otherwise their text will turn blue and you will be given the option to rename them. Should this happen, no worries, just click in the whitespace anywhere on the page to exit the edit mode and try again. \t\t\t\t<\/p>\r\n \t\t\t \t\t\t\r\n \t\t<\/div>\r\n \t\t\n

Step 4:<\/strong> In your File Manager, open the folder called wp-content:<\/p>\n

\"\"<\/p>\n

In your wp-content folder, look for another folder called Plugins.<\/p>\n

\"\"<\/p>\n

Right click the folder, then choose Rename.<\/p>\n

\"\"<\/p>\n

Step 5:<\/strong> To deactivate all plugins at once, rename the plugins folder to something like “plugins.deactivated” just without the quotes.<\/p>\n

\"\"<\/p>\n

Once you select Rename File, your plugins will be deactivated. Now you can return to your WordPress site and see if you can log in to your wp-admin area without issue.<\/p>\n \t\t

\r\n \t\t\tGood To Know:<\/span> \t\t\t \t\t\t\t

\r\n \t\t\t\t\tWhen you login to your wp-admin area after renaming the Plugins folder, your WordPress site is going to panic a bit. Don’t worry. Your plugins and the way they were configured are still there. You’ve only renamed the folder in which the plugins are installed. \t\t\t\t<\/p>\r\n \t\t\t \t\t\t\r\n \t\t<\/div>\r\n \t\t\n

Essentially, WordPress looks for the Plugins folder to run plugins that are installed, and let’s face it, you probably have plugins. When WordPress can’t find the Plugins folder, it deactivates all plugins.<\/p>\n

Step 6:<\/strong> Now, you need to return to the File Manager, open your public_html folder, then the wp-content folder, just as before, except you need to rename the Plugins folder back to Plugins.<\/p>\n

\"\"<\/p>\n

Next, rename the folder ‘plugins’, but without the quotes, and click Rename File.<\/p>\n

\"\"<\/p>\n

Step 7:<\/strong> Now, return to your wp-admin and go to Plugins. Then, one by one, enable your Plugins until your site displays the Internal Server Error.<\/p>\n

When that happens, you know which plugin is causing the issue. Repeat the process above to deactivate all plugins, then when you are able to get back into your wp-admin, delete that plugin before re-activating it.<\/p>\n

Struggling with WordPress troubleshooting? ChemiCloud is the hosting solution designed to save you time and money! <\/b>\ud83e\udd13<\/span> Try our <\/b>Managed WordPress Hosting<\/b><\/a> plans for just $1!<\/b><\/p>\n

If that solved your problem, congrats!\u00a0If not, keep reading!<\/p>\n

#4 Use WordPress Recovery Mode<\/h3>\n

Back in WordPress 5.2, the developers introduced fatal error protection<\/a>. Sometimes WordPress can catch an error and stop it in it’s tracks, especially if it’s with a plugin.<\/p>\n

In the event you see an error that says:<\/p>\n

\"\"<\/p>\n

You should receive an email to your admin email address with more details.<\/p>\n

The email will say something to the effect of:<\/p>\n

Howdy!<\/em><\/p>\n

Since WordPress 5.2, there’s a built-in feature that detects when a plugin or theme causes a fatal error on your site.\u00a0<\/em><\/p>\n

In this case, WordPress caught an error with one of your plugins: <Plugin Name><\/em><\/p>\n

The email will also contain a special link that will allow you to get into your \/wp-admin so you can disable that wonky plugin and get your site back up and running.<\/p>\n

#5 Clear Your \/wp-cache<\/h3>\n

If you’re hosting with ChemiCloud, you’re running on LiteSpeed Servers and should have the LiteSpeed Cache Plugin<\/a> installed in your WordPress to benefit from the speed of our servers truly.<\/p>\n

To clear your LiteSpeed Cache, login to your \/wp-admin and look for the LS logo at the top. Hover over the logo and click Purge All.<\/p>\n

\"\"<\/p>\n

Now, please return to your website and try to open it. If it works, congrats! If not, keep trying with the next step below.<\/p>\n

#6 Enable Debug Mode<\/h3>\n

If the steps above haven’t helped, the next step would be to enable debug mode and read through it’s output to locate the exact cause of the issue. Use the steps below to edit your wp-config file and enable debug mode.<\/p>\n

Step 1:<\/strong> Login to your cPanel. There’s a lot of ways to do this, but the sure-fire easiest way is to login to your Client Area, then open your cPanel.<\/p>\n

\"\"<\/p>\n

Once your cPanel is open, look for the Files section and open the File Manager.<\/p>\n

\"\"<\/p>\n

Step 2:<\/strong> Once the file manager opens, navigate to the directory where your WordPress configuration is installed. This is most likely in your public_html folder.<\/p>\n

\"\"<\/p>\n

Step 3:<\/strong> Look for the wp-config file in the listing of files. Single-click the icon to the left of the file to select it.<\/p>\n \t\t

\r\n \t\t\tImportant Tip:<\/span> \t\t\t \t\t\t\t

\r\n \t\t\t\t\tBe sure to click the icons to the left of the files\/folders you wish to open, otherwise their text will turn blue and you will be given the option to rename them. Should this happen, no worries, just click in the whitespace anywhere on the page to exit the edit mode and try again. \t\t\t\t<\/p>\r\n \t\t\t \t\t\t\r\n \t\t<\/div>\r\n \t\t\n

Next, using your mouse, right-click on the file, then choose Edit from the menu.<\/p>\n

\"\"<\/p>\n

You will see a warning like the one below:<\/p>\n

\"\"<\/p>\n

95% of users can proceed and click Edit.<\/p>\n \t\t

\r\n \t\t\tWhat if I'm in that 5% of users who can't click edit?<\/span> \t\t\t \t\t\t\t

\r\n \t\t\t\t\tContact our support and let them know you installed your WordPress installation using a utf format other than utf-8 and we can help you out! Your native language, or at least the language in which you installed WordPress, probably isn’t based on the Roman Alphabet. \ud83d\ude09 Not to worry, we are all international here and can get you sorted! \t\t\t\t<\/p>\r\n \t\t\t \t\t\t\r\n \t\t<\/div>\r\n \t\t\n

A new tab in your browser will spawn and you will see the codebase that outlines the structure of this themes wp-config.php file. If it feels overwhelming, don’t worry, we’re only looking for the section below:<\/p>\n

\u00a0* For developers: WordPress debugging mode.\r\n*\r\n* Change this to true to enable the display of notices during development.\r\n* It is strongly recommended that plugin and theme developers use WP_DEBUG\r\n* in their development environments.\r\n*\r\n* For information on other constants that can be used for debugging,\r\n* visit the documentation.\r\n*\r\n* @link https:\/\/wordpress.org\/support\/article\/debugging-in-wordpress\/\r\n*\/\r\ndefine( 'WP_DEBUG', false );<\/pre>\n
To enable debug mode, change the false on the last line to true. Be sure to leave the space at the end.<\/p>\n
We can find the information we need to correctly complete this section of our wp-config.php file from our cPanel.<\/p>\n
Step 4:<\/strong> Keeping the tab with the wp-config.php code open, go to the other tab where your cPanel File Manager is open, and click the CP logo in the top left to return to the main cPanel screen.<\/p>\n
\"\"<\/p>\n
Once you’re on the main cPanel screen, look in the Database section (3rd from the top) and click MySQL Databases to open this section.<\/p>\n
Click the Save button in the top right corner to save your changes, otherwise, you’ll need to reenter this information.<\/p>\n
\"\"<\/p>\n
Now, open a new tab in your browser and try to load your website. If it works, great! You solved your issue! Congrats! \u270b\ud83c\udf89<\/p>\n
If this didn\u2019t resolve your issue, we suggest you open a ticket with our Happiness Engineers so they can investigate further.<\/p>\n
If the steps above didn\u2019t solve your issue, you might need to restore the database and site files from a backup if you have one available.<\/p>\n
If you\u2019re a ChemiCloud customer, you can rest easy! All our WordPress hosting<\/strong> plans come with 30 day daily offsite backups allowing them to be quickly restored.<\/p>\n
\n
If you enjoyed this tutorial, then you\u2019ll love our support! All ChemiCloud\u2019s hosting plans include 24\/7 support from our fantastic support team.<\/p>\n<\/div>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
You’ve probably seen it before – the dreaded white screen of doom in WordPress and named as such because it’s a white screen and your WordPress site just appears dead. On rarer occasions, you may see a critical error message instead of the white screen of doom: The error is…<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"ht-kb-category":[34],"ht-kb-tag":[],"class_list":["post-4192","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-troubleshooting"],"_links":{"self":[{"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb\/4192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/comments?post=4192"}],"version-history":[{"count":6,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb\/4192\/revisions"}],"predecessor-version":[{"id":8493,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb\/4192\/revisions\/8493"}],"wp:attachment":[{"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/media?parent=4192"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=4192"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/chemicloud.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=4192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}