Viewing 1 replies (of 1 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @drepublik and thanks for reaching out!

    Looking back at your old thread, I see you are having some scanning connectivity issues. When I see this issue, I usually have people check to make sure their site is not being blocked by the host. Also make sure, if you have a CDN such as Cloudflare, that your IP detection is correct.

    To double-check your IP detection is correct, first, check the following site and take note of your IP: https://www.whatsmyip.org

    Then, head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. Start from the top and check to see if any of the settings show that both of those show the same IP as the site above does.

    If you’re using Cloudflare, you will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.

    Also, have your host whitelist IPs 69.46.36.0 to 69.46.36.32. This could be what is causing the scanner to not connect.

    If that doesn’t work, follow the steps in this guide:
    https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking

    Let me know if this helps!

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Scan process ended after forking’ is closed to new replies.