I also get 520 errors on various pages.
I’m just trying to send the headers so cloudflare can do the actual pushing.
I’m load balancing hhvm and php5-fpm on the same server with nginx serving the pages to Cloudflare.
I’ve never had a 520 error with this plugin before, but the HHVM angle sounds interesting. thetechnuttyuk are you also running HHVM on your server?
Any info you gotta could find in your server logs would be a big help.
Dave,
I’ve run into this error a number of times lately — Cloudflare will return a 520 error on /wp-admin/index.php. Page rules at Cloudflare can make the rest of the back-end accessible, but that particular URL stubbornly returned the 520 error in spite of them.
I’m only just learning that your plugin (which I love) appears to replicate functionality that Cloudflare already provides, so perhaps that’s the conflict.
In any case, in my experience, this little bugger has cropped up on servers with and without HHVM, so I don’t think that’s the issue.
Cloudflare tells me these 520 errors are caused by an issue on their end or possibly within the web server software itself (usually Apache).
They’ve offered to help people troubleshoot where the error is originating, so don’t hesitate to reach out to their support team.
My plugin doesn’t duplicate any functionality of theirs. What it does it signal to their servers that it needs to push the script & CSS assets. You can read more about how it works at https://blog.cloudflare.com/using-http-2-server-push-with-php/ — it’s really simple, which is why these 520 errors are so baffling.
Hi Dave
Just wanting to know if there was any workaround to getting the plugin working with Cloudflare.
I find I only get 520 errors when I try and edit a post. I can browse my site without any issue just editing the post which is the problem.
Cloudflare has page rules however there is no option to disable HTTP2 in page rules…
