• Resolved miguel3348

    (@miguel3348)


    Wordfence could not register with the Wordfence scanning servers when it activated. You can try to fix this by deactivating Wordfence and then activating it again, so Wordfence will retry registering for you. If you keep seeing this error, it usually means your WordPress server can not connect to our scanning servers, or your wfConfig database can not be created to save the key. You can try asking your host to allow your server to connect to noc1.wordfence.com or check the wfConfig database table and database privileges.

    I have tried everything and I can not get Wordfence to work.

    I activated and deactivated the plugin with “Dashboard> Delete Wordfence tables and data on deactivation” On

    The Plugin create the “wfConfig” table perfectly in my DB

    The Plugin works well on other WPs on the same SERVER (the same IP). But it seems that it has reached its maximum. Is there a limit on free WP installations on the same server?

    In Tools> Diagnostics> I see that the file “wafRules.rules” is missing but the “wflogs” folder creates it without problems. This same server has other WPs that have perfectly created files with the extension “.rules”

    In Tools> Connectivity I see the following error “wp_remote_post () test to noc1.wordfence.com failed! Response was: Unknown SSL protocol error in connection to noc1.wordfence.com:443 <br />” which I have disabled in “Debugging Options “>” Enable SSL Verification (Disable this if you are consistently unable to connect to the Wordfence servers.) ”

    Maybe you can only work now with SSL connection?

    But none of this makes it possible to run a Scanner.
    Please some idea

    • This topic was modified 6 years, 8 months ago by miguel3348.
Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Wordfence could not register with the Wordfence scanning servers when it activat’ is closed to new replies.