• Just updated to 3.0 and our website broke. The Cloudflare error about the website being down is displayed, but the website actually works. When I browsed to the direct address the following error was displayed:

    Warning: array_walk() expects parameter 1 to be array, null given in /srv/users/serverpilot/apps/wordpress/public/wp-content/plugins/cloudflare/src/Hooks/HTTP2ServerPush.php on line 72

    Warning: array_walk() expects parameter 1 to be array, null given in /srv/users/serverpilot/apps/wordpress/public/wp-content/plugins/cloudflare/src/Hooks/HTTP2ServerPush.php on line 72

    Disabled the plugin and the website worked again. Please advice.

Viewing 14 replies - 16 through 29 (of 29 total)
  • I am getting a 502 error after I updated. I disabled it and everything is working fine again. There was nothing obvious in the error log to indicate a problem with the plugin however.

    Currently on WordPress 4.6.1 / PHP 5.4.28 / on bluehost.

    We’ve uploaded version 3.0.1 fixing 520 errors and HTTP/2 Server Push warnings. If you still have any issues related with this issue please provide the new error logs with your PHP version.

    Changelog: https://en-gb.www.ads-software.com/plugins/cloudflare/changelog/

    yeah! works great! thank you

    Still getting a 502 Bad Gateway error when trying to access the backend.

    Ray ID: 2e352a2671d91888

    WordPress 4.6.1 / PHP 5.4.28

    nothing in the error log.

    Works for me again, too. Thank you!

    By default Plesk uses nginx is that something which complicates things? Not getting 520 any more but I can’t edit any wordpress posts without getting a 502. This is messing with A LOT of live sites.

    When I turn off nginx the 502 goes away. I have no information on what knock on effects will occur.

    Hi @nilbud,

    Have you upgraded to 3.0.2?

    Thanks,
    John

    Can’t login into my wordpress dashboard after upgrading to 3.0.2. Whenever I try this error is being displayed “Sorry, you are not allowed to access this page.”. When I delete the cloudflare plugin from my plugin folder through cpanel then I am able to login into my wordpress dashboard but then my website does not open.

    Yeah I did upgrade to 3.0.2 when it became available. I’ve left the nginx turned off just in case you guys get frisky again.

    Hello

    I’m having the same error “Sorry, you are not allowed to access this page.” when I refreshed the wp-admin page (to which I was logged in)

    I went back to 1.3.x. plugin version, and it work ok now …

    I also cannot access /wp-admin on several of the sites I manage (Sorry, you are not allowed to access this page.). It looks like it is only sites using this cloudflare plugin that are also using flexible SSL. If i bypass cloudflare i can access admin just fine. All caches have been purged, tried development mode, page rules as per cloudflare, but its still wont working. These sites have been working for months or even longer and the only change as the update to this cloudflare plugin.

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

    Hi @aktech,

    Does disabling SSL fix the issue?

    Thanks,
    John

    I’m having the same issue of not being able to access the administration area on three of four websites using this plugin. We’re using Cloudflare’s Strict SSL and we require SSL for all admin pages. I tried temporarily turning off Cloudflare but the error persists. The only solution was disabling the plugin.

    Also, this is possibly unrelated, but it most definitely began once I upgraded the Cloudflare plugin, images uploaded via the media uploader are broken in the administration site when being set as a Featured Image for a post. However, they show up fine outside of the administration site (with and without SSL) and also within the media uploader.

    Wordpress 4.6.1
    PHP 7.0.8-0ubuntu0.16.04.2
    Cloudflare plugin 3.0.3
    nginx version: nginx/1.10.1 (http/2 supported)
    Specific error: “Sorry, you are not allowed to access this page.”

    Each of the four websites are using the same configuration and plugins, and are also on the same server.

    ** EDIT: After looking into the plugins for each site, the only difference was that the working website had the plugin “cloudflare-flexible-ssl” installed and activated. Propagating this plugin to the broken websites fixed the issues. **

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

    Same issue (Sorry, you are not allowed to access this page.) with 3.0.2 so I tried 3.0.1 and got the same message. I went to 1.3.25 and I now have access again.

Viewing 14 replies - 16 through 29 (of 29 total)
  • The topic ‘Website broken with 3.0’ is closed to new replies.