Support » Fixing WordPress » Site Health reporting cURL error 28 for exactmetircs.com is False

  • Ok, I’ve been on this hunt forever. Here’s what I suspect.
    WordPress is reporting this error falsely.

    “Your server is blocking external requests to exactmetrics.com, please check your firewall settings or contact your host for more details. Error message: cURL error 28: Resolving timed out after 2000 milliseconds”

    Here’s why.
    Ping to exactmetrics.com works fine.
    ping -c 2 exactmetrics.com

    curl to exactmetrics works fine.
    curl http://exactmetrics.com -I

    Wireshark reports traffic going to and from fine.
    ip.addr == 34.107.243.79
    Shows the full ICMP, HTTP and TCP responses for both commands from and to source and destination.

    So everything I throw at it reports connectivity is fine and dandy.
    Except … Site HEalth on WordPress.

    I even tried disabling the exactmetrics plugin from the site – what a stuff around – the same result, even with NOTHING talking to exactmetrics.com, I’m still seeing that error in Site Health.
    Exactmetrics shows the proper traffic on the Dashboard and updates fine.
    Go Figure.

    So, as it’s not actually broken – I’m just forgetting about it.
    So something is wrong somewhere and I can’t find it.

    Further, this is the Wireshark output for starting WordPress up with it running and showing the connections to exactmetrics on startup.`

    151334 1910.883343 192.168.0.15 34.107.243.79 TCP 78 55506 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 TSval=218080453 TSecr=0 SACK_PERM=1
    151335 1910.907105 34.107.243.79 192.168.0.15 TCP 74 443 → 55506 [SYN, ACK] Seq=0 Ack=1 Win=60192 Len=0 MSS=1380 SACK_PERM=1 TSval=942866260 TSecr=218080453 WS=256
    151336 1910.907237 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=1 Ack=1 Win=131328 Len=0 TSval=218080475 TSecr=942866260
    151337 1910.923766 192.168.0.15 34.107.243.79 TLSv1.3 583 Client Hello
    151338 1910.944775 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [ACK] Seq=1 Ack=518 Win=61440 Len=0 TSval=942866298 TSecr=218080490
    151339 1910.946885 34.107.243.79 192.168.0.15 TLSv1.3 1484 Server Hello, Change Cipher Spec
    151340 1910.947141 34.107.243.79 192.168.0.15 TCP 1484 443 → 55506 [ACK] Seq=1419 Ack=518 Win=61440 Len=1418 TSval=942866299 TSecr=218080490 [TCP segment of a reassembled PDU]
    151341 1910.947144 34.107.243.79 192.168.0.15 TLSv1.3 333 Application Data
    151342 1910.947210 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=518 Ack=2837 Win=129600 Len=0 TSval=218080513 TSecr=942866299
    151343 1910.947210 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=518 Ack=3104 Win=129344 Len=0 TSval=218080513 TSecr=942866299
    151344 1910.947921 192.168.0.15 34.107.243.79 TLSv1.3 146 Change Cipher Spec, Application Data
    151345 1910.948048 192.168.0.15 34.107.243.79 TCP 1434 55506 → 443 [ACK] Seq=598 Ack=3104 Win=131072 Len=1368 TSval=218080514 TSecr=942866299 [TCP segment of a reassembled PDU]
    151346 1910.948052 192.168.0.15 34.107.243.79 TLSv1.3 1041 Application Data
    151347 1910.970559 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [ACK] Seq=3104 Ack=1966 Win=64000 Len=0 TSval=942866324 TSecr=218080513
    151348 1910.975796 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [ACK] Seq=3104 Ack=2941 Win=66816 Len=0 TSval=942866330 TSecr=218080514
    151367 1911.494144 34.107.243.79 192.168.0.15 TLSv1.3 1484 Application Data
    151368 1911.494387 34.107.243.79 192.168.0.15 TLSv1.3 630 Application Data
    151369 1911.494443 34.107.243.79 192.168.0.15 TLSv1.3 1484 Application Data
    151370 1911.494447 34.107.243.79 192.168.0.15 TLSv1.3 903 Application Data
    151371 1911.494483 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=2941 Ack=5086 Win=129600 Len=0 TSval=218081054 TSecr=942866847
    151372 1911.494538 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=2941 Ack=7341 Win=127360 Len=0 TSval=218081054 TSecr=942866847
    151373 1911.494754 34.107.243.79 192.168.0.15 TLSv1.3 93 Application Data
    151374 1911.494836 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=2941 Ack=7368 Win=128768 Len=0 TSval=218081054 TSecr=942866847
    151375 1911.495109 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [FIN, ACK] Seq=7368 Ack=2941 Win=66816 Len=0 TSval=942866847 TSecr=218080514
    151376 1911.495170 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [ACK] Seq=2941 Ack=7369 Win=131072 Len=0 TSval=218081054 TSecr=942866847
    151377 1911.495202 192.168.0.15 34.107.243.79 TLSv1.3 90 Application Data
    151378 1911.498199 192.168.0.15 34.107.243.79 TCP 66 55506 → 443 [FIN, ACK] Seq=2965 Ack=7369 Win=131072 Len=0 TSval=218081057 TSecr=942866847
    151379 1911.518662 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [ACK] Seq=7369 Ack=2965 Win=66816 Len=0 TSval=942866872 TSecr=218081054
    151380 1911.520176 34.107.243.79 192.168.0.15 TCP 66 443 → 55506 [ACK] Seq=7369 Ack=2966 Win=66816 Len=0 TSval=942866873 TSecr=218081057
    ~ `
    ~

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator t-p

    (@t-p)

    Please check the error logs on your server for a more specific error message, which may give a clue to why this is happening on your website/server. If you need help locating them, ask your hosting provider to help you with that.

    Also ask your host:
    – If they can update Curl in case you are running an outdated version.
    – If there a firewall or security modules (e.g. mod_security ) that could block the outgoing cURL requests.
    – If there are any other limitations.

    Thread Starter Robert Chalmers

    (@shanghaitimes)

    Hi,
    I have no hosting provider, I do my own.
    There are no errors relating to this, other than the one produced by WordPress in its own Site Health space.
    Everything works, except for that message.

    Thanks
    Robert

    Moderator t-p

    (@t-p)

    Do you have WordPress debugging Enabled in wp-config.php?

    Do you see this in wp-config.php?
    define( 'WP_DEBUG', true );

    If you do, change it to:
    define( 'WP_DEBUG', false );

    If you turn off WordPress debugging, “Warnings” will not be displayed.

    • This reply was modified 1 year, 3 months ago by t-p.
    • This reply was modified 1 year, 3 months ago by t-p.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Site Health reporting cURL error 28 for exactmetircs.com is False’ is closed to new replies.