• GoDaddy Community
  • Website Design & Development
  • Website Design & Development

    cancel
    Showing results for 
    Show  only  | Search instead for 
    Did you mean: 

    Wordfence scan not working

    I've had Wordfence installed for some time with no issues. Since I updated the PHP to 7.3 the scan function has stopped working. It returns the following alert "

    • Scan Failed

      The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Click here for steps you can try

    The activity log returns "Scan process ended after forking."

     

    I have been working with Wordfence support with no success. They have suggested the following:

    Can you reach out to your hosting provider and see if they are able to check on their end if anything is interrupting the connection with Wordfence? It may be a security measure they have in place on their side that is limiting the scan functionality.


    Your web server must be able to connect to port 443 and port 80 of noc1.wordfence.com. To test if it can do this, you can have them run the following commands.

    Depending on what is installed on your server one or more may work:

    dig noc1.wordfence.com
    nslookup noc1.wordfence.com
    host noc1.wordfence.com
    getent hosts noc1.wordfence.com
    ping noc1.wordfence.com

    You can try connecting both to port 80 and port 443. As long as you can connect to both, you should be able to scan. You should see the IP 69.46.36.28 returned.

     

    My hosting plan is Prime Business Hosting with cPanel. I have been told by customer support that it is not possible to check the ports. Is this correct?

     

    2 REPLIES 2
    Resolver I

    @Seizetheday Could you please check the “Wordfence –> Tools –> Diagnostics” page to see if there are any errors showing?

    Have you checked the PHP logs?

    Hi - as I mentioned above the error message = "Scan process ended after forking." Although the issue seems to have resolved it's self now and the scans are working as they should. I'm not sure why. Although the issue seems to be now occurring intermittently.