Scan process ended after forking

  • Resolved Gyztor

    (@gyztor)


    4 years, 4 months ago

    I have been having issues with word fence being unable to scan and have managed to narrow down some possibilities to help make this go faster.
    What i have found out is that my word fence is unable to login due to a path issue from what I have noticed. So when the setting to “start a scan from remote” is on i get the “Starting cron via proxy at URL” prompt than immediately hits “Scan process ended”. so to ensure my site was able to fully connect to your servers i connected it through Word fence central (and was able to successfully) and after some time searching found that the path (replaced the actual path for the page to “admin-page”) https://noc1.wordfence.com/scanp/www.placeholder.com/admin-page/admin-ajax.php?action=wordfence_doScan … leads to a 404 but when i replace “admin-page” with “wp-admin” i see the “OK with https” is there any way to fix this or is something setup wrong? to also mention I use Hide My WP Lite and was wondering if this could cause any issues too

    • This topic was modified 4 years, 4 months ago by Gyztor.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support WFAdam

    (@wfadam)

    4 years, 4 months ago

    Hello @gyztor and thanks for reaching out to us!

    Thanks for providing all that information. A diagnostic should show me what might be happening.

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Thanks again!

    Thread Starter Gyztor

    (@gyztor)

    4 years, 4 months ago

    the diagnostic report has been sent. sorry for the late reply to this.

    Plugin Support WFAdam

    (@wfadam)

    4 years, 4 months ago

    Thanks for sending that!

    So it looks like something is redirecting admin-ajax.php requests to your homepage.

    https://www.yoursite.com/wp-admin/admin-ajax.php should just be a blank page with a 0 to show access, but it’s your homepage.

    I typically see themes cause this redirect but it could also be a plugin. You might have to test with another theme, just to see if that resolves the issue.

    Let me know what you find!

    Thanks again!

    Thread Starter Gyztor

    (@gyztor)

    4 years, 4 months ago

    for me when i tested this with my phone and other devices it shows a 0 at the /wp-admin/admin-ajax.php page so i find it odd that the plugin is unable to reach it. let me look in all of my Hide My WP configs maybe that could have something to do with it

    Thread Starter Gyztor

    (@gyztor)

    4 years, 4 months ago

    So i tried changing some settings so that the ajax path directed correctly for the “Starting cron via proxy at URL” going to see how that works

    Thread Starter Gyztor

    (@gyztor)

    4 years, 4 months ago

    i managed to get scans working and i think i have a theory as to why. The remote start cron key was using a non current one so it was going to a 404 which my nginx is setup to redirect 404s back to homepage. so what i changed was the remote start to off in Tools > Debugging and that actually got the scan to start now. thank you for helping me WFAdam 🙂

    • This reply was modified 4 years, 4 months ago by Gyztor.
    Plugin Support WFAdam

    (@wfadam)

    4 years, 3 months ago

    Thanks for letting me know what you found!

    Glad to see its up and running!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Scan process ended after forking’ is closed to new replies.

Tags