Wordfence could not register with the Wordfence scanning servers when it activat

Hi @slavik67

In the Debugging Options section on the Tools >> Diagnostics page, disable the option Enable SSL Verification (Disable this if you are consistently unable to connect to the Wordfence servers.)

Press the SAVE CHANGES button.

Let me know if that fixes it.

Thanks for the advice. I did everything as you wrote. But unfortunately the problem has not disappeared.
I will add: Recently, in order to increase the PHP, the hosting provider moved all my sites to a new server. The problem started immediately on all my sites. IP of the new server 92.53.96.150

Hi @slavik67

Thank you for the update.

Can you ask your hosting provider if they are blocking outgoing connections to these IP addresses:

44.239.130.172
44.238.191.15
35.155.126.231
54.68.32.247
44.235.211.232
54.71.203.174

For one website with the error shown below can you send at your Wordfence diagnostics report. Please go to the top of the “Diagnostics” tab on the Wordfence “Tools” page. There will be a “SEND REPORT BY EMAIL” button to send the diagnostics report. Enter wftest [at] wordfence [dot] com as the email and slavik67 as the forum username please.

“Connecting to Wordfence servers (https) wp_remote_post() test to noc1.wordfence.com failed! Response was: cURL error 28: Connection timed out after 10000 milliseconds”

Hi
Thank you for help.
I asked the hosting provider a question about blocking IP.
The report was sent.
“Email Diagnostic Report
Diagnostic report has been sent successfully.”

Thank you.

Hi @slavik67

Thank you for the update.

Let me know what your hosting provider says.

Hi,
Hostin replied:
“These addresses do not accept requests from both servers and other devices, incl. not related to Timeweb (this is my hosting).
In the ping attachment from my pc (from the server also 100% loss)

They also attached a screenshot of the ping.

The hosting provider wrote another comment:
“Please check with the plug-in’s technical support how we can check the availability of their ip-addresses, since the ping command does not deliver any of the packets, both from local devices and from our servers, and from the server on which your site is worked before. ”

my hosting site timeweb [dot] com

Hi @slavik67

Thank you for the update.

Can you ask the hosting provider to run the command below on the command line interface for the server for this website and paste the output in a reply:

curl -v https://noc1.wordfence.com

cl02774@vh300:~$ curl -v https://noc1.wordfence.com
* Rebuilt URL to: https://noc1.wordfence.com/
* Trying 44.239.130.172…
* TCP_NODELAY set
* Connected to noc1.wordfence.com (44.239.130.172) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=*.wordfence.com
* start date: Oct 30 00:00:00 2020 GMT
* expire date: Nov 28 23:59:59 2021 GMT
* subjectAltName: host “noc1.wordfence.com” matched cert’s “*.wordfence.com”
* issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
* SSL certificate verify ok.
> GET / HTTP/1.1
> Host: noc1.wordfence.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Thu, 03 Jun 2021 13:38:02 GMT
< Content-Type: application/octet-stream
< Content-Length: 108
< Connection: close
< Content-Type: text/plain
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Strict-Transport-Security: max-age=31536000; includeSubDomains
<
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
{“errorMsg”:”Wordfence API error: Your site did not send an API key when contacting the Wordfence servers.”}

Hi @slavik67

Thank you for the update.

We believe that the issue is either a local certificate configuration issue on your hosting server or the ability of the cURL PHP extension being unable to access those local certificates.

Good day.
Imagine, everything worked for me, I didn’t change anything, I deactivated the plugin and reactivated it. And it all worked. Wonders….
Thank you so much for your time and help.

ОК

Hi @slavik67

Thank you for the update.

If it happens again please refer to my last reply and pass that reply to your hosting provider to look at.