Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author WFMattR

    (@wfmattr)

    This should be a temporary error from a server that was restarted on our end — it should be working now, but let us know if you have any additional trouble. Thanks!

    -Matt R

    Thread Starter DrunkSteel

    (@drunksteel)

    I’m getting another error saying “Scan terminated with error: WordFence API error: Your site did not send an API key when contacting the Wordfence servers.”

    Plugin Author WFMattR

    (@wfmattr)

    Given the timing during the server restart, the site may not have been able to get its initial API key. Try turning on “Delete Wordfence tables and data on deactivation” near the bottom of the options page, and then disable Wordfence and enable it again.

    The API key should be visible in the long text box at the top of the Wordfence options page, if it works.

    If that is not it, it could mean that the site’s database user does not have all privileges in the mysql database — on most hosts, you can check this in phpmyadmin through the hosting company’s control panel.

    -Matt R

    Thread Starter DrunkSteel

    (@drunksteel)

    That fixed it! Thank you!!!

    Thread Starter DrunkSteel

    (@drunksteel)

    One more thing… now I am getting this code during my scan “[Nov 20 10:55:22] Scan can’t continue – stored data not found after a fork. Got type: boolean”

    What do I need to do to finish the scan?

    Plugin Author WFMattR

    (@wfmattr)

    Try changing the “Maximum execution time for each scan stage” to 15 seconds or 12 seconds — sometimes this helps, but it might not help in every case.

    This error is usually rare, but I’ve seen it happen a few times lately. I believe it is related to storing temporary data during scans on hosts with certain settings, and if that is the case, it will be fixed in a future version, so no workarounds are needed.

    Let me know if the above does not help, and I’ll see what else may be possible.

    -Matt R

    Thread Starter DrunkSteel

    (@drunksteel)

    That fixed it. Thanks again. Amazing plugin you guys have here

    such support. much happy.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error 502’ is closed to new replies.