Scan failed

Hello @holidaystory17 and thanks for reaching out to us!

Usually, that would mean there was an issue with the SSL. Anything change in the past few days to prompt this by chance?

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!

Thanks for replying me back. I install/uninstall HTTP Headers fey days ago.

Diagnostic report has been sent successfully.

It looks like everything in the diagnostic says your site is connecting fine to our scan server, so I don’t think it’s dealing with a connection issue.

I did a test on your site’s URL at https://www.ssllabs.com/ and it returned a few errors.

If you could do the following steps for me:

• Go to the Wordfence > Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• CANCEL any current scan and start a NEW scan
• Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.

This will help me see exactly what is happening when the scan fails.

Let me know if you have any questions!

Thanks!

Hi, this is not my site. My site address is https://www.theholidaystory.com/

Can you kindly recheck?

_______
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/block-editor.min.js (Mem:89.0M)
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/block-library.js (Mem:89.0M)
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/block-library.min.js (Mem:89.0M)
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/block-serialization-default-parser.js (Mem:89.0M)
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/block-serialization-default-parser.min.js (Mem:89.0M)
[Jan 22 08:09:03] Scanning: /home/holidlen/public_html/wp-includes/js/dist/blocks.js (Mem:89.0M)
[Jan 22 08:09:04] Calling fork() from wordfenceHash with maxExecTime: 20
[Jan 22 08:09:04] Entered fork()
[Jan 22 08:09:04] Calling startScan(true)
[Jan 22 08:09:04] Got value from wf config maxExecutionTime: 20
[Jan 22 08:09:04] getMaxExecutionTime() returning config value: 20
[Jan 22 08:09:05] Test result of scan start URL fetch: array ( ‘headers’ => Requests_Utility_CaseInsensitiveDictionary::__set_state(array( ‘data’ => array ( ‘date’ => ‘Fri, 22 Jan 2021 02:39:05 GMT’, ‘content-type’ => ‘text/html; charset=UTF-8’, ‘set-cookie’ => ‘__cfduid=dad2b93449374fa11244c92864287167f1611283144; expires=Sun, 21-Feb-21 02:39:04 GMT; path=/; domain=.theholidaystory.com; HttpOnly; SameSite=Lax; Secure’, ‘x-robots-tag’ => ‘noindex’, ‘x-content-type-options’ => ‘nosniff’, ‘cache-control’ => ‘no-store, no-cache, must-revalidate, max-age=0’, ‘x-wp-cf-super-cache-cache-control’ => ‘no-store, no-cache, must-revalidate, max-age=0’, ‘x-wp-cf-super-cache’ => ‘no-cache’, ‘pragma’ => ‘no-cache’, ‘expires’ => ‘Fri, 22 Jan 2021 02:39:05 GMT’, ‘x-frame-options’ => ‘SAMEORIGIN’, ‘referrer-policy’ => ‘strict-origin-when-cross-origin’, ‘cf-cache-status’ => ‘DYNAMIC’, ‘cf-request-id’ => ’07c98eb65a0000fecad
[Jan 22 08:09:05] Starting cron with normal ajax at URL https://www.theholidaystory.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=standard&cronKey=858272836e9ba077c2b846bb7169473e&signature=781007ec29dd64ca6c27071ebc251f40ab1eb8ba7f0899c3700a3ccdb571c268
[Jan 22 08:09:05] Scan process ended after forking.

Looks like the headers might be interfering with Cloudflare within the scan. Have you added your site’s IP to the Cloudflare whitelist?

If your site is protected by Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. You should be able to do this by going to your Cloudflare control panel.

• Login to Cloudflare
• Go to “Firewall”
• Click the “Firewall Rules” tab
• Click “Create a Firewall rule”
• Name the rule under “Rule Name”
• Set the “Field” under “When incoming requests match…” to “IP Address”
• Enter your site’s IP address under “Value”
• At the bottom, under “Then…Choose an action” change “Block” to “Allow”
• Click “Deploy

Once you have added your site to the Cloudflare Whitelist, head back over to your site and attempt another scan.

Let me know if this helps and if you have any questions!

Thanks!

Failed again.

Is it a correct setting:- https://ibb.co/FnV36zB

Request you kindly take a deep look in my site, because sometimes ago I have cleared some malware, after this kind of problem started. I uninstall wordfence one time also. (Delete Wordfence tables and data on deactivation)
__________
Scan Failed
The scan has failed because we were unable to contact the Wordfence servers. Some sites may need adjustments to run scans reliably. Click here for steps you can try.

The error returned was:

There was an error connecting to the Wordfence scanning servers: cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104
___

Yes, it looks correct.

I tested your SSL at https://www.ssllabs.com/ and it is having issues connecting. Run the test if you want to screenshot the results for your host.

Can you check with your host to see if there are any possible SSL issues?

Thanks!