wp_remote_post() test back to this server failed

Resolved pcgtech
(@pcgtech)

4 years, 5 months ago

I’m unable to start a scan on my site. When I check the connectivity status on the Diagnostic page, I get this error:

wp_remote_post() test back to this server failed! Response was: 200 OK

I followed the steps on the “Scan won’t start” part of the help document, including “Start scan remotely” but haven’t had any success.

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

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

Plugin Support wfpeter
(@wfpeter)

4 years, 5 months ago
Hi @pcgtech, thanks for getting in touch!

As you’ve tried the scan troubleshooting documentation already, it’d be good to see what exactly is happening when the scan fails:
- 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.
Wordfence > Tools > Diagnostic > Debugging Screenshot

Can you also 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 pcgtech
(@pcgtech)

4 years, 5 months ago

Thanks for your help Peter!

The scan did not finish, but here are all the log entries. I removed my site URL but it’s the same as above.

[Dec 09 04:23:15] Scheduled Wordfence scan starting at Thursday 9th of December 2021 04:23:15 AM
[Dec 09 21:11:59] Scan stop request received.
[Dec 09 21:22:25] Scan stop request received.
[Dec 09 21:24:13] Scan stop request received.
[Dec 10 16:53:04] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=8e20202b11654047a5be1edf24010b99e2b38b4f33445ea1cbeb425a05bc3260c2950921a097873ed675e3cd1a0e4d7009d8851b728b9fb2bc8e54c5fb024baa4bd247c0f58a52e0444ecb97b5cdb448&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC93d3cudGVhbXJvY2tpbnJvYmJpbnMuY29tIiwic3NsdiI6MjY4NDQzODM5LCJwdiI6IjcuMy4zMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuMjkuMCIsImNzIjoiTlNTXC8zLjUzLjEiLCJzdiI6IkFwYWNoZSIsImR2IjoiMTAuMS40MS1NYXJpYURCIiwibGFuZyI6IiJ9&betaFeed=0&action=timestamp
[Dec 10 16:53:13] Scan stop request received.
[Dec 10 16:53:16] Ajax request received to start scan.
[Dec 10 16:53:16] Entering start scan routine
[Dec 10 16:53:16] Got value from wf config maxExecutionTime: 0
[Dec 10 16:53:16] Got max_execution_time value from ini: 30
[Dec 10 16:53:16] getMaxExecutionTime() returning half ini value: 15
[Dec 10 16:53:16] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/%5BURL RETRACTED]/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=dab9ec4c1b9657e330822d279b2fcb3a&k=8e20202b11654047a5be1edf24010b99e2b38b4f33445ea1cbeb425a05bc3260c2950921a097873ed675e3cd1a0e4d7009d8851b728b9fb2bc8e54c5fb024baa4bd247c0f58a52e0444ecb97b5cdb448&ssl=1&signature=801573d2ea9763d6077baceccc1f960bf55f528db663ba2339815a0ae22ae00d
[Dec 10 16:53:17] Scan process ended after forking.
[Dec 10 16:54:17] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=8e20202b11654047a5be1edf24010b99e2b38b4f33445ea1cbeb425a05bc3260c2950921a097873ed675e3cd1a0e4d7009d8851b728b9fb2bc8e54c5fb024baa4bd247c0f58a52e0444ecb97b5cdb448&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC93d3cudGVhbXJvY2tpbnJvYmJpbnMuY29tIiwic3NsdiI6MjY4NDQzODM5LCJwdiI6IjcuMy4zMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuMjkuMCIsImNzIjoiTlNTXC8zLjUzLjEiLCJzdiI6IkFwYWNoZSIsImR2IjoiMTAuMS40MS1NYXJpYURCIiwibGFuZyI6IiJ9&betaFeed=0&action=timestamp
[Dec 10 16:55:29] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=8e20202b11654047a5be1edf24010b99e2b38b4f33445ea1cbeb425a05bc3260c2950921a097873ed675e3cd1a0e4d7009d8851b728b9fb2bc8e54c5fb024baa4bd247c0f58a52e0444ecb97b5cdb448&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC93d3cudGVhbXJvY2tpbnJvYmJpbnMuY29tIiwic3NsdiI6MjY4NDQzODM5LCJwdiI6IjcuMy4zMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuMjkuMCIsImNzIjoiTlNTXC8zLjUzLjEiLCJzdiI6IkFwYWNoZSIsImR2IjoiMTAuMS40MS1NYXJpYURCIiwibGFuZyI6IiJ9&betaFeed=0&action=timestamp

I have also sent the diagnostics report to the email as requested.

Plugin Support wfpeter
(@wfpeter)

4 years, 5 months ago

Hi @pcgtech, thanks for sending us that report.

I am receiving a wp_remote_post() test back to this server failed! Response was: 200 OK and the response is your homepage. This suggests to me that your theme or a plugin has been configured to redirect paths such as /wp-admin to your homepage rather than show the login page. This can be a problem for Wordfence and other plugins that need to access standard WordPress paths in order to connect.

You can test this yourself by disabling all plugins except for Wordfence and reverting to a default theme such as Twenty Twenty-One. Now try scanning again. Does the error still display when Wordfence is the only plugin enabled on a “fresh” theme? If not, you may be able to re-enable your plugins and theme one-by-one until you find where the problem originates.

You can install a maintenance mode plugin during this time if site visitors are likely to be affected.

Thanks,

Peter.

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

The topic ‘wp_remote_post() test back to this server failed’ is closed to new replies.