Oooookay.
Ready for the weirdest bug report I have had with a wordpress plugin in two whole years?
Banzai.
Sorry for the colloquial language and lack of organization, I’m as if drunk from lack of sleep. Not cloudflare plugin’s fault, I’m on that one for five minutes only, no worries.
I host several blogs and administer one. It’s with that one that I have had issues, and have had THE bug now.
I saw the tracking entry mentioning that for some users, if we tried, and tried, and tried, it eventually worked.
So, guess what, I tried, and tried, and tried.
Four or five attempts, failing as of usual, until, without any warning, the last call did the job, and the plugin installed itself allright.
Yay!
I proceed to write a post.
Publish it.
And then, BAM, cloudflare error message within my browser, saying there is an unknown error, everything works save the end point, the server hosting the website.
Me: FUUUUUUUU!
I check the “public” version of the blog, miracle, the post had been published before the bug occuered, apparently.
Further testing.
Actually, the blog works. It’s the admin part that returns a cloudflare error every time.
For instance:
?Error 520 Ray ID: 2e30916022201025 ? 2016-09-16 01:33:01 UTC
Web server is returning an unknown error ?
So, once I’m done panicking, I simply rename the directory of the plugin by SFTP, to “cloudflare WTF!” (yeah, sorry, not very poetic).
Unsurprisingly, I can once again acccess the admin of the blog once the plugin has been forced-deactivated.
I then proceed to reactivating the plugin from within the wordpress admin.
Hehe, guess what happened again? Yeah.
I also did the test with cloudflare, for my website, set in development mode.
That didn’t make a single difference.
I checked my apache error logs: nothing relevant, the last entry was several hours ago for something else.
I’m done for today, sorry, I reported as best as I could. Cheers!