wp_remote_post() test back to this server failed!

I found an option to send the report and shared the report at

[email protected]

. Can you please help me with this?

Thank You.

Hi @qph9697

The diagnostics report hasn’t arrived.

Please go to the top of the Diagnostics tab on the Wordfence Tools page. If you have at least Wordfence version 7.4.9 installed then there will be an EXPORT button at the top of the page to export a diagnostics report text file.

Place the text file in a ZIP archive, attach it to an email and send your email to wftest [at] wordfence [dot] com

Make sure to put your username qph9697 in the subject field of the email so I can find it.

Let me know here when the email has been sent.

Hi @wfphil,

I have zipped the file and shared an email at your email address, with the subject “Username: qph9697”. Please have a look.

Thank You.

And there are times when it says “OK” in green and after some time, automatically goes to “red with a [cross]” displaying the same issue.

Hi @qph9697,

The error below means that WordPress is unable to send requests back to itself.

[FAIL] wp_remote_post() test back to this server failed! Response was: 500 Internal Server Error

I see that you are using the Ezoic advertising platform and Cloudflare due to the IP addresses detected in the report.

The failure reports:

Error communicating with origin

This indicates that the test request WordPress sends back to itself is not reaching your hosting server. You will need to ask your hosting provider, Ezoic and Cloudflare to help you resolve the cause of why WordPress is unable to send requests back to itself.

Thank you, @wfphil. I will contact my hosting, and will update you.

And @wfphil,

How can I whitelist some IPs, which I guess wordfence might be blocking?

I am unable to find the option to whitelist an IP.

Hi @qph9697

Thank you for the update.

What IP addresses do you want to add to the allowlist and why?

Who owns the IP addresses?

Hi,

The error I was getting was becuase, wordfence was blocking the ezoic ips, when I whitelisted the ezoics ip addresses, the error was gone. And the scan worked perfectly fine.

Hi @qph9697

Thank you for the update.

You do not want to add all of Ezoic’s IP addresses to the Wordfence allowlist as it can be dangerous to do so. I recommed that you remove them.

How do you know for a fact that Wordfence was blocking Ezoic IP addresses?

Hi @wfphil,

Actually I didn’t added all the ip address, earlier my hosting server used to block the ezoics ip due to which my users used to get an “origin error”, to rectify this issue, I was asked to add a small list of ips below 30, so that the issue will get resolved.

I asked ezoic support team and they told me that, for many users, the error 500 internal error with “error connecting to the origin” which I was facing was because wordfence might have blocked the ezoics ip and hence is causing an error to connect to the server. And was asked to whitelist the ips(below 30), as soon as I did, I stopped getting the origin error and the issue was also resolved. With a green Ok mark in diagnostic tab.

Should I whitelist on the server end only? Or at wordfence?

Is there any drawback of whitelisting from wordfence end?

• This reply was modified 3 years, 5 months ago by qph9697.

Hi @qph9697

Thank you for the update.

Do you know why your hosting provider was blocking Ezoic IP addresses?

Are you saying that the Ezoic IP addresses you were asked to add to an allowlist were added to a IP address allowlist on the server and not added to the IP address allowlist in Wordfence?

We have seen in the past that Ezoic don’t fully understand how Wordfence works. See our guide below under the heading “If you are using the Ezoic advertising platform”:

https://www.wordfence.com/help/dashboard/options/#general-wordfence-options

• This reply was modified 3 years, 5 months ago by wfphil.

Hi @wfphil,

Thank you for the information.

And since I was getting an origin error, I contacted my hosting provider. According to ezoic, they offer many options to make sure, that my host will be able to see the visitor’s IP addresses and not the ezoic addresses. But since my hosting does not offer changes at the server level for shared hosting, I was made to go with whitelisting the ezoic’s IP.

But, since the same error was occurring in wordfence, then after talking to the ezoic team, they also asked me to whitelist the IPs, if my hosting cannot move forward with other methods, at server level then.

Hi @qph9697

Thank you for the update.

When you said, “when I whitelisted the ezoics ip addresses, the error was gone.”

Where precisely did you add those IP addresses?

I did that in wordfence at first.

I added all the ips in wordfence whitelist list and the issue was gone.

But after that, I found that the ips were not whitelisted at the server level at my host, due to some .htaaccess file issue.

So I whitelisted the ips at the host level too, and removed from the ips from wordfence, and after that I didn’t faced any issue.