[GH-ISSUE #1206] Pihole with nginx-proxy-manager #983

New issue

Open

opened 2026-02-26 06:35:18 +03:00 by kerem · 13 comments

kerem commented 2026-02-26 06:35:18 +03:00

Owner

Copy link

Originally created by @samad20 on GitHub (Jun 26, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1206

Since port 80 and 443 is reserved for Nginx, how can i install pi hole on docker?

Originally created by @samad20 on GitHub (Jun 26, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1206 Since port 80 and 443 is reserved for Nginx, how can i install pi hole on docker?

kerem added the

enhancement

stale

labels 2026-02-26 06:35:18 +03:00

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@bpycinski commented on GitHub (Jun 28, 2021):

There is no problem at all. Just map the port to anything other, e.g. 8080 See my docker-compose, it works very well:

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
    - "8080:80/tcp"
    - "53:53/tcp"
    - "53:53/udp"
    - "67:67/udp"
    environment:
    - WEBPASSWORD=asecret
    - INTERFACE=eth0
    - USER_UID=1000
    - USER_GID=1000
    volumes:
    - ./volumes/pihole/etc-pihole/:/etc/pihole/
    - ./volumes/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/
    restart: unless-stopped
    networks:
    - internal_nw

But you can even get rid of publishing port 80. Just use npm to forward pihole.mydomain.com to pihole:80.

<!-- gh-comment-id:869458311 --> @bpycinski commented on GitHub (Jun 28, 2021): There is no problem at all. Just map the port to anything other, e.g. 8080 See my docker-compose, it works very well: services: pihole: container_name: pihole image: pihole/pihole:latest ports: - "8080:80/tcp" - "53:53/tcp" - "53:53/udp" - "67:67/udp" environment: - WEBPASSWORD=asecret - INTERFACE=eth0 - USER_UID=1000 - USER_GID=1000 volumes: - ./volumes/pihole/etc-pihole/:/etc/pihole/ - ./volumes/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/ restart: unless-stopped networks: - internal_nw But you can even get rid of publishing port 80. Just use npm to forward `pihole.mydomain.com` to `pihole:80`.

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@scottpageindysoft commented on GitHub (Jul 22, 2021):

I run the same on my network, and the solution above is correct.
Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally

I've had zero issues with this, and I run 80 sites exposed through NPM.

All other internal sites can use any other port that doesn't conflict with others.

<!-- gh-comment-id:884633644 --> @scottpageindysoft commented on GitHub (Jul 22, 2021): I run the same on my network, and the solution above is correct. Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally I've had zero issues with this, and I run 80 sites exposed through NPM. All other internal sites can use any other port that doesn't conflict with others.

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@asyba commented on GitHub (Jul 23, 2021):

I run the same on my network, and the solution above is correct.
Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally

I've had zero issues with this, and I run 80 sites exposed through NPM.

All other internal sites can use any other port that doesn't conflict with others.

what about using only for lan local? for example if I want to access some service with a NPM domain name example.service to 192.168.1.100:8989 ?
I have pihole and NPM docker compose, but going to example.service is not happening nothing.

<!-- gh-comment-id:885674161 --> @asyba commented on GitHub (Jul 23, 2021): > I run the same on my network, and the solution above is correct. > Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally > > I've had zero issues with this, and I run 80 sites exposed through NPM. > > All other internal sites can use any other port that doesn't conflict with others. what about using only for lan local? for example if I want to access some service with a NPM domain name example.service to 192.168.1.100:8989 ? I have pihole and NPM docker compose, but going to example.service is not happening nothing.

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@BenJule commented on GitHub (Oct 23, 2022):

i get an ERR_CONNECTION_TIMED_OUT in my browser!

Nginx-Proxy-Manager

version: '3'
services:
  nginx-proxy-manager:
    container_name: nginx-proxy-manager
    hostname: nginx-proxy-manager
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - /home/benlue/Docker/Nginx-Proxy-Manager/data:/data
      - /home/benlue/Docker/Nginx-Proxy-Manager/letsencrypt:/etc/letsencrypt

ip a

[root@docker-nginx-proxy-manager:/app]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
136: eth1@if137: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.17.0.2/16 brd 172.17.255.255 scope global eth1
       valid_lft forever preferred_lft forever

Pi-Hole:

version: "3"
 
services:
  pihole:
    container_name: pihole
    hostname: pi-hole
    image: pihole/pihole:latest
    ports:
      - "82:80/tcp"
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp"
    environment:
      TZ: 'Europe/Berlin'
      WEBPASSWORD: 'AweSomePass'
      INTERFACE: 'enp0s3'
    volumes:
      - '/var/run/docker.sock:/docker.sock'
      - '/home/benlue/Docker/Pihole/etc:/etc/pihole/'
      - '/home/benlue/Docker/Pihole/dnsmasq:/etc/dnsmasq.d/'
      - '/home/benlue/Docker/etc/resolv.conf:/etc/resolv.conf'
 
    restart: unless-stopped

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
138: eth1@if139: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.17.0.3/16 brd 172.17.255.255 scope global eth1
       valid_lft forever preferred_lft forever

<!-- gh-comment-id:1288129036 --> @BenJule commented on GitHub (Oct 23, 2022): i get an ERR_CONNECTION_TIMED_OUT in my browser! **Nginx-Proxy-Manager** ``` version: '3' services: nginx-proxy-manager: container_name: nginx-proxy-manager hostname: nginx-proxy-manager image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - /home/benlue/Docker/Nginx-Proxy-Manager/data:/data - /home/benlue/Docker/Nginx-Proxy-Manager/letsencrypt:/etc/letsencrypt ``` ip a ``` [root@docker-nginx-proxy-manager:/app]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 136: eth1@if137: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 172.17.0.2/16 brd 172.17.255.255 scope global eth1 valid_lft forever preferred_lft forever ``` **Pi-Hole:** ``` version: "3" services: pihole: container_name: pihole hostname: pi-hole image: pihole/pihole:latest ports: - "82:80/tcp" - "53:53/tcp" - "53:53/udp" - "67:67/udp" environment: TZ: 'Europe/Berlin' WEBPASSWORD: 'AweSomePass' INTERFACE: 'enp0s3' volumes: - '/var/run/docker.sock:/docker.sock' - '/home/benlue/Docker/Pihole/etc:/etc/pihole/' - '/home/benlue/Docker/Pihole/dnsmasq:/etc/dnsmasq.d/' - '/home/benlue/Docker/etc/resolv.conf:/etc/resolv.conf' restart: unless-stopped ``` ip a ``` 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 138: eth1@if139: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 172.17.0.3/16 brd 172.17.255.255 scope global eth1 valid_lft forever preferred_lft forever ```

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@valyrian84 commented on GitHub (Mar 11, 2023):

I have a similar setup and not sure why but all other containers are accessible, except my Pihole.
I get HTTP ERROR 404.

The frustration is killing me. :)

<!-- gh-comment-id:1464715102 --> @valyrian84 commented on GitHub (Mar 11, 2023): I have a similar setup and not sure why but all other containers are accessible, except my Pihole. I get HTTP ERROR 404. The frustration is killing me. :)

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@bmmmm commented on GitHub (Mar 11, 2023):

@valyrian84 , if you want help, you need to provide more information about your concrete case.
Such as providing your configuration / docker-compose from the relevant services and describe the situation/issue/ use case/ how you access it, with your own words.
Looking forward to help you 😊

<!-- gh-comment-id:1464880225 --> @bmmmm commented on GitHub (Mar 11, 2023): @valyrian84 , if you want help, you need to provide more information about your concrete case. Such as providing your configuration / docker-compose from the relevant services and describe the situation/issue/ use case/ how you access it, with your own words. Looking forward to help you 😊

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@valyrian84 commented on GitHub (Mar 11, 2023):

@bmmmm Absolutely. Here you go -

I have a few containers which includes a pihole instance and a nginx proxy manager instance and a few more.

I also run an UDM which is default-gateway to all the various VLANs and subnets that I have in the network. The Internet connection is directly to the UDM. I have ports 80-81, 443 forwarded to Nginx host in UDM.

I have also registered a few FQDNs in DuckDNS and I can see that I am able to resolve and PING from the internet fine.

I have added the FQDNs in the environment variables in my local DuckDNS container.

I have proxy hosts set in my Nginx Proxy for the target on the right host port for PiHole its set to the correct port which for me is 1010 which translates to 80 for the container. But I am not able to access it neither from inside or outside.

Local access using IP Address and port works fine.

I even removed SSL for the host to see if becomes accessible but it showed same results.

Note - I am able to access other containers from public internet fine with the same setup and configurations.

<!-- gh-comment-id:1464941510 --> @valyrian84 commented on GitHub (Mar 11, 2023): @bmmmm Absolutely. Here you go - I have a few containers which includes a pihole instance and a nginx proxy manager instance and a few more. I also run an UDM which is default-gateway to all the various VLANs and subnets that I have in the network. The Internet connection is directly to the UDM. I have ports 80-81, 443 forwarded to Nginx host in UDM. I have also registered a few FQDNs in DuckDNS and I can see that I am able to resolve and PING from the internet fine.  I have added the FQDNs in the environment variables in my local DuckDNS container. I have proxy hosts set in my Nginx Proxy for the target on the right host port for PiHole its set to the correct port which for me is 1010 which translates to 80 for the container. But I am not able to access it neither from inside or outside.  Local access using IP Address and port works fine. I even removed SSL for the host to see if becomes accessible but it showed same results. Note - I am able to access other containers from public internet fine with the same setup and configurations.

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@bmmmm commented on GitHub (Mar 11, 2023):

@valyrian84 - I haven't prepared an answer yet. in the last picture you expose your domain. just because you masqueraded it before ;)

What I think ^^:
The machine is in your local network, right?
I assume that UDM is your router, right?

screenshot from the browser:
404 because you enter via port 80 (http) and you might have no webserver running on your pihole on port 80.

telnet screenshot:
you want to enter your network (router) on port 1010, but as you mentioned before, you only opened 80,81 and 443.
If this device is in your local network, I wouldn't expose port 81 to the internet.

Feel free to correct me if I misunderstood your setup :)

<!-- gh-comment-id:1464963962 --> @bmmmm commented on GitHub (Mar 11, 2023): @valyrian84 - I haven't prepared an answer yet. in the last picture you expose your domain. just because you masqueraded it before ;) --------------------------------- What I think ^^: The machine is in your local network, right? I assume that UDM is your router, right? screenshot from the browser: 404 because you enter via port 80 (http) and you might have no webserver running on your pihole on port 80. telnet screenshot: you want to enter your network (router) on port 1010, but as you mentioned before, you only opened 80,81 and 443. If this device is in your local network, I wouldn't expose port 81 to the internet. Feel free to correct me if I misunderstood your setup :)

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@valyrian84 commented on GitHub (Mar 11, 2023):

@bmmmm Thanks for pointing out my naivety. The snippet has now been removed.

Coming back to the topic, my pihole is running on a Pi (along with other containers). The host port of 1010 is mapped to Pihole container's 80.
As for the NPM config, I only have 80 and 443 opened in the NPM. The NPM is redirecting the incoming requests to actual hosting inside ports (1010 in the case of Pihole) based off the FQ URL.

I hope I was able to clarify your queries.

<!-- gh-comment-id:1465012643 --> @valyrian84 commented on GitHub (Mar 11, 2023): @bmmmm Thanks for pointing out my naivety. The snippet has now been removed. Coming back to the topic, my pihole is running on a Pi (along with other containers). The host port of 1010 is mapped to Pihole container's 80. As for the NPM config, I only have 80 and 443 opened in the NPM. The NPM is redirecting the incoming requests to actual hosting inside ports (1010 in the case of Pihole) based off the FQ URL. I hope I was able to clarify your queries.

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@crispybegs commented on GitHub (Apr 8, 2023):

I run the same on my network, and the solution above is correct.
Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally
I've had zero issues with this, and I run 80 sites exposed through NPM.
All other internal sites can use any other port that doesn't conflict with others.

what about using only for lan local? for example if I want to access some service with a NPM domain name example.service to 192.168.1.100:8989 ? I have pihole and NPM docker compose, but going to example.service is not happening nothing.

did you ever work this out? trying to find out how to do it myself at the moment

<!-- gh-comment-id:1500999279 --> @crispybegs commented on GitHub (Apr 8, 2023): > > I run the same on my network, and the solution above is correct. > > Have your router point 80 and 443 to NPM, then have NPM reverse proxy to all other sites, including PiHole web interface, internally > > I've had zero issues with this, and I run 80 sites exposed through NPM. > > All other internal sites can use any other port that doesn't conflict with others. > > what about using only for lan local? for example if I want to access some service with a NPM domain name example.service to 192.168.1.100:8989 ? I have pihole and NPM docker compose, but going to example.service is not happening nothing. did you ever work this out? trying to find out how to do it myself at the moment

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 9, 2024):

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

<!-- gh-comment-id:1986685527 --> @github-actions[bot] commented on GitHub (Mar 9, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@flyingoctopus commented on GitHub (Oct 18, 2024):

👍

<!-- gh-comment-id:2422986033 --> @flyingoctopus commented on GitHub (Oct 18, 2024): 👍

kerem commented 2026-02-26 06:35:19 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 20, 2025):

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

<!-- gh-comment-id:2989610003 --> @github-actions[bot] commented on GitHub (Jun 20, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

dependabot/npm_and_yarn/backend/liquidjs-10.25.7

dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987

dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41

dependabot/npm_and_yarn/backend/basic-ftp-5.3.0

dependabot/npm_and_yarn/test/follow-redirects-1.16.0

dependabot/npm_and_yarn/test/axios-1.15.0

dependabot/npm_and_yarn/frontend/lodash-4.18.1

dependabot/npm_and_yarn/backend/lodash-4.18.1

dependabot/npm_and_yarn/test/lodash-4.18.1

dependabot/npm_and_yarn/frontend/vite-7.3.2

dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21

dependabot/npm_and_yarn/frontend/lodash-es-4.18.1

dependabot/npm_and_yarn/frontend/happy-dom-20.8.9

dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0

dependabot/npm_and_yarn/frontend/picomatch-4.0.4

dependabot/npm_and_yarn/backend/picomatch-2.3.2

dependabot/npm_and_yarn/frontend/yaml-1.10.3

dependabot/npm_and_yarn/test/flatted-3.4.2

dependabot/npm_and_yarn/test/tar-7.5.11

dependabot/npm_and_yarn/frontend/immutable-5.1.5

master

dependabot/npm_and_yarn/test/glob-10.5.0

dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1

dependabot/npm_and_yarn/test/form-data-4.0.4

v3-abandoned

bump-freedns

openidc

ssl-passthrough-hosts

static-content

v2.14.0

v2.13.7

v2.13.6

v2.13.5

v2.13.4

v2.13.3

v2.13.2

v2.13.1

v2.13.0

v2.12.6

v2.12.5

v2.12.4

v2.12.3

v2.12.2

v2.12.1

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.4

v2.10.3

v2.10.2

v2.10.1

v2.10.0

v2.9.22

v2.9.21

v2.9.20

v2.9.19

v2.9.18

v2.9.17

v2.9.16

v2.9.15

v2.9.14

v2.9.13

v2.9.12

v2.9.11

v2.9.10

v2.9.9

v2.9.8

v2.9.7

v2.9.6

v2.9.5

v2.9.4

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.1

v2.8.0

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.4

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.1

v2.1.0

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.0

v2.0.0

1.1.2

1.1.1

1.0.1

Labels

Clear labels   

awaiting feedback

  

bug

  

cannot reproduce

  

dns provider request

  

duplicate

  

enhancement

  

enhancement

  

enhancement

  

good first issue

  

help wanted

  

invalid

  

need more info

  

no certbot plugin available

  

product-support

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

stale

  

troll

  

upstream issue

  

v2

  

v2

  

v2

  

v3

  

wontfix

No labels

awaiting feedback

bug

cannot reproduce

dns provider request

duplicate

enhancement

enhancement

enhancement

good first issue

help wanted

invalid

need more info

no certbot plugin available

product-support

pull-request

question

stale

troll

upstream issue

v2

v2

v2

v3

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

No description provided.