HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443)

Help
1

I have a personal domain that I host for my nextcloud on (I'd rather not disclose)
when I try: sudo certbot renew
I get

Failed to renew certificate [ncloud.mydomain.com](http://ncloud.mydomain.com  with error: HTTPSConnectionPool(host='[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at ...

Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

mydomain.com points to another VPS for a school project that is https enabled
ncloud.mydomain.com points to server at home and returns the error when I try to renew

Errno -3 is about DNS? (my nextcloud is functional and reachable without certificate btw)

when I do : dig duck.com >>> a delay and then a timeout

<<>> DiG 9.16.33-Debian <<>> duck.com
 global options: +cmd
 connection timed out; no servers could be reached

I recently (2-3 months ago) set up the school project, mydomain.com to point to another VPS, its is probably the cause but how do I fix it? School is out so I can, I don't need the project anymore...

2

DNS resolving is broken for whatever system you're running Certbot in.

4 Likes
3

nano etc/resolv.conf to add alternative dns server, I don't know what broke it in the first place. :thinking:
nameserver 1.1.1.1

4

Will that DNS setting survive a reboot?

My /etc/resolve.conf file has this in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
3 Likes
5

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