mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2885] NPM docker wont start. #1976
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1976
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @blownco on GitHub (May 4, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2885
seems to be in some sort of restart loop? anyone else have this?
[supervisor ] service 'nginx' exited (with status 1).
[supervisor ] restarting service 'nginx'.
[supervisor ] starting service 'nginx'...
[nginx ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:0200100D:system library:fopen:Permission denied:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D002:BIO routines:BIO_new_file:system lib)
@blownco commented on GitHub (May 6, 2023):
a full reinstall fixed the issue.
@BHeshka commented on GitHub (Jun 11, 2023):
I ran into this issue after deleting an SSL certificate that was still being used by proxy hosts.
@jqtmviyu commented on GitHub (Oct 1, 2023):
create files like
letsencrypt/live/npm-13/fullchain.pemletsencrypt/live/npm-13/privkey.pem, resolve it.