cnm on "[Plugin: Jetpack by WordPress.com] Blank Page After upgrade to 4.0"

I'm getting a blank page after i upgraded.I had to disable plugin to get back in.

https://wordpress.org/plugins/jetpack/

Same problem here.. Unable to log out, and website inaccessible...

Workaround was to disable plugin..

Second serious defect with Jetpack in April, after the 'bogus video links in Idea' problem with 3.9.5 on April 1..

Not impressed with quality, and testing, of recent updates...

Robert Gadsdon.

Mine too.
White screen of death!
WP_DEBUG, true - no error is displaying
Front end - blank
Admin end - blank

WP_Debug only enables the Debug Mode.

You will need to set WP_DEBUG_DISPLAY as well to true to see the error on your browser.

The problem is triggered by connecting to wordpress.com. Disabling the plugin and enabling it will let your site work. Right after the activation and permission for which wordpress.com account to use your site will stop working (I can see the redirect url to my dev server that should trigger the successful activation screen).

At that point nothing is retued anymore by the front end of WordPress (I can still access the admin area). There's no error message, no page content, nothing in the debug log, and the http response code is 200 (WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY are tued on).

Also have the same problem.

Situation undetected.
Tried cmaessen's solution. Not worked.
Enabled WP_DEBUG_DISPLAY as Jon (Kenshino) suggested. Nothing but the same blank page.
I tried deleting cache, and disabling all the caching plugin from very beginning.

BTW, with some similar combination of plugins in other WP installs of mine, the 4.0 is working on Single and Multisite instances.
I tried deleting cache, and it's still functioning well in those sites.

What I described isn't a solution, it's when/what triggers the problem on my install. Current workaround is to disable the plugin and wait for an update or feedback from the programmers on how to resolve it.

+1 - seems intermittent - get WSOD disable and enable the plugin then it's ok for a while but after a while ends up back as WSOD

+1 - today's update killed two of my sites with a 500 error WSOD, but other of my sites are fine (so far, anyway).

I am jumping in with a WSOD courtesy of JetPack as well. I sent a support inquiry about this directly. Should be interesting to see their feedback.

Oddly, it was JetPack monitoring that told me my site was down in the first place this evening.