My domain is: hemphealth.cc I ran this command: sudo certbot --nginx -d hemphealth.cc -d www.hemphealth.cc It produced this output: requests.exceptions.SSLError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by SSLError(SSLError("bad handshake: SysCallError(-1, 'Unexpected EOF')"))) My web server is (include version): NGINX 1.18.0 The operating system my web server runs on is (include version): Ubuntu 20.04 My hosting provider, if applicable, is: OVH US I can login to a root shell on my machine: Yes I'm using a control panel to manage my site: No The version of my client is: certbot 0.40.0 I am going to assume that this is just a DDOS mitigation issue given that OVH tends to have a lot of blocked IP's. How can I proceed?

[image] _netwolf: How can I proceed? We probably need the help of @lestaff to check if your IP address is blocked indeed.

Yup; it looks like the "temporary" blocking described in this thread: [image] New "bad handshake" & similar errors Help H…

Awesome, thank you for your help.

Try: curl -v https://acme-v02.api.letsencrypt.org/directory OR curl -I https://acme-v02.api.letsencrypt.org/directory

I went ahead and ran the command, this is the output: curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443 I am assuming it's a blocked ip, just a waiting game atm, thank you all for your help

Which is to be expected if requests also couldn't connect. Let's wait until the LE staff has decided if the IP is blocked or not. @_netwolf You might be asked to PM the IP address involved.

[image] _netwolf: I am assuming it's a blocked ip It seems that way. We can confirm that curl is working with another test: curl -I https://google.com/ Then we can be even more sure - LOL

One can never be too sure, might just ping google to verify. :laughing:

Yes, we had blocked this IP address as part of mitigating a DDoS attack. It's unblocked now. If you've had this IP address for more than a couple of months, then it's likely that your system is compromised and you'll need to thoroughly investigate.

Yep, the service was started 8-14-2021 at 1200 CST. OVH is notoriously bad with responding to tickets, thank you for helping me out.

Bad Handshake issue, Unable to Connect to LetsEncrypt server

Help

petercooperjr August 14, 2021, 8:27pm 3

Yup; it looks like the "temporary" blocking described in this thread:

Topic		Replies	Views
Certbot bad handshake issue Help	2	1132	April 2, 2021
SSLError : bad handshake Help	3	867	March 27, 2022
Creation of certificate fails with certbot and certbot-auto Help	3	1224	February 26, 2020
Check if IP is blocked HTTPSConnectionPool(host=‘acme-v02.api.letsencrypt.org’, port=443): Help	8	1043	September 26, 2023
“bad handshake” & similar errors related to previous ddos tor exit node attack? Help	2	896	April 5, 2021

Bad Handshake issue, Unable to Connect to LetsEncrypt server

Related topics