Unable to get a SSL cert for my proxies

Help
1

I have been trying for the past few hours to get an SSL cert for my self hosted docker containers so that I can access them. I am able to get them running, but when I attempt to get the SSL certificate for HTTPS, it says "Internal Error" and does not allow me to go through with it. I am using nginx proxy manager. I am a huge novice to self hosting and linux, so forgive me if I am not knowledgable in some things. And, yes, I RTFM, that didn't make it any easier for me

My domain is: http://cloud.hungnir.work

I ran this command: I ran the Request a New SSL Certificate page on my NPM site.

It produced this output: Internal error, here is a more detailed log:

 "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-4" --agree-tos --authenticator webroot --email 'redacted@outlook.com' --preferred-challenges "dns,http" --domains "cloud.hungnir.work"
[10/4/2025] [8:25:30 AM] [Global   ] › ⬤  debug     CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-4" --agree-tos --authenticator webroot --email 'redacted@outlook.com' --preferred-challenges "dns,http" --domains "cloud.hungnir.work"
[10/4/2025] [8:25:41 AM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/temp/letsencrypt_4.conf
[10/4/2025] [8:25:41 AM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[10/4/2025] [8:25:41 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[10/4/2025] [8:25:41 AM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload
[10/4/2025] [8:25:41 AM] [Express  ] › ⚠  warning   Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Some challenges have failed.
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.

My web server is (include version): v2.12.6

The operating system my web server runs on is (include version): Ubuntu 24.04.3 LTS

My hosting provider, if applicable, is: myself

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): Not sure what this means, but I am using NPM

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): N/A, "command certbot not found"

2 
 /tmp/letsencrypt-log/letsencrypt.log

get that log file then we can start: think forum doesn't like NPM becase it stash away any certbot side logs.

2 Likes
3

Yes, the log @orangepizza describes would be helpful.

But, you don't have any A or AAAA records in your DNS. One or both are needed to complete the HTTP Challenge using --webroot that you chose.

An A and/or AAAA record is needed for anyone to reach your server from the public internet. Not just Let's Encrypt

3 Likes
4

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