Scan fails to start with Cloudflare website

Hi @marvyndt, thanks for providing that.

“Scan process ended after forking” can be quite common, so we have a help document for this you could quickly look at for ideas you’ve not tried yet: https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking

If you have allowed your own site’s IP and our IPs from the instructions earlier in this thread for Cloudflare, it looks like you may have also tried starting scans with IPv4 Only from Wordfence > All Options > Advanced Scan Options and starting scans remotely from the Wordfence > Tools > Diagnostics page. Can I confirm if these are both the case?

Thanks,
Peter.

I am not blocking /wp-admin in .htaccess or robots.txt. To my knowledge I am not blocking access in any other manner.

There is a Cloudflare WAF rule for the host server’s IP address to skip all rules.

I have tried “Use only IPv4 to start scans” both on and off. There is no noticeable difference in results.

With “Start all scans remotely” enabled, the scan fails almost immediately. With is disabled, it fails after about 30 minutes.

I added the Cloudflare’s proxied IP address to the WAF rule and noticed a new error in the activity log. Could be related?

[Aug 16 08:11:24] Entered fork()
[Aug 16 08:11:24] 10787 files indexed
[Aug 16 08:11:24] Forking during indexing: /var/www/vhosts/dcn.org/digitalcontentnext.org/wp-content/uploads/2021/05/ChangeAhead-300x138.jpg
[Aug 16 08:11:24] Entered fork()
[Aug 16 08:11:24] Error writing value header for wfsd_engine
[Aug 16 08:11:24] Calling startScan(true)
[Aug 16 08:11:24] Got value from wf config maxExecutionTime: 25
[Aug 16 08:11:24] getMaxExecutionTime() returning config value: 25
[Aug 16 08:11:24] Cached result for scan start test: true
[Aug 16 08:11:24] Starting cron with normal ajax at URL https://digitalcontentnext.org/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=[HIDDEN BY AUTHOR]
[Aug 16 08:11:24] Scan engine received request.
[Aug 16 08:11:24] Verifying start request signature.
[Aug 16 08:11:24] Fetching stored cronkey for comparison.
[Aug 16 08:11:24] Checking cronkey: [HIDDEN BY AUTHOR] (expecting [HIDDEN BY AUTHOR])
[Aug 16 08:11:24] Checking saved cronkey against cronkey param
[Aug 16 08:11:24] Requesting max memory
[Aug 16 08:11:24] Setting up error handling environment
[Aug 16 08:11:24] Setting up scanRunning and starting scan
[Aug 16 08:11:24] unserialize(): Error at offset 0 of 1552120 bytes (8) File: /var/www/vhosts/dcn.org/digitalcontentnext.org/wp-content/plugins/wordfence/lib/wfConfig.php Line: 670
[Aug 16 08:11:24] Scan can't continue - stored data not found after a fork. Got type: boolean
[Aug 16 08:11:24] Scan terminated with error: Scan can't continue - stored data not found after a fork.
[Aug 16 08:11:24] Notice: unserialize(): Error at offset 0 of 1552120 bytes in /var/www/vhosts/dcn.org/digitalcontentnext.org/wp-content/plugins/wordfence/lib/wfConfig.php on line 670
[Aug 16 08:11:24] Scan process ended after forking.

• This reply was modified 1 year, 6 months ago by marvyndt.

Hi @marvyndt, thanks for the extra log information.

The strange thing aout the unserialize() error is that a reinstall of Wordfence is normally the solution to it. The cause can sometimes be related to corrupt tables so the Wordfence Assistant plugin can help you clear our tables completely before a reinstall.

You can import/export settings first, making sure to keep the key you’re provided with safe in the mean time, if there are any non-default settings you don’t want to lose.

The instructions for removal using the Wordfence Assistant, or manually (including database table names) are here: https://www.wordfence.com/help/advanced/remove-or-reset/

Thanks again,
Peter.