Solutions to the blank screen and / or error 500 when accessing WordPress

There are several situations in which you may find with an ugly blank screen when accessing the WordPress administration, one of them especially worrying is when it comes with a server error 500.

The first temptation to to see an error 500 if it is the case, is to contact your server, but not always the fault is from your hosting provider – I said not always, eh!

 screen-white-wordpress "width =" 838 "height =" 513 "srcset =" https://ayudawp.com/wp-content /uploads/2016/11/pantalla-blanca-wordpress-840x514.jpg 840w, https://ayudawp.com/wp-content/uploads/2016/11/pantalla-blanca-wordpress-550x337.jpg 550w, https: / /ayudawp.com/wp-content/uploads/2016/11/pantalla-blanca-wordpress-768x470.jpg 768w, https://ayudawp.com/wp-content/uploads/2016/11/pantalla-blanca-wordpress. jpg 980w "sizes =" (max-width: 838px) 100v w, 838px "/> </p>
<p> The reasons can be several, but almost always are usually caused after some update of plugins, themes or even WordPress, or any change in the configuration of a plugin or theme, apart from that you are a big hand, which is also possible. </p>
<p> There are several things we can check and try to fix, and I advise you to follow this anti-disaster list if you find a blank screen when accessing the administration of your WordPress. [19659007] First of all: Activate debugging </span></h2>
<p> Before I start to touch anything, I recommend that you activate the debug mode (<em> debug </em>) of WordPress, this way you will stop seeing the blank screen and, instead , the errors that are really causing the problem will be shown. </p>
<p> To do so, open the file <code> wp-config.php </code> of your WordPress installation and add the following lines: </p>
<div id=

define ( 'WP_DEBUG' true ) ; [19659003] define ( 'WP_DEBUG_LOG' true ) ;

It is possible that the first line already exists, if so simply change it from false to true.

The first line is the one that activates the error display, and the second one creates a debug file in /wp-content/debug.log in the that all debugging errors will appear.

Check the plugins

The first thing is to check the most common suspects: the plugins . To check if someone has been the culprit access by FTP or cPanel to your server and change the name to the folder of the plugins .

It will be in / wp-content / plugins / ] so give it another name, for example / wp-content / plugins-malos / to say the least.

If you can access it simply rename the plugins folder to its original name and return to activate them, one by one, testing if you can then access, to detect which is causing the error.

Check the topics

To check if it is a matter of the issues the procedure is similar, but first you must make sure that you have installed at least one of the default WordPress themes, the Twentyloquesea that you play this year.

Why do I tell you this? Well, because we are going to deactivate the active theme and do not want your website to go blank without displaying any content?

WordPress, if it does not detect any active theme, it automatically activates the last default theme that you have installed, so that if gives Google to go through your website while doing experiments or fixes, even if it looks ugly, unless it shows your content instead of … nothing.

Well, once you download a subject Twentyalgo and upload it via FTP or cPanel to the folder / wp-content / themes / in this same folder, rename the folder of your active theme to whatever, for example:

From ] / wp-content / themes / Nombredemitema / to / wp-content / themes / Nombredemitema-malo /

When renaming the folder, WordPress deactivates the active theme , looks to see if there is any Twentyalgo installed and activates it.

Next delete the folder of your theme, previous backup, and try to access to your WordPress.

If it was a problem of the subject you should be able to enter the administration. Then upload a clean and updated version, before trying again to activate it again.

Check the .htaccess file

Another of the most common reasons is that your file .htaccess be corrupt have something that does not suit you, so to speak. They can be joined lines that should not be, spaces or intros out of site, too many things, so we'll go to the fast, not to review line by line.

Access by FTP or cPanel to the installation directory of your WordPress and make a copy of the .htaccess file. Then delete it or change the name whichever you prefer, so that it is not active.

Your website should work equally, but it will fail to click on any internal link, this is normal. Just try to access the WordPress administration – if it already works – and in Settings -> Permanent links save changes without modifying any settings.

With this action WordPress creates a new file .htaccess clean, only with the rules of permanent links of WordPress, and all the links on your website will work, as well as the administration, if you have succeeded.

Increase the memory limit of PHP

] We have already seen this before, but here we can also use it, and that is that, due to the PHP memory limit of your server, your website may show an error 500 .

The way easier to check if this is the problem is to open the file wp-config.php of your installation and add the following line:

Save the changes and try to enter. If you do not get it try to raise the limit to 128M or even 256M. But do not think that this is valid forever, realize that it is a temporary patch and you should review your hosting plan, or even change the provider.

Check the WordPress installation files

It may also be that, due to a failed installation, some WordPress files are corrupted or incomplete so download the latest version from WordPress.org and, via FTP or cPanel, upload the folders wp-admin and wp-includes and replaces the existing ones with the new ones.

Check the file and / or folder permissions

Another possible reason may be due to the files and / or folders of your installation ] do not have the correct permissions . If so, this can also cause 500 errors and white screens of death in WordPress.

You can solve it in two ways:

  1. Access by FTP or cPanel to your installation and check the permissions of each file and / or folder and check if they have the right ones: 644 for files, 755 for folders . The bad thing about this method is that you have to check the permissions almost one by one.
  2. Change all hit permissions by adding this line to your wp-config.php file .
  3. If you're staying in SiteGround you can access the WordPress Toolkit and, in one click, automatically change all the permissions of your installation to the appropriate ones in the button Fix permissions .

Contact your hosting provider

If none of the above works I'm afraid you have to contact your hosting provider to give you a solution, which sometimes will change of hosting plan.

If it is the case I recommend that you try with SiteGround not only you will not have most of these problems thanks to their systems of account isolation and specialized optimization in WordPress but if you have any problem you solve it immediately … and yes, they have very competitive prices.

Do you know any other way?

If you have discovered some other way to solve the problem of the white screen and / or error 500 in the administration of WordPress we are looking forward to reading it in your comments.

🙂

Loading …

That may also help you: