mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #1618] Feature: Allow update custom existing SSL Certificate #1217
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#1217
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 @rmartcas on GitHub (Nov 30, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1618
Is your feature request related to a problem? Please describe.
Every 3 months i need to manually update all my letsencript certificates for all my domains/subdomains. After certbot renew i need to manually create a new SSL Certificate entry with the new certificates for the next 3 months and update one by one all of my proxy hosts with the new certificate entry previosly created.
This is a tedious task because i have a lot of proxy hosts entries.
Describe the solution you'd like
It would be very nice to have an option to re-upload the private key and certificate for an existing SSL Certificate like this:
Describe alternatives you've considered
Additional context
I hope this will be a good feature :)
Regards.
@BobWs commented on GitHub (Dec 21, 2021):
+1 This would be a great enhancement!
At the moment I have to change every 60+ days the Certs of 30 containers manually when my LE Cert is renewed.
I use docker Linuxserver/swag to renew my wildcard LE Cert and that has to be imported every-time on a renewal for every container.
@spcqike commented on GitHub (May 3, 2022):
+1
as a "workaround" i managed to update the cert files within the container itself and restarted nginx. this works for my sites. only disadvantage: NPM doesn't (and can't) know the new expiration date and shows it as overdue. but: you don't have to update all your reverse proxys and services.
@Tuphal commented on GitHub (Aug 1, 2022):
I have the same issue, when my wildcard cert is expiring.
I don't want to manually edit all my domain entries.
A "Renew Custom Cert" would be a pretty nice feature
@BobWs commented on GitHub (Aug 3, 2022):
Would you like to share your workaround?
@spcqike commented on GitHub (Aug 3, 2022):
@BobWs as i wrote, i updated the cert files within the container. as the filesystem is a mounted volume (folder?) to keep everything persistent, this was quite easy.
i restarted the container and it started again, now using the new certificate.
as i mentioned: only the disadvantage is, that it still shows the old expiration date in the UI
i think this has to do with the fact that the data is stored in a database and it is only updated when going through the UI.
@SSpt1978 commented on GitHub (Apr 1, 2023):
+1 This would be a great enhancement!
I have more than 100 Hosts.
For now the solution of spcqike works.
@BenjaminBini commented on GitHub (Apr 18, 2023):
I confirm that this would be of great help. I have a wildcard certificate (on a private network with no public DNS, so no Let's Encrypt possible) and I have 100+ hosts to update, it is a slow process! Thank you :)
@editor37 commented on GitHub (Aug 13, 2023):
Same routine every 3 months. Nothing new ?
@karpana commented on GitHub (Sep 4, 2023):
i know this is a thread necro, but I'm curious if any progress has been made on this front.
I use a wildcard letsencrypt certificate, using a domain registrar that doesn't support automation, in order to obfuscate my subdomains. It is quite frustrating having to "rebuild" all the certificate configurations for all my subdomains byu hand.
I am going to explore the solution that @spcqike has provided. but in the meantime, I'd like to give my +1 to this enhancement request.
@BobWs commented on GitHub (Sep 4, 2023):
The @spcqike approach works for me, so I say give it try.
@MarlBurroW commented on GitHub (Sep 13, 2023):
The current mounting workaround is OK... but it would be beneficial to have a feature in the UI that allows for updating an existing certificate by re-uploading new certificate files without removing the existing one (associations with hosts are conserved). This enhancement would empower the less technical members of my team to update certificates independently, especially considering we have 50 hosts using the same wildcard to update individually.
Big +1
@BobWs commented on GitHub (Sep 13, 2023):
This feature request was posted 2 years ago, so don't get your hopes up for it to change within a reasonable period!
I guess it's is a very low priority feature to implement for the developers.
@spcqike commented on GitHub (Sep 13, 2023):
as its open source, everyone who can code can do so and open a pull request.
in this case i would think about a central storage location, where all hosts read the same file. or at least a script that keeps the certificate updated on every host automatically. updating 50 hosts in a webUI manually is .... not practical.
@Rdiger-36 commented on GitHub (Feb 22, 2024):
I've got the same Problem. I solved it with the workaround from @spcqike.
I have also found a workaround for the problem with the expiration date. To do this, simply change the expires_on entry from your certificate in the table certificates in the NPM database. I use MariaDB and have set the expiration date to that of the new certificate. You can also set it to any other date you want.
You can do this either via the console or via phpMyAdmin, which is much easier.
@naziris commented on GitHub (Mar 2, 2024):
Based on @spcqike answer:
After you update the CRT file. Add a dummy domain with the new CRT.
Then download locally the database.sqlite file from your docker container.
Open it on your machine with a sqlite editor
Go to certificate table and view the rows
Edit the dummy row you added before and note down the content of modified_on, expires_on and meta.
Now edit the actual row of the domain you would like to modify, and copy paste the data we extracted on previous step
Delete the dummy row and save the changes
Copy the new/modified database.sqlite file back to the container and restart it
Here's your edit "button" :)
@Commifreak commented on GitHub (May 22, 2024):
+1 for a replace feature to select either all new or only the new cert (while keeping the key). Would make custom cert updates easier.
An upload/edit via textarea (input base64) would be nice as well.
@itguy327 commented on GitHub (Jun 12, 2024):
+1
@marvin78 commented on GitHub (Jul 18, 2024):
+1
@adrian-moll commented on GitHub (Aug 9, 2024):
+1
@krilzov commented on GitHub (Aug 22, 2024):
+1
@alexbiaolol commented on GitHub (Aug 24, 2024):
A workround works form me:
nginx_manager_1 is your container name of nginx-proxy-manager.
docker volumes: /root/data:/data
Using the acme.sh script to automatically install the certs file:
acme.sh xxxxxxxxxx --key-file /root/data/custom_ssl/npm-2/privkey.pem --fullchain-file /root/data/custom_ssl/npm-2/fullchain.pem --reloadcmd "docker exec nginx_manager_1 nginx -s reload"
or you can manually do it with command everything 3 month:
docker exec nginx_manager_1 nginx -s reload;
@rumansaleem commented on GitHub (Mar 9, 2025):
I have also faced the same issue, and I managed to come up with a solution PR #4425.
@ducnt102 commented on GitHub (Mar 11, 2025):
This is my solution,
Connect to SQLite3 and update proxy_host to use the new host.
Find the ID of the new certificate.
`sqlite3 data/database.sqlite
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
sqlite> SELECT id,nice_name,domain_names FROM certificate;
9 is the new certificate ID.
2 is the old certificate ID.
UPDATE proxy_host SET certificate_id = 9 WHERE certificate_id = 2;
restart service
`
@Buronn commented on GitHub (Apr 22, 2025):
Same issue here, i need a solution, i have a custom container that renovates my custom certificates but i cant put them into npm automatically
@derRichter commented on GitHub (Sep 23, 2025):
+1 here
but ok, i set a custom-Cert with the expire-Date to 2999 and done...
Then i can upload every new certifiacte with "certify certificate Manager" to the real Webserver and to the NPM and restart both
@Legendary4226 commented on GitHub (Sep 25, 2025):
+1
I have miss configured something in the domains list and now I need to recreate a token from Cloudflare for the DNS challenge
@Riffer commented on GitHub (Jan 6, 2026):
+1 - it should be possible for NPM to retrieve the expire date directly from the cert.
@ts2580 commented on GitHub (Feb 11, 2026):
+1