mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3806] Update custom SSL cert expiration date when SSL files change in the cert directory #2507
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#2507
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 @begunfx on GitHub (Jun 13, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3806
Is your feature request related to a problem? Please describe.
Currently I'm generating SSL certs outside of NPM. I'm able to use a script to copy the certs into the custom cert folder inside of NPM on a cron/schedule. The issue is after the custom SSL cert is initially created, if I update the SSL files in the cert folder the date within the UI does not update.
Describe the solution you'd like
The simplest solution I can think of is to watch the cert folder for changes and if it is updated then write a new date from the SSL cert into the database and update the date in the UI.
Describe alternatives you've considered
I can't think of any other alternatives other than manually creating a new custom cert everytime it's about to expire - not a reasonable solution by any means.
Additional context
My SSL cert is by ZeroSSL.
@ManaZero37 commented on GitHub (Jun 24, 2024):
I'm also experiencing the same issue. I'm updating my certificates regularly using ACME, but it seems that the updated certificate files are not working.
@moseslsy commented on GitHub (Jul 5, 2024):
Same issue here. I have to use a workaround by including the cert locations in the server.conf and selecting no SSL in the GUI
@Yzzzed commented on GitHub (Jul 9, 2024):
Same problem.
@cybaijie commented on GitHub (Jul 25, 2024):
I also need this function
@github-actions[bot] commented on GitHub (Feb 16, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@begunfx commented on GitHub (Feb 17, 2025):
Please keep this issue open!
@DarkIntaqt commented on GitHub (Jun 2, 2025):
Or some sort of cronjob that checks regularly / on startup. Additionally (or at least) a button to refresh a custom SSL certificate on the dashboard would also do the job (somehow).
@zackeray commented on GitHub (Nov 12, 2025):
Same problem.