Hi @richieps, thanks for reaching out to us!
Can you do the following so I can get the information I need to help you?
- Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
- Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
Set “Maximum execution time for each scan stage” to 20 on the options page
- Click to “Save Changes”
- Go to the Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- Start a new scan
- Copy the last 20 lines or so from the Log (click the “Show Log” link) once the scan finishes and paste them in the post.
It may also help to send us a diagnostic report at the same time 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.
Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.
Thanks,
Peter.
Hi @wfpeter
Thanks for your response.
I’d seen your recommendations previously, and enabled them, but didn’t want to presume that I should post the information without being asked 😉
Here we go:
[Aug 02 08:15:09] Entering start scan routine
[Aug 02 08:15:09] Got value from wf config maxExecutionTime: 20
[Aug 02 08:15:09] getMaxExecutionTime() returning config value: 20
[Aug 02 08:15:09] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/richiesroom.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=quick&cronKey=417ab1a3b9bcf5272f53aa7843ce8561&k=e896dabc70abd576c0ceb4d19fab3d4a9dba0bd2e06fcfa40857eb06d9d2d7eb300c576b9121e5faf2719500aa393fd7e4bbae6c1f3fd49be16106f0593fe7b9&ssl=0&signature=60d3ffcb0a57ebefca72a77bab1896abdd3fe802e91b274082158c29b37e0fff
[Aug 02 08:15:10] Scan process ended after forking.
[Aug 02 08:15:10] Scan engine received request.
[Aug 02 08:15:10] Verifying start request signature.
[Aug 02 08:15:10] Scan Engine Error: The signature on the request to start a scan is invalid. Please try again.
[Aug 02 12:12:39] Calling Wordfence API v2.26:https://noc1.wordfence.com/stats.json
[Aug 02 12:12:39] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=e896dabc70abd576c0ceb4d19fab3d4a9dba0bd2e06fcfa40857eb06d9d2d7eb300c576b9121e5faf2719500aa393fd7e4bbae6c1f3fd49be16106f0593fe7b9&s=eyJ3cCI6IjUuOCIsIndmIjoiNy41LjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmljaGllc3Jvb20uY29tIiwic3NsdiI6MjY5NDg4MjA3LCJwdiI6IjcuNC4yMSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3LjcxLjAiLCJjcyI6Ik9wZW5TU0xcLzEuMS4xZCIsInN2IjoiTGl0ZVNwZWVkIiwiZHYiOiIxMC4zLjMwLU1hcmlhREItbG9nLWNsbC1sdmUiLCJsYW5nIjoiZW5fR0IifQ&betaFeed=0&action=resolve_ips
[Aug 02 12:12:50] Scan stop request received.
[Aug 02 15:17:33] Calling Wordfence API v2.26:https://noc1.wordfence.com/stats.json
[Aug 02 15:34:44] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=e896dabc70abd576c0ceb4d19fab3d4a9dba0bd2e06fcfa40857eb06d9d2d7eb300c576b9121e5faf2719500aa393fd7e4bbae6c1f3fd49be16106f0593fe7b9&s=eyJ3cCI6IjUuOCIsIndmIjoiNy41LjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmljaGllc3Jvb20uY29tIiwic3NsdiI6MjY5NDg4MjA3LCJwdiI6IjcuNC4yMSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3LjcxLjAiLCJjcyI6Ik9wZW5TU0xcLzEuMS4xZCIsInN2IjoiTGl0ZVNwZWVkIiwiZHYiOiIxMC4zLjMwLU1hcmlhREItbG9nLWNsbC1sdmUiLCJsYW5nIjoiZW5fR0IifQ&betaFeed=0&action=resolve_ips
[Aug 02 15:34:44] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=e896dabc70abd576c0ceb4d19fab3d4a9dba0bd2e06fcfa40857eb06d9d2d7eb300c576b9121e5faf2719500aa393fd7e4bbae6c1f3fd49be16106f0593fe7b9&s=eyJ3cCI6IjUuOCIsIndmIjoiNy41LjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmljaGllc3Jvb20uY29tIiwic3NsdiI6MjY5NDg4MjA3LCJwdiI6IjcuNC4yMSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3LjcxLjAiLCJjcyI6Ik9wZW5TU0xcLzEuMS4xZCIsInN2IjoiTGl0ZVNwZWVkIiwiZHYiOiIxMC4zLjMwLU1hcmlhREItbG9nLWNsbC1sdmUiLCJsYW5nIjoiZW5fR0IifQ&betaFeed=0&action=resolve_ips
[Aug 02 15:34:47] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=e896dabc70abd576c0ceb4d19fab3d4a9dba0bd2e06fcfa40857eb06d9d2d7eb300c576b9121e5faf2719500aa393fd7e4bbae6c1f3fd49be16106f0593fe7b9&s=eyJ3cCI6IjUuOCIsIndmIjoiNy41LjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmljaGllc3Jvb20uY29tIiwic3NsdiI6MjY5NDg4MjA3LCJwdiI6IjcuNC4yMSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3LjcxLjAiLCJjcyI6Ik9wZW5TU0xcLzEuMS4xZCIsInN2IjoiTGl0ZVNwZWVkIiwiZHYiOiIxMC4zLjMwLU1hcmlhREItbG9nLWNsbC1sdmUiLCJsYW5nIjoiZW5fR0IifQ&betaFeed=0&action=timestamp
I’ve also used the ‘Send Report by Email’ suggestion.
Thanks,
Richie
Hi @richieps, no problem and it’s always good to check if you’re unsure.
Your diagnostic doesn’t seem to show any connectivity errors, it is worth (after seeing that log entry) pointing you in the direction of our Scan process ended after forking documentation to ensure permissions and .htaccess blocks are not preventing access to the wp-admin folder.
Also, these issues can be related to caching. Litespeed cache and Advanced Caching drop-in plugin are enabled on your site so you could try flushing/clearing them yourself from their settings pages. WP Engine has also been a cause where “Purge All Caches” in the General Settings section should be tried. Once the data has been cleared try another scan if the above documentation didn’t do the trick!
Let me know how you get on.
Thanks,
Peter.
Hi @wfpeter
I’ve double-checked htaccess and also custom plug-ins and there is nothing blocking access to the wp-admin folder.
I’ve just done a Purge All instruction in LSC and started another scan and this was completed within a couple of minutes. Success!!
However, I don’t really want to have to clear the cache every time I run a scan as that somewhat defeats the purpose of having the content cached 😉 Now that we have identified the issue are there any workarounds that you are aware of?
Hi @richieps,
That’s great news regarding your scan completion.
I don’t know of an absolutely proven way to stop certain cache plugins from needing to be occasionally cleared, but there are a couple of things you could consider for action if it happens again. Older Wordfence installations that have been updated over time may need the wfConfig database table rebuilding, even if MySQL doesn’t flag it up. Exporting your settings, running a remove/reset and re-importing can also have an effect in updating the database structure.
Also, if you’re seeing the scan signature message in the log sometimes, then it might be that a scan is trying to start while a scan is already running. That might mean that some cron jobs are running twice, like when there are multiple servers behind a load balancer. Speaking with your host might provide a way to remedy this so that only 1 cron tries to run.
Thanks again,
Peter.
Hello, I just tried in order all the bullet points you outlined above. I received again the following:
[DEC 27 12:08:36] Scan Engine Error: The signature on the request to start a scan is invalid. Please try again.
The orange triangle filled with an exclamation point shows the there’s a problem with File Changes and Vulnerability Scan.
I’ve sent a report as requested to wftest@wordfence.com with the following forum user name: brenbooks18
Thanks for looking into the problem.
