starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #174] Add entity ids to tables in web interface #152

New issue

Closed

opened 2026-02-26 06:30:51 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 06:30:51 +03:00

Owner

Originally created by @Kranzy on GitHub (Jul 24, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/174

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Yes

Describe the bug

What version of Nginx Proxy Manager is reported on the login page? Nginx Proxy Manager v2.0.13

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:

Setup new proxy with new ssl cert
navigate folders to find ssl cert files

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

Running on docker on Synology Nas

Originally created by @Kranzy on GitHub (Jul 24, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/174 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? **Yes** - Are you sure you're not using someone else's docker image? **Yes** - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Yes** **Describe the bug** - What version of Nginx Proxy Manager is reported on the login page? **Nginx Proxy Manager v2.0.13** 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: 1. Setup new proxy with new ssl cert 2. navigate folders to find ssl cert files **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** - Running on docker on Synology Nas

kerem

2026-02-26 06:30:51 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@qy2009 commented on GitHub (Aug 1, 2019):

totally agree, if the folder can represent the proxy name, would be much easier!

@qy2009 commented on GitHub (Aug 1, 2019): totally agree, if the folder can represent the proxy name, would be much easier!

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@sm00tje commented on GitHub (Mar 14, 2020):

+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.

@sm00tje commented on GitHub (Mar 14, 2020): +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.

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@jc21 commented on GitHub (Mar 15, 2020):

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.

@jc21 commented on GitHub (Mar 15, 2020): > 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.

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@Kranzy commented on GitHub (Mar 23, 2020):

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?

@Kranzy commented on GitHub (Mar 23, 2020): 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?

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@jc21 commented on GitHub (Mar 23, 2020):

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 :)

@jc21 commented on GitHub (Mar 23, 2020): 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 :)

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@miguelwill commented on GitHub (Mar 24, 2020):

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

@miguelwill commented on GitHub (Mar 24, 2020): 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

kerem commented

2026-02-26 06:30:53 +03:00

Author

Owner

@jonas-resch commented on GitHub (Jun 4, 2020):

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"

@jonas-resch commented on GitHub (Jun 4, 2020): 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"

kerem commented

2026-02-26 06:30:54 +03:00

Author

Owner

@kennylajara commented on GitHub (May 16, 2021):

I think that a good option is to add a file named hosts.txt or something similar inside of the /letsencrypt/archive/npm-# where you can find a list of the hosts having this SSL.

But, in the mean time, how can I know what number is each SSL?

@kennylajara commented on GitHub (May 16, 2021): I think that a good option is to add a file named `hosts.txt` or something similar inside of the `/letsencrypt/archive/npm-#` where you can find a list of the hosts having this SSL. But, in the mean time, how can I know what number is each SSL?

kerem commented

2026-02-26 06:30:54 +03:00

Author

Owner

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

Unfortunately I can't think of any way this is currently possible. However I just opened a PR for this. But instead of txt files or a new table column I have opted to put this information inside the three-dot-menu on the right. (This is because this is only relevant for few people, so it shouldn't need a prominent place.)

In a while an automatically bult docker image should be available under jc21/nginx-proxy-manager:github-pr-1100, which you can use before it is merged and a new version has been published.

@chaptergy commented on GitHub (May 16, 2021): Unfortunately I can't think of any way this is currently possible. However I just opened a PR for this. But instead of txt files or a new table column I have opted to put this information inside the three-dot-menu on the right. (This is because this is only relevant for few people, so it shouldn't need a prominent place.) ![image](https://user-images.githubusercontent.com/26956711/118401962-415dac00-b657-11eb-9aff-680cd9a05a49.png) In a while an automatically bult docker image should be available under `jc21/nginx-proxy-manager:github-pr-1100`, which you can use before it is merged and a new version has been published.

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#152

No description provided.

Rows
Columns