• Resolved hitonguyen

    (@hitonguyen)


    Dear sir,
    I’m having trouble logging into my WP sites with admin accounts.
    The problem started when Wordfence updated 2 days ago. After logging out, our Admin accounts cannot log back in because of the Authenticate error and we cannot reach 2FA to log in. Fortunately, there are still 2 Admin accounts that have not logged out. We checked and gradually turned off the plugin, reCapcha, and 2FA on one of those pages, and the admin accounts of that page were logged back to normal.
    Then we started looking for the cause of the error and discovered that Wordfence was not working as usual. Some errors we found are as follows:

    • When we enable 2FA for an Admin account, that account will have an Auth error and cannot log in until another admin deletes that account’s 2FA.
    • Wordfence’s scan cannot run, error is displayed
      “Scan Stage Failed
      A scan stage has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Wordfence will make up to 4 attempts to resume each failed scan stage. This scan may recover if one of these attempts is successful. Click here for steps you can try.”
    • I tried the steps inside there but it didn’t work. Enable debugging mode returns the following content:
      “[Jun 11 00:31:52] Scan stop request received.
      [Jun 11 00:31:58] Ajax request received to start scan.
      [Jun 11 00:31:58] Entering start scan routine
      [Jun 11 00:31:58] Got value from wf config maxExecutionTime: 0
      [Jun 11 00:31:58] Got max_execution_time value from ini: 60
      [Jun 11 00:31:58] getMaxExecutionTime() returning half ini value: 30
      [Jun 11 00:31:58] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/woocommerce-1162769-4161918.cloudwaysapps.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork =0&scanMode=custom&cronKey=c4e6212dcdb1c63fbf0e5f4bfe645070&k=3ecb3034bb30ba6bdb4ffa02e870ee9d44d6da66fae3d2b55ff7a82f94d493e73a40fc5c64419fc5404a 00418d01fa3bee1a4b72f1dfcbcc73e9280e0b525cde19800e2652cdd2becd081993e2b3704af3d05c49af0a209e05b47bea85515b6f&ssl=1&signature=07adc40d90cafa646 58b44bb8da57dcecabfc2b3324f2f79e9a3fa35a140eb80
      [Jun 11 00:31:59] Scan process ended after forking.”
    • I even tried to remove the plugin to reinstall it but it didn’t work. Currently I am checking errors on 1 page and disabling this plugin on all my remaining pages. I really like this plugin even though I’ve only used it for a little over a month. Hope I get help so I can use it again. Hope to hear from you soon.
      Thank you very much!

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @hitonguyen, thanks for getting in touch and sorry to see you’re having trouble with this.

    Your troubleshooting seems very thorough, although I’m wondering if there’s now a problem with our IPs or your own site connecting in as scans are clearly affected on top of 2FA.

    If you’ve not already tried our help document for the “Scan process ended after forking” message, you could quickly look at for ideas you’ve not tried yet: https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking

    Failing all of the above, please send a diagnostic to wftest @ wordfence . com directly from the link at the top of the Wordfence > Tools > Diagnostics page, that may help. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,
    Peter.

    Thread Starter hitonguyen

    (@hitonguyen)

    Hiiiii Peter,
    I tried your instructions but it didn’t seem to work. I’m not sure but it seems to have worked again after I included the list of recommended ips in the allow rule. I turned it back on for one of my pages. Hahaaaa. Thank you so much for your support!

    I just had this happen after updating wordfence and our wp-2fa plugin at the same time. admin accounts (2fa enabled) couldn’t log in. They could after i delete the wp-2fa plugin from the plugins folder.
    It seems some incompatibility between wordfence and wp-2fa has arisen.

    Ok, so it looks like wordfence community has a 2fa feature now.
    Maybe this is why it conflicts with our other plugin.
    https://pasteboard.co/2K3XS7qsfyDI.png

    • This reply was modified 3 weeks, 1 day ago by chonkat.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.