Scan Engine Error: The signature on the request to start a scan is invalid. Plea

Response:

Hello @fferrari , thank you for reaching out.

I would not recommend deleting the .htaccess file, this is not a Wordfence file but rather a WordPress one which allows your site to interact with Ajax. It is also where we store waf configuration information, which is not related to your scan.

A diagnostic would help me identify what issue you are facing. Can you send a 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.

NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

Hope this helps,

Christian

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

@wfchristian How are you? thank you for your help, email sent!
thank you so much

Hello @fferrari , thank you for the diagnostic.

You mentioned having the IPs allowlisted in Cloudflare, but you need to allowlist your server IP, not Wordfence IPs

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 Source 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!

Christian

Dear @wfchristian,

I made the rule and it keeps failing.

I have been using Cloudflare for many years and so far nothing has changed recently. And this started failing a month ago on all sites.

Even yesterday I changed the NS pointing to the VPS directly (without cloudflare) and the problem persisted, I think cloudflare is not the problem. What do you think?

this info comes from my vps:
nslookup noc1.wordfence.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: noc1.wordfence.com
Address: 54.148.171.133
Name: noc1.wordfence.com
Address: 35.83.41.128
Name: noc1.wordfence.com
Address: 52.25.185.95

and this one from my desktop:

nslookup noc1.wordfence.com
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: noc1.wordfence.com
Address: 35.83.41.128
Name: noc1.wordfence.com
Address: 54.148.171.133
Name: noc1.wordfence.com
Address: 52.25.185.95


Also I don’t see problems on this too.

thank you again

Solved!! the problem was this plugin… Change wp-admin login

really thank you for the help!

@fferrari Oh man, thank you a lot by this information! I got same problem since few mounths ago and never got the solution. So I just deactivated the “Change wp-admin login” and voylá.

Hello @fferrari

Glad you resolved the issue, I would have recommended the same solution.

Changing the wp-admin location is known to cause problems with our scanning feature.

Wordfence has built in protection for your login page so you don’t need to change its location. Our CEO released a video a few years ago detailing why this is the case if you would like to learn more: https://www.wordfence.com/blog/2017/10/should-you-hide-wordpress-login-page/

Glad I could be of assistance,

Christian