xcarnell

The connectivity error is always there.

The output was:

|||* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* 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 multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55afa566f540)
> GET / HTTP/2
> Host: noc1.wordfence.com
> user-agent: curl/7.74.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
< date: Thu, 28 Mar 2024 20:58:20 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
<
* Connection #0 to host noc1.wordfence.com left intact
{"errorMsg":"Wordfence API error: Your site did not send an API key when contacting the Wordfence servers."}%   |||