• 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 15 replies - 1 through 15 (of 22 total)
  • Thread Starter xysiu

    (@xysiu)

    Additional info

    When pasting in a browser the https://[MY_DOMAIN]/wp-admin/admin-ajax.php?action=cloudflare_proxy i get a different autcome when compare it with https://[MY_DOMAIN]/wp-admin/admin-ajax.php?action=cloudflare_proxy

    My entire page is using HTTPS protocol. Maybe it has something in common with the fact, that I’ve just moved DNS to Cloud Flare, and it hasn’t been 24hours? There’s information on your page that ‘SSL certificate issuance may take up to 24 hours.’

    Is the problem still occurring?

    Thread Starter xysiu

    (@xysiu)

    Yes. Reinstallation of the plugin didn’t help. Downgrading to 3.0.2 also.

    And to confirm again – this issue DOESN’T occur in 3.0.2 correct?

    Thread Starter xysiu

    (@xysiu)

    This issue occurs in both versions: 3.0.2 and 3.0.3. I didn’t check the older versions, though.

    Maybe this chrome console log will be helpful:

    client.js:960 POST https://[MY_DOMAIN]/wp-admin/admin-ajax.php?action=cloudflare_proxy 403 ()
    Request.end @ client.js:960
    request @ http.js:95
    post @ http.js:139
    pluginAccountPost @ PluginAPI.js:29
    (anonymous function) @ user.js:62
    (anonymous function) @ index.js:9
    handleLoginSubmit @ ClientLoginPage.js:37
    onClick @ ClientLoginPage.js:70
    ReactErrorUtils.invokeGuardedCallback @ ReactErrorUtils.js:71
    executeDispatch @ EventPluginUtils.js:79
    executeDispatchesInOrder @ EventPluginUtils.js:102
    executeDispatchesAndRelease @ EventPluginHub.js:43
    executeDispatchesAndReleaseTopLevel @ EventPluginHub.js:54
    forEachAccumulated @ forEachAccumulated.js:23
    processEventQueue @ EventPluginHub.js:259
    runEventQueueInBatch @ ReactEventEmitterMixin.js:18
    handleTopLevel @ ReactEventEmitterMixin.js:34
    handleTopLevelWithoutPath @ ReactEventListener.js:93
    handleTopLevelImpl @ ReactEventListener.js:73
    perform @ Transaction.js:136
    batchedUpdates @ ReactDefaultBatchingStrategy.js:62
    batchedUpdates @ ReactUpdates.js:94
    dispatchEvent @ ReactEventListener.js:204

    Uncaught TypeError: Cannot read property ‘body’ of undefined
    v4ResponseOk @ CFClientV4API.js:13
    pluginResponseOk @ PluginAPI.js:19
    (anonymous function) @ user.js:63
    (anonymous function) @ http.js:107
    Request.callback @ client.js:804
    (anonymous function) @ client.js:527
    Emitter.emit @ index.js:133
    xhr.onreadystatechange @ client.js:886

    The result: I can’t authorize the CloudFlare inside WordPress so the plugin is useless for me ??

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

    Are there any errors in the PHP error log?

    Thread Starter xysiu

    (@xysiu)

    No, the log is clean.

    Try this:

    SSH into your server and cd into the cloudflare plugin folder. Run composer update, activate the plugin, enter credentials.

    install composer (if you don’t already have it)
    https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx

    composer update

    Activate the plugin
    Enter your credentials

    Thread Starter xysiu

    (@xysiu)

    I’m using virtual hosting, not dedicated server, so I’m not able to install any additional libraries and packages :/

    So what’s the problem with this login screen? Is it PHP incompatibility? Or the plugin has a bug?

    The new version they just pushed updated the dependencies so just grab the newest 3.0.4 and you should be good.

    Thread Starter xysiu

    (@xysiu)

    Yeah, but now I can’t find the CloudFlare settings page (after upgrading to 3.0.4) in the WordPress menu – it’s gone ?? So no ability to log in :””///

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

    Hey,

    Just to clarify – you don’t need to run composer on your server for our plugin to work. Running composer install or composer update will generate a vendor/ folder which we keep under source control so you don’t have to run those commands.

    If you’re not seeing errors in the PHP error log then I don’t think the dependencies are the root cause of this error. The exception would be is if your WordPress file structure is non-standard causing require_once 'vendor/autoload.php'; to fail.

    Thread Starter xysiu

    (@xysiu)

    After upgrading to 3.0.5 the problem still exists. I can’t log in with API credentials. Same error in the browser console :”(

    How can I fix this?

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

    (@xysiu)

    OK. Somehow I was able to install composer on my virtual hosting. But when I’m trying to do composer update in the plugin folder, I get Fatal Error Unable to create lock file: Bad file descriptor (9).

    I’m so close to resigning from this plugin ??

    Hi @xysiu,

    There was only one fix in 3.0.5, and it wasn’t related to this issue. We still don’t know the root cause of your issue so we haven’t released a fix yet.

    Would you please open a support ticket with us so we can debug further? Please include:

    A link to this page
    Version of PHP
    Version of WordPress

    Thanks,
    John

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