3.0.1 breaks website

Hi,

Were you getting 502 errors when your site broke?

Thanks,
John

Hello John, yes that is what appears.

Hey,

We think this bug is related to our implementation of HTTP2/ServerPush. We’re removing it in 3.0.2 which should be released some time today. Please let us know if this update fixes your errors.

Thanks,
John

Will do, thanks!

Holy Cow – just updated the plugin – how do I get rid of it right now, because I can’t access the admin panel. Deleting the plugin or renaming it was no success.

Hi @janworx,

What version did you upgrade to?
What happens when you try to access the admin panel?
Are there any errors in the PHP error log?

Thanks,
John

janworx, If you can access the plugin folder for cloudflare and edit the cloudflare.php file, just comment out the very last line of the file. Example below. If this doesn’t work or you can’t do it, then you might have to wait. Right now I just have the plugin disabled, since I realize I am not utilizing cloudflares features at the moment.

// Enable HTTP2 Server Push
//add_action('init', array('\CF\Hooks\HTTP2ServerPush', 'init'));

disclosure this was mentioned in another thread, I am not a part of cloudflare obviously.

• This reply was modified 8 years, 2 months ago by Stephen.

If I delete or rename it, I get a broken login screen. It has fields that won’t work. If I reinstate the plugin, it says I don’t have permission to enter site. Give me location of error log, and I’ll go look there.

Site broken. spanishpeaksarts.org

Ha! But that was already IN it without me doing anything! Here it is:

// Enable HTTP2 Server Push
// Removed until the problems are indentified and fixed
// add_action(‘init’, array(‘\CF\Hooks\HTTP2ServerPush’, ‘init’));

Too weird.

Yeah I didn’t actually look at the source for 3.0.1 so they might have made that change. Either way it didn’t help in 3.0.1 but worked in 3.0 .

Yeah so the root cause was in our implementation of HTTP2/Server Push. It created too many headers for blogs with large front ends. 3.0.1 was an attempted fix but it only fixed the 520s, not the 502s. It was removed in 3.0.2.

Thanks,
John

3.0.2 certainly fixes it. Thanks!

Very sorry about the problems this caused. I’m surprised we didn’t catch this during the beta.

It is understandable, too many variables!