Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Often, this error is caused by blocking /wp-admin/, either with a plugin or in the .htaccess file:
    My scans don’t finish – Scan process ended after forking

    A few people have also had to turn on the option “Disable config caching” near the bottom of the Wordfence Options page, so if you’re not blocking wp-admin, that may help as well.

    Thread Starter lsu1973

    (@lsu1973)

    Thanks… I retried the scans everything worked.

    Plugin Author WFMattR

    (@wfmattr)

    Ok, great. If it does happen again, try that “Disable config caching” option — on most hosts the config cache makes things slightly faster, but a few hosts have had unusual issues from it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Scan Error’ is closed to new replies.