mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #244] Renewal configuration file /etc/letsencrypt/renewal/npm-xx.conf is broken. Skipping. #216
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#216
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 @danmed on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/244
I'm running the latest docker image and i'm unable to renew any certificates..
Looking in the logs i'm seeing this :
`
[11/25/2019] [3:20:24 PM] [Express ] › ⚠ warning Command failed: /usr/bin/certbot renew -n --force-renewal --disable-hook-validation --cert-name npm-50
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 64, in _reconstitute
File "/usr/lib/python3/dist-packages/certbot/storage.py", line 460, in init
File "/usr/lib/python3/dist-packages/certbot/storage.py", line 519, in _check_symlinks
certbot.errors.CertStorageError: expected /etc/letsencrypt/live/npm-50/cert.pem to be a symlink
Renewal configuration file /etc/letsencrypt/renewal/npm-50.conf is broken. Skipping.
0 renew failure(s), 1 parse failure(s)`
It's happening to everything that's due to expire or has expired...
Any ideas how i can correct all this?
@chaptergy commented on GitHub (May 11, 2021):
It's been a while since this issue was opened. If you are still experiencing issues please let me know to reopen this issue.