Connectivity Error (Connecting Back to Site) wp_remote_post

Hi @nbexiga, thanks for your message.

Seeing a connectivity error in IPv6 isn’t uncommon as not all hosts support it, even if something such as Cloudflare assigns an address.

For the first one, surprisingly SSL routines::wrong version number doesn’t always point to an issue with the version number itself, and could be version indicators during the handshake with our server, or even an issue with a proxy server. In most cases for this that I can see, configuration changes need to be made at the server. I would recommend reaching out to your host or network admin to see if they can see any problems with SSL on your server.

They may be able to try running curl -v https://noc1.wordfence.com/. If they can’t resolve it from the feedback given there, you could send us a copy of the output to see if we can see what might be going wrong.

Let us know what you find out,
Peter.

Hello

Sorry for late reply.

Kindly see the output . Also i have errors in the Site Health. I atached a image if you can help me with that, because i think those are related.

https://ibb.co/tC1JRj5
https://ibb.co/P9MwztB

root@vmi1576139:~# curl -v https://noc1.wordfence.com/

• Trying 52.25.185.95:443…
• Connected to noc1.wordfence.com (52.25.185.95) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• CAfile: /etc/ssl/certs/ca-certificates.crt
• CApath: /etc/ssl/certs
• TLSv1.0 (OUT), TLS header, Certificate Status (22):
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.2 (IN), TLS header, Certificate Status (22):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.2 (IN), TLS header, Finished (20):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.2 (OUT), TLS header, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
• ALPN, server accepted to use h2
• Server certificate:
• subject: CN=noc1.wordfence.com
• start date: Jun 12 00:00:00 2023 GMT
• expire date: Jul 10 23:59:59 2024 GMT
• subjectAltName: host “noc1.wordfence.com” matched cert’s “noc1.wordfence.com”
• issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
• SSL certificate verify ok.
• Using HTTP2, server supports multiplexing
• Connection state changed (HTTP/2 confirmed)
• Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• Using Stream ID: 1 (easy handle 0x55d2d0703eb0)
• TLSv1.2 (OUT), TLS header, Supplemental data (23):

GET / HTTP/2
Host: noc1.wordfence.com
user-agent: curl/7.81.0
accept: /

• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
  < HTTP/2 200
  < date: Mon, 01 Apr 2024 21:22:51 GMT
  < content-type: text/plain
  < content-length: 108
  < server: nginx
  < x-frame-options: SAMEORIGIN
  < x-xss-protection: 1; mode=block
  < x-content-type-options: nosniff
  < strict-transport-security: max-age=31536000; includeSubDomains
  <
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• Connection #0 to host noc1.wordfence.com left intact

curl: (35) OpenSSL/3.0.2: error:0A00010B:SSL routines::wrong version number