NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Internal Error when request new ssl certificate

Open
#3,291 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

npminternal

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?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

i try to create new reverse proxy and when i try create a new ssl certificate it's keep give me internal error and when i try to add cerificates by using Add SSL cerificates function this error come out :

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

port 80 is already open, and i do a portforward too for this port (80,443,81)

i try to create new domain and try to generate new SSL certificate but everything seems not working, it's working fine in previous version i don't know what wrong with this version. And i also try to untick force SSL and HTTP/2 support disable and still receive the error.

i try to uninstall NPM and reinstall it again but the result is same.

i also try to Test Server Reachability and i receive "Communication with the API failed, is NPM running correctly?"

please help me.

this is my docker-compose.yml

port 80 and 443 is already in use.

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '8484:80'
      - '81:81'
      - '4443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied docker-compose.yml and the Certbot command shown in the error, then inspect /tmp/letsencrypt-log/letsencrypt.log and test server reachability. Compare the published ports with the ports required for HTTP and HTTPS validation; done means the API check succeeds and a new SSL certificate is issued.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
infrastructure, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.