Lichtywara

Changed custom br0 to 192.168.50.3 and made sure the SERVER IP variable was the same. Fired right up! I feel a little dumb now but at least I am a dummy with less ads floating around. :) Will make the new changes in my router and I'll be back in business!!! Thank you Squid. Your help was MUCH appreciated!

Anyone have an idea or a few cycles to help me out?? Any time I try to reinstall pihole I get the following output. As mentioned previously I've checked TCP/UDP ports 53, UDP port 67 and TCP port 80, 443 to ensure nothing else was using them. As I understand it ports 53 and 67 are the big ones. Nothing is using them. Port 443 is being utilized by nginx. Changing any of the ports does not seem to make any difference. It is as if there is some network config data still linked from the previous instance of the pihole container that did not get removed properly associated with "custom br0". I tried changing the static IP assigned to my Unraid server also altering all the IPs manually in my other containers. All other containers are working but pihole still breaks if I choose custom br0. "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole-template' --net='br0' --ip='192.168.50.2' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_53'='53' -e 'UDP_PORT_53'='53' -e 'UDP_PORT_67'='67' -e 'TCP_PORT_80'='80' -e 'TCP_PORT_443'='443' -e 'DNS1'='8.8.8.8' -e 'DNS2'='8.8.4.4' -e 'TZ'='America/Toronto' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'ServerIP'='192.168.50.2' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/cache/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/cache/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --restart=unless-stopped 'pihole/pihole:latest' 7c9619cf37bece81f38cfae61a42e46142d727c03348dbe2b94a0795d57fc9b9 docker: Error response from daemon: Address already in use. The command failed."

I've been reading and digging deeper. I read that sometimes the error can occur if the port is already in use. I SSH into Unraid and ran some checks using the lsof command to see if the Pihole ports were already in use. None of the ports seem to be in use. Next I tried changing from custom br0 (needed for Pihole to work properly) to Host. The app then amazingly does start!!! So I tried changing it to bridge to see what would happen which fails the same way as using custom br0. So I feel like I am closer but not sure what is involved here that could be crashing Pihole in Docker immediately when those settings are used. The IP in the previous setup is exactly identical to the current one. Perhaps something is lingering behind so when Pihole now tries to setup/use the same settings its a bust. I don't know where this could be.

I could use some expert help. I installed a SSD cache drive and was attempting to move all docker apps off the array and onto the cache drive. I failed....... I have since removed all other docker apps and started again but this time installing all the apps again on the cache drive instead. The only app that refuses to come back gracefully is Pihole Template. I receive the following error running pihole after deleting and re-installing pihole-template from CA: "Execution error Error code 403" I have tried removing pihole and ensuring that the appdata folder has been cleaned of any leftover data however each time I try to reinstall I get the same result. When I choose to look at the logs from Pihole they are blank. It does not appear as if anything is being written to them. Previous attempts would yield a failure stating that the address is already in use at installation time. I no longer get that error message. The app seems to install cleanly now but again will not start with the above error. I am really stuck and run out of talent to get this fixed. Tried Googling the answer but I'm not really finding any help. My Linux knowledge is very limited which doesn't help but I can get around a little. I've rebooted and created a Diagnostic which I hope attaches OK. Any help from the community would be appreciated!! unraid-diagnostics-20210418-1411.zip