The last discussed is :-

Hi @satbeer, apologies for the delay, we have been seeing this issue coming in exclusively from your hosting provider so have been attempting to converse with them and other customers seeing the same thing to find suitable resolutions to this issue.

Please can you ask your host if they have an outbound proxy or firewall that might limit or close connections, because outbound connections (in your diagnostic) from your site to noc1.wordfence.com are intermittently failing. Please inform them that these Wordfence servers used to be in the range 69.46.36.0/27 and have recently changed, in case the host had previously whitelisted those and need to whitelist the new IPs, which are 75.2.79.124 and 99.83.193.37.

Thanks,

Peter.
______

My hosting provider replyed

I have checked the server and could see the Wordfence IPs (75.2.79.124 and 99.83.193.37) are not blocked on our server and can connect to the IPs from the server without any issues. Since your domain is hosted on one of our shared servers, it is not possible to whitelist the IPs on it.

Also, I have checked the domain and it is loading fine from my end.
___

cURL error 56: OpenSSL SSL_read: Connection reset by peer, err no 104. The diagnostic report already shared from this account.

I have the same problem on all 3 of my websites and have already tried the troubleshooting tips.

This is a sample from one of them for which I have just emailed the diagnostic report.If required, I can send it for the other 2 websites too.

1. Unable to do manual update. This error was noticed around 24th January and I chose to wait for the next update which was on 26th January. I am not able to do a manual update.

The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was January 12, 2021 11:25 pm, so this site may be missing new rules added since then. You may wait for the next automatic attempt at February 2, 2021 11:33 pm or try to?Manually Update?by clicking the “Manually Refresh Rules” button below the Rules list.

2. Scan fail error: I am receiving this message every time I try to do a scan

Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104

I have checked the connectivity and it appears alright. I also am receiving notifications of plugin updates required.

Please help.

Thanks in advance

We have defined proxy settings in wp-config.php file and noticed that any proxy server that uses ports above 30000 range (31112 for example) does not work. If we use lower port ranges such as 22225 it works as expected.

We have checked our VPS firewalls and disabled all other plugins on the WP installation. No difference there.

We have also verified that the VPS can connect to proxies by executing curl commands on cli and even created example php file that makes a call via these proxies. All works as expected (so server itself has no issues with these port ranges).

This issue only emerges with wp core.

Error received is “cURL error 56: Proxy Connect Aborted”.

I am getting a cURL error 56 in WP Super Cache. That is because my server company will not allow loopbacks.

Is there a workaround that you can recommend?

Thanks
Terr5y

I get the following error message when I try to connect:

Network: CURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html).

Thanks

An error occurred while fetching file from: https://..demo_import/demo2/demo2.xml!
Reason: http_request_failed – cURL error 56: Failure when receiving data from the peer.

Could you tell me how to fix this error?

Thank you so much!