API can't connect

  • Resolved Annie888

    (@annie888)


    9 years, 7 months ago

    Hi all,

    I did see another thread on this but I didn’t see any answers that apply to me.

    I started getting the API can’t connect error today. After trying a few things with no results, I uploaded the new version of the WF 2.5.1 plugin. And still getting the error.

    I have a support ticket into my host. The Tech said that there’s probably a rule blocking it and that they will investigate it and try resolve it.

    In the mean time my question is: How important is it too have the API connect?

    For me, the plugin seems to still have full functionality. Its rendering ips
    in live traffic, and blocking, everything seems to be running okay.

    And the error message is not showing in the top of the page like it did before. but when I run the connectivity test that is where I see the error.

    Here’s the error message I get:

    Wordfence connectivity tester
    DNS lookup for noc1.wordfence.com returns: 69.46.36.8

    STARTING CURL http CONNECTION TEST….
    Curl connectivity test passed.

    STARTING CURL https CONNECTION TEST….
    Curl connectivity test passed.

    Starting wp_remote_post() test
    wp_remote_post() test to noc1.wordfence.com failed! Response was: 404 Not Found
    This likely means that your hosting provider is blocking requests to noc1.wordfence.com or has set up a proxy that is not behaving itself.
    This additional info may help you diagnose the issue. The response headers we received were:
    server => nginx/1.4.6 (Ubuntu)
    date => Wed, 03 Sep 2014 03:46:49 GMT
    content-type => text/html
    content-length => 177
    connection => close

    Thanks in advance,

    Annie

    https://wordpress.org/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • WFSupport

    (@wfsupport)

    9 years, 7 months ago

    Annie888

    Sorry you are having issues with the API. Is this a free key or a paid one?

    If it’s free, see the last item on this page:

    https://wordfence.freshdesk.com/support/solutions/articles/1000010333-i-changed-my-domain-name-and-need-to-delete-my-key-how-do-i-do-it-or-i-have-another-key-related

    If paid, let me know and I’ll double check on the procedure.

    Thanks!

    tim

    WFSupport

    (@wfsupport)

    9 years, 7 months ago

    Annie888

    Are you still having this issue? Have you heard anything back about your host’s possible changes? Did you try the last item in the link I sent?

    Let us know.

    Thanks!

    tim

    Thread Starter Annie888

    (@annie888)

    9 years, 7 months ago

    Hi Tim.

    Thank you for the quick reply AND follow up! Sorry I couldn’t reply sooner.

    My host emailed back telling me there is no block on the Wordfence site/url – plugin. I sent them the error message.

    Yes I did try the “deactivate’ check-mark – uninstall, it didn’t work.

    As stated above, I’m not sure how important it is to get the API to connect as the plugin seems to function properly – And the error comes and goes.

    At any rate, I have the 5.2.1 and I wish to have the updated 5.2.2 but I don’t want to update with the current problem.

    So I’m going to delete the WF Congig and Cashe file and all other WF files in my WP-Content folder. Then download the newer version. And hopefully that’ll give me the newer version with a new key and the API should then work and I’ll then be updated as well. The only pain with that is in-putting all the Advanced blocks that’s currently in place.

    Hope you approve of the plan. The option you suggested didn’t work, nor did it work when I changed servers (host) WF still had all the config info from previous host and couldn’t preform scans. Deleting all the files from WP-Content was the only thing that worked. Getting it set-up all over again is time consuming, but worth it to me to have this awesome plugin. I love watching live traffic it has helped me tremendously getting real time views of 301’s and visitor geography and so much more, to help maintain and improve my site not to mention the awesome security. The security features and blocking features have saved my xxxx.

    Thanks Tim!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘API can't connect’ is closed to new replies.