My web server is (include version): Apache2 version 2.4 The operating system my web server runs on is (include version):Opensuse Leap15.1 I can login to a root shell on my machine (yes or no, or I don't know):Yes I'm using a control panel to manage my site :Yes Client is :Certbot version=1.4.0 C…

[image] Rich64: certbot==1.4.0 not too old [image] Rich64: What exactly is Certbot moaning about [image] Rich64: ConnectionError: HTTPSConnectionPool(host=' acme-v02.api.letsencrypt.org ', port=443) Try: nslookup acme-v02.api.letsencrypt.org ifconfig | grep -Ei 'add|inet' cur…

Only if you can use DNS authentication. HTTP authentication would fail; as the challenge request would try the IP of the FQDN directly.

Thanks a lot. Will give it a try. Regards.

[image] rg305: Only if you can use DNS authentication. HTTP authentication would fail; as the challenge request would try the IP of the FQDN directly. I used this code: sudo certbot run --cert-name keta.com.ng -a manual --preferred-challenges dns -d keta.com.ng,www.keta.com.ng -i apache An…

@lestaff [image] Rich64: HTTPSConnectionPool(host=' acme-v02.api.letsencrypt.org ', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f775635a668>: Failed to establish a new connection: [Errno -3] Temporary…

@rg305 's advice is correct. Most often this type of error "Temporary failure in name resolution" is due to a local networking problem on the subscriber's network, for instance a broken recursive resolver. That tends to show up on the /directory request because it's the first request the client makes…

Thanks for the prompt response, Jacob. :slightly_smiling_face: Since this is out of a certificate-seeker's control, I wanted to ensure that it wasn't becoming a trend. I have not as yet seen this with my own ACME client.

[image] rg305: [image] Rich64: certbot==1.4.0 not too old [image] Rich64: What exactly is Certbot moaning about [image] Rich64: ConnectionError: HTTPSConnectionPool(host=' acme-v02.api.letsencrypt.org ', port=443) Try: nslookup acme-v02.api.letsencrypt.org ifconfig | grep -…

[image] griffin: Thanks for the prompt response, Jacob. :slightly_smiling_face: Since this is out of a certificate-seeker's control, I wanted to ensure that it wasn't becoming a trend. I have not as yet seen this with my own ACME client. @griffin Thanks a lot! especially for helping to call …

[image] jsha: @rg305 's advice is correct. Most often this type of error "Temporary failure in name resolution" is due to a local networking problem on the subscriber's network, for instance a broken recursive resolver. That tends to show up on the /directory request because it's the first reques…

Can I use Certbot for any certification?

Help

griffin October 13, 2020, 4:34pm 6

@lestaff

Several instances of this same issue have cropped up lately. Any ideas?

Topic		Replies	Views
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None An unexpected error occurred: Help	6	2556	November 10, 2023
Error running certbot Help	9	876	November 14, 2023
Error requesting certificate Help	7	1943	March 18, 2022
Error updating certificates Help	7	502	August 18, 2022
Error run certbot Help	3	1945	October 9, 2021

Can I use Certbot for any certification?

Related topics