Trying to request a new SSL Cert but am getting weird error

Help
1

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. crt.sh | 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: tijn-lab.nl

I ran this command: (Trying to request a new ssl cert through nginx proxy manager with CF dns

It produced this output:

CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
An unexpected error occurred:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:410:5)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

The operating system my web server runs on is (include version): lxc container running debian 12

My hosting provider, if applicable, is: proxmox

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 (no, or provide the name and version of the control panel): yes nginx proxy manager v2.12.2

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

here is also the link to the logs that it produced

but in short i've been trying to request a new ssl certificate for my domain but cant get it to work sometimes it doesnt even show that error it just says "Internal Error"

2

For some reason, the host that's running your NPM does not have any DNS resolving capabilities.

You probably need to look at this LXC container thing and if for some reason that's making it not being able to resolve hostnames. Does it have network connectivity to begin with?

2 Likes
3

You're absolutely right thats something i should've checked first.
I actually installed tailscale recently on my proxmox install that changed something in the dns i returned it back to normal now it works again

4 Likes