# Unable to get a SSL cert for my proxies **URL:** \ **Category:** Help\ **Created:** [October 4, 2025, 8:38am UTC](https://community.letsencrypt.org/t/unable-to-get-a-ssl-cert-for-my-proxies/241930 "2025-10-04T08:38:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![isaiah-lol](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/isaiah-lol/32/89151_2.png) [@isaiah-lol](https://community.letsencrypt.org/u/isaiah-lol)\ **Post date:** [October 4, 2025, 8:38am UTC](https://community.letsencrypt.org/t/unable-to-get-a-ssl-cert-for-my-proxies/241930/1 "2025-10-04T08:38:55Z")
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](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: ```nohighlight "/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"** ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [October 4, 2025, 12:01pm UTC](https://community.letsencrypt.org/t/unable-to-get-a-ssl-cert-for-my-proxies/241930/2 "2025-10-04T12:01:48Z")
```nohighlight /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. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [October 4, 2025, 1:13pm UTC](https://community.letsencrypt.org/t/unable-to-get-a-ssl-cert-for-my-proxies/241930/3 "2025-10-04T13:13:42Z")
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 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [November 3, 2025, 1:14pm UTC](https://community.letsencrypt.org/t/unable-to-get-a-ssl-cert-for-my-proxies/241930/4 "2025-11-03T13:14:01Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.