[GH-ISSUE #404] Allow user to download SSL certificate #341

Closed
opened 2026-02-26 06:32:26 +03:00 by kerem · 3 comments
Owner

Originally created by @theraw on GitHub (May 10, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/404

Hello,

I would like to be allowed to download ssl/cert/key from dashboard.

also it would be nice if you replace the number count of vconf file and ssl folder from number to domain/subdomain name!

ex when i create first proxy_host you create nginx vhost as 1.conf it will be better if domainname.com.conf this way i more easy to find out where is domain config file or ssl folder!

Originally created by @theraw on GitHub (May 10, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/404 Hello, I would like to be allowed to download ssl/cert/key from dashboard. also it would be nice if you replace the number count of vconf file and ssl folder from number to domain/subdomain name! ex when i create first proxy_host you create nginx vhost as `1.conf` it will be better if `domainname.com.conf` this way i more easy to find out where is domain config file or ssl folder!
kerem 2026-02-26 06:32:26 +03:00
Author
Owner

@gkroonder commented on GitHub (May 31, 2021):

There are some good questions in #683; I personally would like to see certificate-foldernames in /etc/letsencrypt/live/ to use the certificate name as show in the GUI. I.e. "domain.ext".

That IMHO would make it much easier to re-use the certs from NPM in other docker containers, something that will come up again and again...

I've looked at the code and I see it is not a simple change.
But maybe it is possible to make symlinks the active certs to a 'static' [cert displayname] location?
I.e. /certificates/mydomain.ext (wildcard or tld) or /certificates/host.mydomain.ext (for hostname certs).
It could be a separate dir && docker-volume i.e. /certificates, or a dir under the data or letsencrypt volumes.

I wish I was a programmer and could help a bit, but alas, I can just (barely) get the gist of the code.

Thanks for listening to my input.

Best regards,

George

<!-- gh-comment-id:851554478 --> @gkroonder commented on GitHub (May 31, 2021): There are some good questions in #683; I personally would like to see certificate-foldernames in /etc/letsencrypt/live/ to use the certificate name as show in the GUI. I.e. "domain.ext". That IMHO would make it much easier to re-use the certs from NPM in other docker containers, something that will come up again and again... I've looked at the code and I see it is not a simple change. But maybe it is possible to make symlinks the active certs to a 'static' [cert displayname] location? I.e. /certificates/mydomain.ext (wildcard or tld) or /certificates/host.mydomain.ext (for hostname certs). It could be a separate dir && docker-volume i.e. /certificates, or a dir under the data or letsencrypt volumes. I wish I was a programmer and could help a bit, but alas, I can just (barely) get the gist of the code. Thanks for listening to my input. Best regards, George
Author
Owner

@chaptergy commented on GitHub (May 31, 2021):

For now https://github.com/jc21/nginx-proxy-manager/pull/1100 has been implemented to make it generally possible to know which certificate is which.

<!-- gh-comment-id:851611870 --> @chaptergy commented on GitHub (May 31, 2021): For now https://github.com/jc21/nginx-proxy-manager/pull/1100 has been implemented to make it generally possible to know which certificate is which.
Author
Owner

@chaptergy commented on GitHub (Nov 18, 2021):

Added via https://github.com/jc21/nginx-proxy-manager/pull/1343

<!-- gh-comment-id:972967257 --> @chaptergy commented on GitHub (Nov 18, 2021): Added via https://github.com/jc21/nginx-proxy-manager/pull/1343
Sign in to join this conversation.
No milestone
No project
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#341
No description provided.