Scan failed to start and wp_remote_post() test back failed.

  • Resolved vishwajeet

    (@vishwajeetyadavpatil)


    2 years, 4 months ago

    Hi,

    I am unable to resolve the scan failed to start issue. Tried everything I could find in the forum. The scan is failed to start as well as receiving the error in diagnostic wp_remote_post() test back to this server failed! Response was: 403 Forbidden.

    Here is what I done so far:

    1. Tried enabling debug and start scan remotely.
    2. Added firewall rule in cloudflare to allow site ips as suggested
    3. whitelisted wordfence ips in cloudflare
    4. Other troubleshooting methods mentioned in wordfence documentation like checking ajax handler, disabling plugins, enabling Use the Cloudflare “CF-Connecting-IP etc.

    Here is error log:

    [Jul 26 15:02:01] Ajax request received to start scan.
[Jul 26 15:02:01] Entering start scan routine
[Jul 26 15:02:01] Got value from wf config maxExecutionTime: 20
[Jul 26 15:02:01] getMaxExecutionTime() returning config value: 20
[Jul 26 15:02:01] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.cryptominerbros.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=4d44ae27b14fe37e28dd5d133479a122&k=7e60c534202519340e7446fed471229385661e6425d202c2e1ada31d4fe46e5f870832f74d2df88a3c40257cb31b9d1281f247d5a71aca3a7646a7398549bfc3b9e3c161fb424c542904c523f41b2db4&ssl=1&signature=ad819f480aa12686f5b3bdac05f0dd98b6eeedc4e556e50056869f7cc5542aef
[Jul 26 15:02:01] Scan process ended after forking.
[Jul 26 15:02:04] Ajax request received to start scan.
[Jul 26 15:02:04] Entering start scan routine
[Jul 26 15:02:04] Got value from wf config maxExecutionTime: 20
[Jul 26 15:02:04] getMaxExecutionTime() returning config value: 20
[Jul 26 15:02:04] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.cryptominerbros.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=5a045ad3d5eb045eae6901e9f1849561&k=7e60c534202519340e7446fed471229385661e6425d202c2e1ada31d4fe46e5f870832f74d2df88a3c40257cb31b9d1281f247d5a71aca3a7646a7398549bfc3b9e3c161fb424c542904c523f41b2db4&ssl=1&signature=8e4d175820b9f80bee22ee051f2078ba0b873af64e4a6efa0f08685d58e1b22e
[Jul 26 15:02:04] Scan process ended after forking.
[Jul 26 15:02:07] Ajax request received to start scan.
[Jul 26 15:02:07] Entering start scan routine
[Jul 26 15:02:07] Got value from wf config maxExecutionTime: 20
[Jul 26 15:02:07] getMaxExecutionTime() returning config value: 20
[Jul 26 15:02:07] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.cryptominerbros.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=5779bc631de6f1c61be78465ae53d3fd&k=7e60c534202519340e7446fed471229385661e6425d202c2e1ada31d4fe46e5f870832f74d2df88a3c40257cb31b9d1281f247d5a71aca3a7646a7398549bfc3b9e3c161fb424c542904c523f41b2db4&ssl=1&signature=e45e3874077e985ba4492e19ff705a6acc788c526a6dd11e6feb8e4415c8adea
[Jul 26 15:02:08] Scan process ended after forking.
[Jul 26 15:04:29] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=7e60c534202519340e7446fed471229385661e6425d202c2e1ada31d4fe46e5f870832f74d2df88a3c40257cb31b9d1281f247d5a71aca3a7646a7398549bfc3b9e3c161fb424c542904c523f41b2db4&s=eyJ3cCI6IjYuMC4xIiwid2YiOiI3LjUuMTEiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvd3d3LmNyeXB0b21pbmVyYnJvcy5jb20iLCJzc2x2IjoyNjk0ODgxNDMsInB2IjoiNy40LjI5IiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy41OC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMSIsInN2IjoibmdpbnhcLzEuMTQuMCIsImR2IjoiNS43LjMwIiwibGFuZyI6IiJ9&betaFeed=0&action=timestamp
[Jul 26 15:16:41] Scan stop request received.

    But when I disable proxying in cloudflare it starts to work. I don’t know what else should be done with cloudflare to start the scan.

    Thanks,

    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)

    Hi @vishwajeetyadavpatil,

    Did you try to add our IPs to the Cloudflare whitelist in addition to those of your site? I also assume you’ve seen the notes around Scan process ended after forking, but considering that disabling proxying in Cloudflare fixes things, it may not apply in this case.

    In the Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs section, it can sometimes help to add trusted proxies. If you see multiple comma-separated IP addresses either on Wordfence > Tools > Diagnostics > IP(s) Used by this Server, or in IP Detection on that page (next to the in-use “CF-Connecting-IP” value) then you may need to add the one(s) that don’t correspond to your personal IP as seen on whatsmyip.org

    If none of the above seems to help, 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.

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

    Thanks,

    Peter.

    Thread Starter vishwajeet

    (@vishwajeetyadavpatil)

    Hi @wfpeter

    Thanks for the reply.

    All the ips found in ip detection CF-Connecting-IP and ips used by this server are added in trusted proxies as well as in cloudflare firewall rule to allow. Also, wordfence ips are whitelisted on cloudflare. But the issue still exist.
    I have sent you the diagnostic report by email.

    Thanks again,
    Vishwajeet

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Scan failed to start and wp_remote_post() test back failed.’ is closed to new replies.