Checklist
jc21/nginx-proxy-manager:latest docker image?Describe the bug
When creating a proxy with new SSL Cert it seems to be placing the cert files in the /letsencrypt/archive/npm-3 folder instead of the /letsencrypt/live/npm-3 folder. Also is there any way to know which npm- folder belongs to which proxy?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected to find the files in this location /letsencrypt/live/npm-3 but instead of npm- it would be the proxy name or another identifiable name
Operating System
totally agree, if the folder can represent the proxy name, would be much easier!
+1 using NGINX proxy manager for homeassistant, so i need to know the location of the certs for using the cert in for other plugins for example. also for using the cert on other machine for tunneling ssl trough the proxy.
totally agree, if the folder can represent the proxy name, would be much easier!
The problem here is that a cert can have multiple domain names, even wildcards. In addition, a cert can be applied to more than 1 proxy host, redirection host etc. So it made sense to keep it numerical as far as certbot is concerned.
As for the archive vs live folders, this is a certbot thing that I don't have control over. I believe the live folder has symlinks to the archive one.
that makes sense in terms of multiple names per cert etc. Is there a way in your front end to note the corrosponding folder for that particular cert, at least that way we know which one to use?
Yeah so this would as easy as adding an ID column to all the objects. I myself have been wanting to do it when I'm debugging stuff :)
that's right, in other hosting panels (like ispconfig) the site ID appears in the first column, allowing you to know in the list itself which ID corresponds to the site you need
for the certificates you could have the same solution, so you could have the ID at hand in case of automating the extraction or copy of the certificate
You could also use the timestamp to check which certificate is stored in which folder. Just use the creation date and expiration time displayed in the web ui under "SSL certificates"
Most helpful comment
totally agree, if the folder can represent the proxy name, would be much easier!