starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 09:55:51 +03:00

[GH-ISSUE #3411] Error while creating ssl certificate #2282

New issue

Closed

opened 2026-02-26 07:34:50 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:34:50 +03:00

Owner

Originally created by @arndel90 on GitHub (Dec 22, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3411

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
My domain is:
ardelplanque.ovh

I have nginx proxy manager installed, port 80 and 443 open in my router and it points to my server.
adding a proxy host works in http (accessible in LAN et WAN).

when i want to add a ssl certificate it gave me the following error message :

Error: Command failed: 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 "my_email@mail.com" --preferred-challenges "http" --domains "plex.ardelplanque.ovh"
Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
An unexpected error occurred:
requests.exceptions.SSLError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by SSLError(SSLError(1, '[SSL: TLSV1_UNRECOGNIZED_NAME] tlsv1 unrecognized name (_ssl.c:1056)')))
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 ChildProcess.exithandler (node:child_process:402:12)
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)

i've search for an answer but can't find anything related.

certbot 2.5.0

thanks for reading ;-)

Nginx Proxy Manager Version
2.10.4

To Reproduce
Steps to reproduce the behavior:

Go to 'host->proxy hosts->add proxy host'
complete the form to add a proxy host, and request a new SSL certificate (same happend when request a certificate before adding the proxy host).
See error

Expected behavior
adding the proxy host with a SSL certificate

Operating System
omv6 with docker and portainer, nginx PM in container

Originally created by @arndel90 on GitHub (Dec 22, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3411 - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** My domain is: ardelplanque.ovh I have nginx proxy manager installed, port 80 and 443 open in my router and it points to my server. adding a proxy host works in http (accessible in LAN et WAN). when i want to add a ssl certificate it gave me the following error message : Error: Command failed: 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 "my_email@mail.com" --preferred-challenges "http" --domains "plex.ardelplanque.ovh" Saving debug log to /tmp/letsencrypt-log/letsencrypt.log An unexpected error occurred: requests.exceptions.SSLError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by SSLError(SSLError(1, '[SSL: TLSV1_UNRECOGNIZED_NAME] tlsv1 unrecognized name (_ssl.c:1056)'))) 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 ChildProcess.exithandler (node:child_process:402:12) 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) i've search for an answer but can't find anything related. certbot 2.5.0 thanks for reading ;-) **Nginx Proxy Manager Version** 2.10.4 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'host->proxy hosts->add proxy host' 2. complete the form to add a proxy host, and request a new SSL certificate (same happend when request a certificate before adding the proxy host). 4. See error **Expected behavior** adding the proxy host with a SSL certificate **Operating System** omv6 with docker and portainer, nginx PM in container

kerem

2026-02-26 07:34:50 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:51 +03:00

Author

Owner

@L-i-v-y commented on GitHub (Dec 25, 2023):

First of all, maybe you want to hide your registered email address in your report.

Coming back to your problem, that many probably have by now, according to a reddit post I found anything with creating an SSL certificate is caused by an outdated module used by the Docker container; the solution is to update that part from within the container.
See this reddit post (it's answers) for a possible fix:
https://www.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/

@L-i-v-y commented on GitHub (Dec 25, 2023): First of all, maybe you want to hide your registered email address in your report. Coming back to your problem, that many probably have by now, according to a reddit post I found anything with creating an SSL certificate is caused by an outdated module used by the Docker container; the solution is to update that part from within the container. See this reddit post (it's answers) for a possible fix: https://www.reddit.com/r/nginxproxymanager/comments/166fbka/certbot_renew_internal_error/

kerem commented

2026-02-26 07:34:51 +03:00

Author

Owner

@arndel90 commented on GitHub (Dec 26, 2023):

thanks for the answer,
i've found a workaround as a fresh installation of certbot (with snap) on the server didn't work neither :
i create the certificat on my synology nas and then import them in the NPM container.
as it is quite tedious, i'll look for the reddit post later this week and give a feedback if it worked or not ;-)

@arndel90 commented on GitHub (Dec 26, 2023): thanks for the answer, i've found a workaround as a fresh installation of certbot (with snap) on the server didn't work neither : i create the certificat on my synology nas and then import them in the NPM container. as it is quite tedious, i'll look for the reddit post later this week and give a feedback if it worked or not ;-)

kerem commented

2026-02-26 07:34:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 15, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Jul 15, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:34:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 6, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Aug 6, 2025): Issue was closed due to inactivity.

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#2282

No description provided.

Rows
Columns