[GH-ISSUE #2800] Internal Error: when creating a new ssl certificate UBUNTU v18/v20 & DEBIAN v11 #1924

Closed
opened 2026-02-26 07:33:17 +03:00 by kerem · 2 comments
Owner

Originally created by @KodekaTeamOfficial on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2800

Checklist

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

Describe the bug

Internal Error: when creating a new ssl certificate
so, i will add my subdomain and when will create ssl in SSL TAB with modal. i can't create and add new ssl.

in addition, on the SSL Certificate TAB.
I also can't create a new Certificate.
when I try to test 'Test Server Reachability' it always shows the response 'Communication with the API failed, is NPM running correctly?'

and when I force to save, I get an error log like this:

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name " npm-6" --agree-tos --authenticator webroot --email "email@gmail.com" --preferred-challenges "dns,http" --domains "sub.domain.my.id"
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.

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)

Nginx Proxy Manager Version

V2.10.2 -> before

Operating System

I am using UBUNTU v18 and v20 operating system.
and DEBIAN v11

Originally created by @KodekaTeamOfficial on GitHub (Apr 3, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2800 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No - Are you sure you're not using someone else's docker image? - No - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> Internal Error: when creating a new ssl certificate so, i will add my subdomain and when will create ssl in SSL TAB with modal. i can't create and add new ssl. in addition, on the SSL Certificate TAB. I also can't create a new Certificate. when I try to test 'Test Server Reachability' it always shows the response 'Communication with the API failed, is NPM running correctly?' and when I force to save, I get an error log like this: Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name " npm-6" --agree-tos --authenticator webroot --email "email@gmail.com" --preferred-challenges "dns,http" --domains "sub.domain.my.id" 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. 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) **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> V2.10.2 -> before <!--**To Reproduce**--> <!--Steps to reproduce the behavior: --> <!--1. Go to '...' --> <!--2. Click on '....' --> <!--3. Scroll down to '....' --> <!--4. See error --> <!--**Expected behavior** --> <!-- A clear and concise description of what you expected to happen. --> <!--**Screenshots** --> <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> I am using UBUNTU v18 and v20 operating system. and DEBIAN v11 <!--**Additional context** --> <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 07:33:17 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@andzejsp commented on GitHub (Apr 7, 2023):

smells awfully like #2713

<!-- gh-comment-id:1500052953 --> @andzejsp commented on GitHub (Apr 7, 2023): smells awfully like #2713
Author
Owner

@KodekaTeamOfficial commented on GitHub (Apr 8, 2023):

updates!
after I searched, it turns out this is not a bug.
Turns out I haven't pointed the public IP to Cloudflare DNS correctly.
And now, I've managed to do well.

Thank you, and I permission to close this thread

<!-- gh-comment-id:1500827925 --> @KodekaTeamOfficial commented on GitHub (Apr 8, 2023): **updates!** after I searched, it turns out this is not a bug. Turns out I haven't pointed the public IP to Cloudflare DNS correctly. And now, I've managed to do well. Thank you, and I permission to close this thread
Sign in to join this conversation.
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#1924
No description provided.