Nginx Proxy Manager VS docker-pi-hole

I recently had trouble getting an SSL cert, but I found this PR and it already has an image and it works for me. I use Tailscale and my network isn't visible from the internet so I use the DNS Challenge option with GoDaddy and an API key.

I'm trying to use the react-express-mysql awesome-compose as a framework for setting up multiple react apps that are tied to the same domain. Once dev is complete, I update the Dockerfile for the frontend to add in Nginx and have Nginx serve the frontend so that it is not running using npm start. I additionally am using Nginx Proxy Manager as a reverse proxy to route where I need and manage SSL termination for me.

I ended up using the NGINX Proxy Manager [the projects home site] and added certificates but I'm seeing a fair number of installs going with https://traefik.io on YouTube.

Nginx Proxy Manager is a very easy and popular reverse proxy with a GUI.

Otherwise is the Nginx Proxy Manager a nice looking Reverse Proxy based on nginx with a GUI. I've been using it myself for a few years and experienced a few times some stability problems after updating with docker compose. Otherwise rock solid for me.

My reverse proxy does it automatically, NginxProxyManager.

Put on Debian or Ubuntu, using docker/docker-compose install Plex, Nextcloud (nice way to store your files), and some sort of reverse proxy like NPM.

More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/

version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped

services: pihole: container_name: pihole image: pihole/pihole:latest hostname: pihole # Container hostname (optional) domainname: mynetwork.local # Container domain (optional) mac_address: f7:55:63:b0:68:83 # Random MAC address (optional) networks: virtualnet: # Name of macvlan ipv4_address: 192.168.100.249 # Desired IP for pihole dns: - 127.0.0.1 - 1.1.1.1 ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" - "443:443/tcp" volumes: - ./pihole-configs/:/etc/pihole/ - ./dnsmasq.d-configs/:/etc/dnsmasq.d/ # DNSMASQ_USER # https://github.com/pi-hole/docker-pi-hole/issues/963 # https://github.com/pi-hole/docker-pi-hole/blob/master/README.md#upgrade-notes environment: FTLCONF_LOCAL_IPV4: 10.59.0.6 # Desired IP for pihole VIRTUAL_HOST: pihole.mynetwork.local DNSMASQ_USER: root PIHOLE_DNS_: 1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001 restart: unless-stopped # Set container to always restart

I have't yet used the NAS with docker so I don't know how exactly to set it up, but I run my pihole in a container and I just followed the official guide https://github.com/pi-hole/docker-pi-hole

More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/

The Pi-hole documentation addresses the port 53 conflict for Ubuntu and Fedora. See the section “Installing on Ubuntu or Fedora” on this page.

Docker Tag 2023.02.2

version: "3" services: cloudflared: container_name: cloudflared image: visibilityspots/cloudflared:latest restart: unless-stopped networks: pihole_net: ipv4_address: 10.0.0.2 environment: UPSTREAM1: 'https://1.1.1.1/dns-query' UPSTREAM1: 'https://1.0.0.1/dns-query' googleflared: container_name: googleflared image: visibilityspots/cloudflared:latest restart: unless-stopped networks: pihole_net: ipv4_address: 10.0.0.4 environment: UPSTREAM1: 'https://8.8.8.8/dns-query' UPSTREAM2: 'https://8.8.4.4/dns-query' pi-hole: depends_on: [cloudflared, googleflared] container_name: pihole image: pihole/pihole:latest restart: unless-stopped ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "8090:80/tcp" environment: ServerIP: '10.0.0.3' DNS1: '10.0.0.2#5054' DNS2: '10.0.0.4#5054' IPv6: 'true' TZ: 'America/Los_Angeles' DNSMASQ_LISTENING: 'all' WEBPASSWORD: '' VIRTUAL_HOST: 'pi-hole.local' MAXDBDAYS: 7 networks: pihole_net: ipv4_address: 10.0.0.3 dns: - 127.0.0.1 volumes: - './etc-pihole/:/etc/pihole/' - './etc-dnsmasq.d/:/etc/dnsmasq.d/' - './var-log/:/var/log/' # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN restart: unless-stopped deploy: resources: limits: memory: 512M reservations: memory: 128M networks: pihole_net: driver: bridge ipam: config: - subnet: 10.0.0.0/29