Uptime monitor "Connection was reset remotely during SSL handshake"

I use Manage WP to monitor my site, which uses Site24x7 to monitor uptime. Manage WP told me I should reach out to Let's Encrypt to help with this error: "Connection was reset remotely during SSL handshake" which is causing the uptime monitor to disconnect.

Manage WP shared this link: Troubleshooting SSL handshake spikes - Site24x7 Forum

My domain is: valeowc.com

My web server is (include version): Linux

The operating system my web server runs on is (include version): Wordpress 5.6

My hosting provider, if applicable, is: Dotster

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

1 Like

Hi @pamvan,

It looks like a subtle problem to me. I ran these tests:


Although you can see errors reported, the errors are relatively minor and I don't believe that any of them are relevant to what you're seeing with the Site24x7 monitor.

Is it possible to get some more information from Site24x7 to help investigate?

In particular, does this error occur every time or just occasionally? Can they provide any further technical details about the connection error?

It seems like this particular error would typically be caused by a firewall or other anti-abuse system run by your hosting provider (which somehow decided that some of the connections from Site24x7 were abusive, excessive, or forbidden). Can you ask the hosting provider whether this could be the case for some reason?

I don't believe that there's anything wrong with your certificate or your HTTPS setup itself—the tests that I linked above (and my own browser-based testing) indicate to me that these configurations are actually OK and not particularly problematic. (The error messages that appear in these tests could point to potential configuration improvements, but again, I don't believe they would be directly capable of causing the specific error that you reported from Site24x7.)


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.