• After activating the plugin, I go to cloud flare wordpress settings page and try to login with my credentials (email + API number). Unfortunately nothing happens. In the browser console I get:

    Failed to load resource: the server responded with a status of 403 ()
    POST https://[MY_DOMAIN]/wp-admin/admin-ajax.php?action=cloudflare_proxy 403 ()
    Uncaught TypeError: Cannot read property ‘body’ of undefined

    Any ideas what’s happening?

Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter xysiu

    (@xysiu)

    Done. I’ve opened a support ticket.

    Thread Starter xysiu

    (@xysiu)

    Guys, can you please answer for the ticket that you’ve asked me to create? For one week there’s nothing but silence :/

    BTW. in 3.0.6 the problem still persists.

    • This reply was modified 8 years, 5 months ago by xysiu.

    @xysiu,

    What is the number for your cloudflare support ticket? I’ll follow up.

    Thanks,
    John

    Thread Starter xysiu

    (@xysiu)

    1231339 – thanks

    Hi,

    I was able to login to my development environment with your credentials. The 403 http status code you’re seeing is “Forbidden”. Is your web host blocking the CloudFlare IP address space?

    Thanks,
    John

    Thread Starter xysiu

    (@xysiu)

    No. It’s not the case. I’m running another testing instance on the same server, and the plugin works fine there. So I thought it’s a matter of plugins.

    I’ve disabled all of the plugins on a product instance. It didn’t help.
    I did the same operation on a testing instance. The Cloudflare plugin works fine there.

    The only difference that I have between testing and production instance is the protocol (HTTP vs. HTTPS) that was configured. But when I disabled the https on a production, still I wasn’t able to authorize with the Cloudflare form.

    So I tried to play with directly accessing admin-ajax.php file with the action=cloudflare_proxy parameter. For testing instance, I get 0 value displayed in the browser. For the production instance, I have a null value.

    So I did the same test with admin-ajax.php file and action parameter on the production instance only.

    When HTTPS is configured in WordPress, I get:
    null for accessing the file via HTTPS
    0 for accessing the file via HTTP

    When HTTP is NOT configured in WordPress, I get:
    0 for accessing the file via HTTPS
    null for accessing the file via HTTP

    So it looks like the problem is either on the production instance or there is not covered edge case in the Cloudflare plugin that is the root of the problem. I don’t know when the admin-ajax.php file can return null. Maybe that’s a good trace to follow.

    But that’s it. This is everything that I can do on my side.

    • This reply was modified 8 years, 5 months ago by xysiu.

    Sorry if I missed something, I only skimmed through the thread, but I was dealing with what at first glance looks like an identical issue, and after deleting the plugin folder, reinstalling and finally reactivating it, I got an error message on attempted activation informing me that php-curl wasn’t installed. After installing the package everything worked as intended.

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘Can’t login with my email and API number’ is closed to new replies.