starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2321] Custom Certificate Import not working Cant enter local path? #1645

New issue

Closed

opened 2026-02-26 07:31:53 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 07:31:53 +03:00

Owner

Originally created by @1liminal1 on GitHub (Oct 13, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2321

Have you searched for similar issues (both open and closed)?
- Yes, seems to be a workaround

Describe the bug
When trying to specify the path local NPM docker instance path to certificates I just get a dialog box keep popping up with access to the local computer.

Nginx Proxy Manager Version
v2.9.18

To Reproduce
Steps to reproduce the behavior:

Add SSL certs
Custom
Try to enter Certificate & Key location

Expected behavior
Am able to enter the local NPM docker instance path to my the certificates already on the NPM server

Screenshots

Operating System
Debian

Additional context
People have certs that they want to use and not being able to automate that is a PIA

Originally created by @1liminal1 on GitHub (Oct 13, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2321 - Have you searched for similar issues (both open and closed)? - Yes, seems to be a workaround **Describe the bug** When trying to specify the path local NPM docker instance path to certificates I just get a dialog box keep popping up with access to the local computer. **Nginx Proxy Manager Version** v2.9.18 **To Reproduce** Steps to reproduce the behavior: 1. Add SSL certs 2. Custom 3. Try to enter Certificate & Key location **Expected behavior** Am able to enter the local NPM docker instance path to my the certificates already on the NPM server **Screenshots** ![image](https://user-images.githubusercontent.com/10505942/195556560-26e4e99c-a72b-4940-b6ae-0fc66e9dc90b.png) **Operating System** Debian **Additional context** People have certs that they want to use and not being able to automate that is a PIA

kerem

2026-02-26 07:31:53 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@the1ts commented on GitHub (Oct 13, 2022):

@1liminal1 When you say local path, do you mean local to the npm server or local to the browser? I'm not sure because you use local twice in the report.
If you mean local to the npm server, then the correct method would be to use docker volumes to put the cert into the correct location within the npm docker container.

@the1ts commented on GitHub (Oct 13, 2022): @1liminal1 When you say local path, do you mean local to the npm server or local to the browser? I'm not sure because you use local twice in the report. If you mean local to the npm server, then the correct method would be to use docker volumes to put the cert into the correct location within the npm docker container.

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@1liminal1 commented on GitHub (Oct 13, 2022):

Hi there,

Thanks for that. Yes, local server path. I have the certs already on the docker instance ready to go. But I cant specify a path.

If there is a path where the certs will be automatically loaded, can you advise what that is. Is there doco for it?

@1liminal1 commented on GitHub (Oct 13, 2022): Hi there, Thanks for that. Yes, local server path. I have the certs already on the docker instance ready to go. But I cant specify a path. If there is a path where the certs will be automatically loaded, can you advise what that is. Is there doco for it?

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@the1ts commented on GitHub (Oct 14, 2022):

custom ssl certs are held in the data volume under custom_ssl/npm-number, I suggest you create a cert with the correct names in the UI. Then the npm-number directory will be made, then link in your cert and key.

@the1ts commented on GitHub (Oct 14, 2022): custom ssl certs are held in the data volume under custom_ssl/npm-number, I suggest you create a cert with the correct names in the UI. Then the npm-number directory will be made, then link in your cert and key.

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@1liminal1 commented on GitHub (Oct 15, 2022):

Ok... So what your saying is;

Add the cert though the UI the first time and make a note of what the directory name was created under the "custom_ssl" directory. For me using Portainer its;

/portainer/Files/AppData/Config/Nginx-Proxy/data/custom_ssl/npm-1/

Then set up an export, or whatever sync method you want, to export the certs to that folder after renewal and NPM with pick up the new certs automatically.

Is that right?

@1liminal1 commented on GitHub (Oct 15, 2022): Ok... So what your saying is; Add the cert though the UI the first time and make a note of what the directory name was created under the "custom_ssl" directory. For me using Portainer its; /portainer/Files/AppData/Config/Nginx-Proxy/data/custom_ssl/npm-1/ Then set up an export, or whatever sync method you want, to export the certs to that folder after renewal and NPM with pick up the new certs automatically. Is that right?

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@the1ts commented on GitHub (Oct 15, 2022):

yes, as long as your certs end up in the custom_ssl/npm-number and are readable by nginx it will work. You will have to restart NPM when they change, but that is true of apache/nginx or any SSL protected service.
In short NPM does not store the cert in the DB, just pointers to the location they are on the file system which is why this works.

@the1ts commented on GitHub (Oct 15, 2022): yes, as long as your certs end up in the custom_ssl/npm-number and are readable by nginx it will work. You will have to restart NPM when they change, but that is true of apache/nginx or any SSL protected service. In short NPM does not store the cert in the DB, just pointers to the location they are on the file system which is why this works.

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@the1ts commented on GitHub (Oct 16, 2022):

Hoping we can close this off since docker images cannot get access to host files not presented as volumes so it doesn't make sense as a development request. So the only sensible thing is to present the cert and key as docker volumes as suggested.

@the1ts commented on GitHub (Oct 16, 2022): Hoping we can close this off since docker images cannot get access to host files not presented as volumes so it doesn't make sense as a development request. So the only sensible thing is to present the cert and key as docker volumes as suggested.

kerem commented

2026-02-26 07:31:54 +03:00

Author

Owner

@1liminal1 commented on GitHub (Oct 16, 2022):

Yes thanks, I wanted to convert this to a feature request, but seems its easier to just open one.

Thanks for your help, I do appreciate it :)

@1liminal1 commented on GitHub (Oct 16, 2022): Yes thanks, I wanted to convert this to a feature request, but seems its easier to just open one. Thanks for your help, I do appreciate it :)

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

No description provided.

Rows
Columns