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 #1901] NPM to enable https access to docker conainers inside my home network only using letsEncrypt certificates #1383

New issue

Closed

opened 2026-02-26 07:30:45 +03:00 by kerem · 10 comments

kerem commented

2026-02-26 07:30:45 +03:00

Owner

Originally created by @queen4me on GitHub (Mar 1, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1901

I don't want to expose my home network directly to the internet but connect via VPN when I'm not at home or access a Docker container via NPM and https from a client in my home network.
At the moment I'm completely stuck understanding how to access a docker container from inside my network using NPM for https.

I'd like to use the integrated and existing automatism for upgrading letsEncrypt SSL-certificates directly from NPM and with my internet connection (outgoing) but instead of accessing the docker container from the internet using the domain name and NPM I'd like to configure NPM for internal access only.

I've withdrawn every alternative like using pi-hole and local DNS records because this won't help me at all.

Hopefully somebody reads this post and shows me a solution with the existing NPM and the "correct" usage/configuration for my use case.

Thanks a lot for helping and by the way the creators and maintainers of NPM did a great job!!!

Originally created by @queen4me on GitHub (Mar 1, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1901 I don't want to expose my home network directly to the internet but connect via VPN when I'm not at home or access a Docker container via NPM and https from a client in my home network. At the moment I'm completely stuck understanding how to access a docker container from inside my network using NPM for https. I'd like to use the integrated and existing automatism for upgrading letsEncrypt SSL-certificates directly from NPM and with my internet connection (outgoing) but instead of accessing the docker container from the internet using the domain name and NPM I'd like to configure NPM for internal access only. I've withdrawn every alternative like using pi-hole and local DNS records because this won't help me at all. Hopefully somebody reads this post and shows me a solution with the existing NPM and the "correct" usage/configuration for my use case. Thanks a lot for helping and by the way the creators and maintainers of NPM did a great job!!!

kerem

2026-02-26 07:30:45 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@LePresidente commented on GitHub (Mar 3, 2022):

You can set up a access-list with your local IP range in the allow and the default rule deny. then add that rule to your acess list in each proxy host.

@LePresidente commented on GitHub (Mar 3, 2022): You can set up a access-list with your local IP range in the allow and the default rule deny. then add that rule to your acess list in each proxy host.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@ssrahul96 commented on GitHub (Mar 3, 2022):

@queen4me may i know why pi-hole does not work for you case?, The SSL certificates are issues for domain names not ip. in that case you definetly need a dns record for the same, (local or public depending upon ur needs)

@ssrahul96 commented on GitHub (Mar 3, 2022): @queen4me may i know why pi-hole does not work for you case?, The SSL certificates are issues for domain names not ip. in that case you definetly need a dns record for the same, (local or public depending upon ur needs)

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@queen4me commented on GitHub (Mar 4, 2022):

Thank you folks.

@LePresidente
You mean I can keep the DNS "untouched" and access is only possible from my internal network because internal devices have an internal IP.
Setting up an access-list with allow 192.168.178.0/24 and adding this ACL to the proxy-host.

@ssrahul96
I'm struggeling with my PiHole because local DNS records like container1.mydomain.de 192.168.178.6 and using https://container1.mydomain.de in my browser have not been successfull at all.

@queen4me commented on GitHub (Mar 4, 2022): Thank you folks. @LePresidente You mean I can keep the DNS "untouched" and access is only possible from my internal network because internal devices have an internal IP. Setting up an access-list with allow 192.168.178.0/24 and adding this ACL to the proxy-host. @ssrahul96 I'm struggeling with my PiHole because local DNS records like container1.mydomain.de 192.168.178.6 and using https://container1.mydomain.de in my browser have not been successfull at all.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@ssrahul96 commented on GitHub (Mar 5, 2022):

Thank you folks.

@LePresidente You mean I can keep the DNS "untouched" and access is only possible from my internal network because internal devices have an internal IP. Setting up an access-list with allow 192.168.178.0/24 and adding this ACL to the proxy-host.

@ssrahul96 I'm struggeling with my PiHole because local DNS records like container1.mydomain.de 192.168.178.6 and using https://container1.mydomain.de in my browser have not been successfull at all.

could you do a nslookup and ensure that its pointing to your pihole dns, i am using adguard, i think both of these does the same job.

@ssrahul96 commented on GitHub (Mar 5, 2022): > Thank you folks. > > @LePresidente You mean I can keep the DNS "untouched" and access is only possible from my internal network because internal devices have an internal IP. Setting up an access-list with allow 192.168.178.0/24 and adding this ACL to the proxy-host. > > @ssrahul96 I'm struggeling with my PiHole because local DNS records like container1.mydomain.de 192.168.178.6 and using https://container1.mydomain.de in my browser have not been successfull at all. could you do a nslookup and ensure that its pointing to your pihole dns, i am using adguard, i think both of these does the same job.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@queen4me commented on GitHub (Mar 5, 2022):

@LePresidente
I now re-configured everything and my container is now accesible usind DDNS but if I enable the access-list I get an error 403. After disabling the access list everything works but I think I'm accessing over internet instead of my home network directly.

@queen4me commented on GitHub (Mar 5, 2022): @LePresidente I now re-configured everything and my container is now accesible usind DDNS but if I enable the access-list I get an error 403. After disabling the access list everything works but I think I'm accessing over internet instead of my home network directly.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@ssrahul96 commented on GitHub (Mar 5, 2022):

access list

could you share your access list config, vpn subnet and npm subnets?

@ssrahul96 commented on GitHub (Mar 5, 2022): > access list could you share your access list config, vpn subnet and npm subnets?

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@queen4me commented on GitHub (Mar 8, 2022):

@ssrahul96

I use PiHole as DNS and Adguard on my client as well. Could this be a/the problem?
nlsookup with my actual setup:

`nslookup container.mydomain.ddnss.de
Server: Unknown
Address:

Not authorised response:
Name: mydomain.ddnss.de
Address:
Aliases: container.mydomain.ddnss.de`

Like I've written without any PiHole local DNS settings just DynDNS with ddnss.de and two portforwarding on my internetrouter for port 80 and 443 to my NPM-Container IP.

@queen4me commented on GitHub (Mar 8, 2022): @ssrahul96 I use PiHole as DNS and Adguard on my client as well. Could this be a/the problem? nlsookup with my actual setup: `nslookup container.mydomain.ddnss.de Server: Unknown Address: <IP v6 Address> Not authorised response: Name: mydomain.ddnss.de Address: <IPv4 from my internet router> Aliases: container.mydomain.ddnss.de` Like I've written without any PiHole local DNS settings just DynDNS with ddnss.de and two portforwarding on my internetrouter for port 80 and 443 to my NPM-Container IP.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@queen4me commented on GitHub (Mar 8, 2022):

Problem is solved. My Fritzbox has a problem with DHCP clients and setting the IP of the PiHole.
After setting the DNS manually to the PiHole IP everything is fine now.

Thanks a lot for helping folks.

@queen4me commented on GitHub (Mar 8, 2022): Problem is solved. My Fritzbox has a problem with DHCP clients and setting the IP of the PiHole. After setting the DNS manually to the PiHole IP everything is fine now. Thanks a lot for helping folks.

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 22, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 22, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:30:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 7, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 7, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:30:36 +03:00

[PR #1383] [CLOSED] FIX: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory #3426

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

No description provided.

Rows
Columns