Scan Engine Error: Request Signature Invalid

  • Resolved grovesp

    (@grovesp)


    4 years, 10 months ago

    cPanel Hosting at GoDaddy (Filesystem Installation)

    This is an older WordPress site which we’ve maintained for some time with the free version of Wordfence. It’s worked quite well until recently. The site was on an old, Linux Shared Hosting Plan (called ‘Classic’) and GoDaddy moved us into the new cPanel hosting. Now, we receive the following error when attempting to perform a scan:

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

    Several attempts were made to alleviate this, including reinstallation of the plug-in, enabling Start All Scans Remotely, and disabling SSL Verification. (Wordfence > LiveView > Diagnostics) None helped.

    The only search results for this topic come up with a gentleman that doesn’t know how it was resolved, but it took care of itself. (The signature on the request to start a scan is invalid.)

    While this doesn’t seem common, is this somehow tied to the fact we’re on a different server/platform? Is there a certificate/identity attached to the Wordfence that needs updating, or is there something else going on here?

    Thanks for your help!

    • This topic was modified 4 years, 10 months ago by grovesp.
    • This topic was modified 4 years, 10 months ago by Yui.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    4 years, 10 months ago

    Hi @grovesp, thanks for all the detail so far.

    With this hosting plan change, it does seem relevant that the issue has happened immediately afterwards. Did you also try disabling/reenabling all plugins as the user had tried in the other topic?

    I suspect this issue might be related to caching, so that could be why disabling all plugins and reenabling them fixes the issue as I imagine cache plugins will flush their data during this process. If you have any caching plugins you could try flushing/clearing them yourself. WP Engine has also been a cause where “Purge All Caches” in the General Settings section should be tried.

    If that doesn’t do the trick, please could 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.

    It’d be good to also see the full scan log:

    • 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.

    Thanks,

    Peter.

    grahappa

    (@grahappa)

    4 years, 8 months ago

    I’m having the same problem. Here is the log. Thank you

    [Aug 25 12:42:40] Ajax request received to start scan.
    [Aug 25 12:42:40] Entering start scan routine
    [Aug 25 12:42:40] Got value from wf config maxExecutionTime: 0
    [Aug 25 12:42:40] Got max_execution_time value from ini: 120
    [Aug 25 12:42:40] ini value of 120 is higher than value for WORDFENCE_SCAN_MAX_INI_EXECUTION_TIME (90), reducing
    [Aug 25 12:42:40] getMaxExecutionTime() returning half ini value: 45
    [Aug 25 12:42:40] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/mysubdomain.mydomain.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=81bff5692cf4210c74f4e32f2a96f27b&k=933e3e0d919ea04b14c97082df3aefbf2b7ea1a18bc0afe1dae20dc309364f74dd1bc32f6ad1ae259951c7d66e3be8d7467a28aa9f9e7351c9dcb4dac0e7a925&ssl=1&signature=8cece605eaf6c5a070e5e22c5144effb551920600e3e18c2a36ffcef11b27887
    [Aug 25 12:42:40] Scan process ended after forking.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Scan Engine Error: Request Signature Invalid’ is closed to new replies.