starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #3251] Keeps trying to renew deleted certificates #2194

New issue
Open
opened 2026-02-26 07:34:27 +03:00 by kerem · 5 comments
kerem commented 2026-02-26 07:34:27 +03:00
Owner
Copy link

Originally created by @Waldorf3 on GitHub (Oct 10, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3251

After changing from using domain based certificates to DNS based challenge, and now having just one wild-card cert for all my domains, I deleted all the old per-domain certificates (through the GUI, one by one).

Container logs now show it still tries (and fails) to renew all the deleted certificates. Obviously something goes wrong when certificates are deleted, and the database isn't updated correctly.

npm  | Failed to renew certificate npm-11 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-12 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-13 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-14 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-2 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-3 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-4 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-5 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-8 with error: Some challenges have failed.
npm  | Failed to renew certificate npm-9 with error: Some challenges have failed.
npm  | All renewals failed. The following certificates could not be renewed:
npm  |   /etc/letsencrypt/live/npm-11/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-12/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-13/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-14/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-2/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-3/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-4/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-8/fullchain.pem (failure)
npm  |   /etc/letsencrypt/live/npm-9/fullchain.pem (failure)
npm  | 10 renew failure(s), 0 parse failure(s)

v2.10.4 © 2023 jc21.com. Theme by Tabler

Originally created by @Waldorf3 on GitHub (Oct 10, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3251 After changing from using domain based certificates to DNS based challenge, and now having just one wild-card cert for all my domains, I deleted all the old per-domain certificates (through the GUI, one by one). Container logs now show it still tries (and fails) to renew all the deleted certificates. Obviously something goes wrong when certificates are deleted, and the database isn't updated correctly. ``` npm | Failed to renew certificate npm-11 with error: Some challenges have failed. npm | Failed to renew certificate npm-12 with error: Some challenges have failed. npm | Failed to renew certificate npm-13 with error: Some challenges have failed. npm | Failed to renew certificate npm-14 with error: Some challenges have failed. npm | Failed to renew certificate npm-2 with error: Some challenges have failed. npm | Failed to renew certificate npm-3 with error: Some challenges have failed. npm | Failed to renew certificate npm-4 with error: Some challenges have failed. npm | Failed to renew certificate npm-5 with error: Some challenges have failed. npm | Failed to renew certificate npm-8 with error: Some challenges have failed. npm | Failed to renew certificate npm-9 with error: Some challenges have failed. npm | All renewals failed. The following certificates could not be renewed: npm | /etc/letsencrypt/live/npm-11/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-12/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-13/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-14/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-2/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-3/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-4/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-5/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-8/fullchain.pem (failure) npm | /etc/letsencrypt/live/npm-9/fullchain.pem (failure) npm | 10 renew failure(s), 0 parse failure(s) ``` v2.10.4 © 2023 [jc21.com](https://jc21.com/?utm_source=nginx-proxy-manager). Theme by [Tabler](https://tabler.github.io/?utm_source=nginx-proxy-manager)
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 30, 2024):

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

<!-- gh-comment-id:2138528373 --> @github-actions[bot] commented on GitHub (May 30, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@nik2208 commented on GitHub (Aug 27, 2024):

needed to set as deleted all table 'certificate' rows referring to deleted domain names. that solved the issue

<!-- gh-comment-id:2311464749 --> @nik2208 commented on GitHub (Aug 27, 2024): needed to set as deleted all table 'certificate' rows referring to deleted domain names. that solved the issue
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jun 1, 2025):

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

<!-- gh-comment-id:2926293976 --> @github-actions[bot] commented on GitHub (Jun 1, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jan 22, 2026):

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

<!-- gh-comment-id:3782127999 --> @github-actions[bot] commented on GitHub (Jan 22, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@Waldorf3 commented on GitHub (Jan 23, 2026):

needed to set as deleted all table 'certificate' rows referring to deleted domain names. that solved the issue

still unresolved. Would be nice if someone would fix it instead of just repeatedly closing it

<!-- gh-comment-id:3788881855 --> @Waldorf3 commented on GitHub (Jan 23, 2026): > needed to set as deleted all table 'certificate' rows referring to deleted domain names. that solved the issue still unresolved. Would be nice if someone would fix it instead of just repeatedly closing it
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2194
No description provided.