Skip to content

[emerg] cannot load certificate #3969

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Bluscream opened this issue Aug 31, 2024 · 3 comments
Open

[emerg] cannot load certificate #3969

Bluscream opened this issue Aug 31, 2024 · 3 comments
Labels
bug stale

Comments

@Bluscream
Copy link

Checklist

  • 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
can be seen in the log below

Nginx Proxy Manager Version

2.11.3

To Reproduce
Steps to reproduce the behavior:

  1. Go to certs
  2. Click on new cert
  3. use cloudflare
  4. click ok

Expected behavior
new cert

Screenshots

CommandError: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-16/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-16/fullchain.pem, r) error:10000080:BIO routines::no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

    at /app/lib/utils.js:16:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket. (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Pipe. (node:net:338:12)

Operating System
raspbian latest

Additional context
@Bluscream Bluscream added the bug label Aug 31, 2024
@totorus
Copy link

totorus commented Sep 21, 2024

Same bug, same errors.

@biscottiman
Copy link

biscottiman commented Sep 23, 2024 •
edited
Loading

Had the same issue. Turns out this is caused by proxy hosts I had which were still trying to load the SSL which was deleted. Was able to resolve it with:

  1. entered the container for nginx-app-1
    docker exec -it nginx-app-1 bash
  2. recreated the folder in /etc/letsencrypt/live that was missing (in my case /npm3)
    mkdir /etc/letsencrypt/live/npm-3
  3. copied files from another live SSL
    cp /etc/letsencrypt/live/npm-5/fullchain.pem /etc/letsencrypt/live/npm-3/fullchain.pem
    cp /etc/letsencrypt/live/npm-5/privkey.pem /etc/letsencrypt/live/npm-3/privkey.pem
  4. Exit container
    exit
  5. Restart your container
    docker compose restart
    (if using docker compose and currently in the directory containing your docker compose file)

After that I was able to access the webui and remove the proxy hosts that were causing the issue. Remember to go back and clean up the files you created previously.

@github-actions GitHub Actions
Copy link

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

@github-actions github-actions bot added the stale label May 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Bluscream @biscottiman @totorus
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy