Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
openssl s_client -connect acme-v02.api.letsencrypt.org:44
It produced this output:
no peer certificate available
No client certificate CA names sent
SSL handshake has read 0 bytes and written 295 bytes
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
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):n/a
I am using acme client gem(2.0.1) for ruby, and the system works at many sites, however I have this one site that is getting the above described error trying to create an ssl connection. I found a couple posts about it, the one that looked the most similar ended with, 'well, it fails from 1 isp, but not from the other, so we're happy.'
I did wireshark the transaction, and it appeared to me that the rst was coming from lets encrypt's side. the command continues to work from other sites. Wondering where I should look to resolve.
thanks in advance,