If you encounter this issue, you’ll need to do a manual WordPress upgrade<\/a>.<\/p>\n Sometimes WordPress gets stuck at:<\/p>\n It means that a To do this manually, you’ll need to log in to your site using an FTP client or via your hosting dashboard (cPanel, Plesk, etc) and delete The white screen of death in WordPress is a possible culprit if you attempt to:<\/p>\n In many cases, the plugin that has just been installed or modified could result in a conflict with your current theme or other plugins. That’s why it’s important to use WordPress products developed using best practices.<\/p>\n Try to disable any recently modified or installed plugins and see if your WordPress goes back to normal. <\/p>\n In case your dashboard isn’t operational at all, you can disable plugins in WordPress using FTP access. A caveat is that you’ll only be able to do this if you have access to your FTP with the required directory permissions. Most hosting companies provide FTP service. However, if WordPress is installed on a Virtual Private Server or you’re with a managed host<\/a>, you might not have an FTP server. <\/p>\n You may need to install an FTP client, such as FileZilla<\/a>. <\/p>\n To disable the plugin:<\/p>\n Reopen your browser and see whether your site loads. Use the above steps to disable as many plugins as you need to in order to combat the white screen of death in WordPress.<\/p>\n Alternatively, you can disable all of your WordPress plugins simultaneously. Here’s how:<\/strong><\/p>\n Disabling all your plugins one by one could take you a longer while. Instead, you can rename the main Then, create another folder called If your case of the white screen of death in WordPress was caused by a particular plugin’s modification, disabling the plugin through your FTP server should resolve the problem. As a rule of thumb, test all your modified plugins using a backup site<\/a> before launching on your main WordPress.<\/p>\n Just like the white screen of death caused by plugins above, disabling the theme can resolve any WSOD problems that are theme-related. The following are some common causes and solutions:<\/p>\n New themes can cause a conflict with existing plugins. In this case, deactivate the newly installed theme, which will cause WordPress to revert to your automatic default theme. Ensure that the default theme hasn’t already been deleted. If so, upload it back to your themes folder within To disable the theme, follow the same procedure described above for plugins, except this time working with the A major WordPress update oftentimes can drive poorly coded themes out. Poorly-coded or outdated themes will often not work once the latest WordPress update is installed.<\/p>\n If you notice that the white screen of death in WordPress appeared immediately \/ soon after conducting an update, your old theme is mostly likely to be the reason behind it. Deactivating your theme as described above could turn things back to normal.<\/p>\n WordPress isn’t a fan of buggy coding. Its proper working depends on a set of well-built objects operating in harmony. If one of those parts is missing or malfunctions, your WordPress will fail to work, resulting in the WSOD.<\/p>\n Themes made by reputable theme shops (shameless plug<\/a>) and those found in the WordPress.org repository are comprehensively tested for any defects. If your white screen of death in WordPress comes after installing any of such themes, the problem could be a plugin-theme conflict.<\/p>\n Modifying or updating themes by hand could cause occurrence of improper coding, which is the heart of most WSOD problems. Try to replace the modified file with an old copy from your backup. Otherwise, you should download and reinstall original theme files.<\/p>\n This is a classic indication that your site has grown beyond what your current hosting provider gives you<\/a>. Higher amounts of traffic to your site demand higher memory limits, so you should plan to upgrade accordingly.<\/p>\n Start by increasing your PHP memory allocation<\/a> by adding or editing this line in your For shared hosts, a memory limit of 64MB is sufficient. Consult the hosting provider if the problem persists after making this alteration.<\/p>\n Cheap web hosting<\/a> can also come at the expense of quality. Such providers want to ensure that they get as many customers within a single server as they can. Therefore, the resources allocated to every client are very limited, for example RAM. If you can’t increase your memory limit, you’ll need to upgrade to the next plan to stop the white screen of death in WordPress from occurring.<\/p>\n In the end, most WordPress users and admins will be faced with the infamous WSOD at one point or another in their lives. This problem won’t arise from the WordPress core itself, but with using themes and plugins not coded with WordPress best practices in mind, user errors, or hosting limitations.<\/p>\n If you don’t want to worry all that much about this white screen of death, you should first go for quality WordPress hosting provider<\/a>. A good company will sort out any potential problems as they arise, ensuring that your downtime is kept at a minimum.<\/p>\n It’s important to stay positive and remember that there’s a solution to every situation that you face.<\/p>\nCause #2: Maintenance mode freeze<\/h2>\n
![\"white](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2016\/07\/maintenance-error.png\")
<\/p>\n.maintenance<\/code> file, which WordPress automatically installs when it starts updating, hasn’t been removed.<\/p>\n.maintenance<\/code>, located in your website root folder.<\/p>\nCause #3: Problems with plugins<\/h2>\n
\n
\n
wp_content\/plugins<\/code><\/li>\nmy-bad-plugin<\/code> name it _my-bad-plugin<\/code> or my-bad-plugin_disabled<\/code>. Choose any name provided it doesn’t sound like any other plugin’s name and you can remember it later<\/li>\nplugins<\/code> folder to something else, e.g. from wp_content\/plugins<\/code> to wp_content\/plugins_old<\/code>. This should disable all your plugins simultaneously.<\/p>\nwp_content\/plugins<\/code>. You can activate each plugin by moving them to the new plugins folder.<\/p>\nCause #4: Problems with themes<\/h2>\n
a) Problems when installing a new theme<\/h3>\n
wp_content\/themes<\/code>.<\/p>\nwp_content\/themes<\/code> folder rather than the plugins<\/code> folder. Rename the specific theme’s folder, which automatically deactivates the theme.<\/p>\nb) Problems with badly coded themes<\/h3>\n
![\"500](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2016\/07\/500-error.png\")
<\/p>\nc) Problems with theme modification<\/h3>\n
Cause #5: Going above the allowable memory limit<\/h2>\n
wp-config.php<\/code> file:<\/p>\ndefine('WP_MEMORY_LIMIT', '64M');<\/code><\/pre>\n