WordPress White Screen of Death Jetpack

Glenn Blog 2 Comments

If you are experiencing the WordPress ‘White Screen of Death’ in your WordPress admin area (or elsewhere) then Jetpack by WordPress.com could be the culprit. To find this out access your site via FTP and rename the Jetpack folder. If your Dashboard springs back to life then you’ve identified the Jetpack Plugin as the culprit, but of course you still want to use jetpack as it ghives you loads of WordPress functions. Try the following to see if it fixes the issue.

  1. Via FTP access your plugins folder /wp-content/plugins and rename the ‘jetpack’ folder to ‘jetpack-1’
  2. Via FTP open the WordPress wp-config.php file
  3. Add the following before “/* That’s all, stop editing! Happy blogging. */”
     
    /** Set WordPress Memory Limit */
    define('WP_MEMORY_LIMIT', '64M');
    
  4. Put your Jetpack folder back to it’s original name of ‘jetpack’ and refresh your WordPress Admin

This has now increased the WordPress memory limit to sufficiently support Jetpack.

Did that work for you?

About the Author
wordpress white screen of death jetpack Wordpress White Screen of Death Jetpack 0da77002febbfe28d15144a57bbcc2c9 s 180 d mm r g

Glenn

A highly experienced Web Developer (WordPress, Webflow, Weebly & Custom), Front-end / Back-end Developer & New Media Specialist, with extensive knowledge of a wide spectrum of technologies in the Development and Creative Industries, built up over a number of years.

  • Jon

    I’m currently going through the process of debugging Jetpack, which ever since version 4.4 has caused a white-screen-of-death upon update. Jetpack team have been reasonably helpful, asking for server logs etc. and suggested upping the memory in wp-config.php just as you’ve suggested. However, they suggested upping it to 256M, not just 64M. They also said to do the same in the php.ini file if you have access (which I don’t) and/or as an alternative to do the same in the .htaccess file (which I did).

    Unfortunately for me, none of these methods have helped me cure my problem!

    • Hi Jon
      Yes 256M is perfectly acceptable.
      A couple of other things to check:-
      1. Ensure you are on at least Php 5.6
      2. Disable your cache if you have one installed. Then reactivate and clear the cache completely.
      3. Put WordPress into debug mode ‘define( ‘WP_DEBUG’, true );’ in WPDM-config.php and check for any WordPress / plugin errors
      4. Check your server logs for php errors error.log
      5. Ask your hosting company to investigate
      Glenn