Wordfence could not get an API key

  • Resolved RandyN

    (@randyn)


    10 years, 4 months ago

    I just installed Wordfence Version 3.8.9 onto WordPress 3.7.1. I encountered what seems to be a common problem:

    “Wordfence could not get an API key from the Wordfence scanning servers when it activated. You can try to fix this by going to the Wordfence “options” page and hitting “Save Changes”. This will cause Wordfence to retry fetching an API key for you. If you keep seeing this error it usually means your WordPress server can’t connect to our scanning servers. You can try asking your WordPress host to allow your WordPress server to connect to noc1.wordfence.com.”

    I went to Options and hit Save Changes, and I deactivated/reactivated the plugin. No change. I then ran the connection testing utility near the bottom of the Options page and got this result:

    “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.”

    http://wordpress.org/plugins/wordfence/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter RandyN

    (@randyn)

    10 years, 4 months ago

    Tried again just now (17 hours after first post). Again, couldn’t retrieve the key. The connectivity test passed again. However, I could not ping noc1 from the blog’s host system.

    %ping -c 4 noc1.wordfence.com
    PING noc1.wordfence.com (69.46.36.8): 56 data bytes
    — noc1.wordfence.com ping statistics —
    4 packets transmitted, 0 packets received, 100.0% packet loss

    However, I can connect to noc1 on port 80:
    %telnet noc1.wordfence.com 80
    Trying 69.46.36.8…
    Connected to noc1.wordfence.com (69.46.36.8).
    Escape character is ‘^]’.

    Any ideas what the problem may be?

    Plugin Author Wordfence Security

    (@mmaunder)

    10 years, 4 months ago

    Hi,

    Can you tell me which hosting provider you’re using? They may have some kind of proxy set up that appears to be able to connect to Wordfence scanning servers in actually is creating problems.

    Thanks,

    Mark.

    Thread Starter RandyN

    (@randyn)

    10 years, 4 months ago

    It’s shared hosting at Pair Networks (http://www.pair.com).

    jonathan.nepomuceno

    (@jonathannepomuceno)

    10 years, 4 months ago

    Hi,

    As posted by RandyN. We are also currently encountering the same error. I was able to telnet to noc1.wordfence.com without any problems.

    We are currently hosted in Amazon and is using wordpress version 3.8 with your latest version of wordfence.

    I have checked my error logs but did not find errors related to wordfence.

    Hoping to get an update on your end soon.

    Regards,

    Jonas

    Plugin Author Wordfence Security

    (@mmaunder)

    10 years, 3 months ago

    Thanks for the update.

    We fixed an issue that caused this a while back but it may have reoccurred, so I’m going to log this bug and investigate.

    Regards,

    Mark.

    jonathan.nepomuceno

    (@jonathannepomuceno)

    10 years, 3 months ago

    Hi Mark,

    Thank you for your response. We will be monitoring the plug in for updates.

    Regards,

    Jonas

    companyv

    (@companyv)

    10 years, 3 months ago

    This might be my problem as well – site is only displaying “No API Key Defined”

    companyv

    (@companyv)

    10 years, 3 months ago

    THIS was not my problem – it was actually “meetup” API that was failing!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Wordfence could not get an API key’ is closed to new replies.

Tags