starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #2192] Issue when requesting a new Let's Encrypt SSL certificate #1570

New issue

Closed

opened 2026-02-26 07:31:36 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:31:36 +03:00

Owner

Originally created by @kefdk on GitHub (Aug 7, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2192

Describe the bug
When requesting a new SSL certificate from Let's Encrypt, I get a Internal Error.

Looking into my log through Docker, I get the following error message:

[8/6/2022] [8:39:32 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[8/6/2022] [8:39:37 AM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #39: xxx.yyy.zzz
[8/6/2022] [8:39:37 AM] [SSL      ] › ℹ  info      Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-39" --agree-tos --authenticator webroot --email "my@mail.com" --preferred-challenges "dns,http" --domains "xxx.yyy.zzz" 
[8/6/2022] [8:39:40 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[8/6/2022] [8:39:40 AM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-39" --agree-tos --authenticator webroot --email "my@mail.com" --preferred-challenges "dns,http" --domains "xxx.yyy.zzz" 
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Some challenges have failed.

Nginx Proxy Manager Version
Version 2.9.18

To Reproduce
Steps to reproduce the behavior:

Create a new Proxy Hosts
Go to SSL section for the Proxy Host.
Select "Request a new SSL Certificate (with Let's Encrypt)"
Input an e-mailaddress in the "Email Address for Let's Encrypt" (in my case auto filled).
Check the "I Agree to the Let's Encrypt Terms of Service".
Click Save
After some waiting time, the message "Internal Error" is displayed and no SSL certificate is retrieved.

Expected behavior
I expected a certificate for my domain to be created and added to the Proxy Host.

Extra info
It looks like renewal of my existing certificates works fine, so it's only requesting a new certificate that is an issue.

I'm running my installation on a Docker, and been running it for over 2 years without any issues. The last time I know this was working was in 19th February 2022.

Originally created by @kefdk on GitHub (Aug 7, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2192 **Describe the bug** When requesting a new SSL certificate from Let's Encrypt, I get a Internal Error. Looking into my log through Docker, I get the following error message: ``` [8/6/2022] [8:39:32 AM] [Nginx ] › ℹ info Reloading Nginx [8/6/2022] [8:39:37 AM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #39: xxx.yyy.zzz [8/6/2022] [8:39:37 AM] [SSL ] › ℹ info Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-39" --agree-tos --authenticator webroot --email "my@mail.com" --preferred-challenges "dns,http" --domains "xxx.yyy.zzz" [8/6/2022] [8:39:40 AM] [Nginx ] › ℹ info Reloading Nginx [8/6/2022] [8:39:40 AM] [Express ] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-39" --agree-tos --authenticator webroot --email "my@mail.com" --preferred-challenges "dns,http" --domains "xxx.yyy.zzz" Saving debug log to /var/log/letsencrypt/letsencrypt.log Some challenges have failed. ``` **Nginx Proxy Manager Version** Version 2.9.18 **To Reproduce** Steps to reproduce the behavior: 1. Create a new Proxy Hosts 2. Go to SSL section for the Proxy Host. 3. Select "Request a new SSL Certificate (with Let's Encrypt)" 4. Input an e-mailaddress in the "Email Address for Let's Encrypt" (in my case auto filled). 5. Check the "I Agree to the Let's Encrypt Terms of Service". 6. Click Save 7. After some waiting time, the message "Internal Error" is displayed and no SSL certificate is retrieved. **Expected behavior** I expected a certificate for my domain to be created and added to the Proxy Host. **Extra info** It looks like renewal of my existing certificates works fine, so it's only requesting a new certificate that is an issue. I'm running my installation on a Docker, and been running it for over 2 years without any issues. The last time I know this was working was in 19th February 2022.

kerem

2026-02-26 07:31:36 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:31:37 +03:00

Author

Owner

@kefdk commented on GitHub (Aug 7, 2022):

Issue was server related. Found it after three days of debugging.

@kefdk commented on GitHub (Aug 7, 2022): Issue was server related. Found it after three days of debugging.

kerem commented

2026-02-26 07:31:37 +03:00

Author

Owner

@BenJule commented on GitHub (Sep 7, 2022):

What was the issue?

@BenJule commented on GitHub (Sep 7, 2022): What was the issue?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1570

No description provided.

Rows
Columns