spants

I changed the template 2 weeks ago but it would probably (and hopefully!) not update anyones existing settings.... Note that my system works perfectly on BR0 but I understand that others have problems

not sure - I use it in bridge mode and forward port 1883

Do you have anything else using port 1883?

Hi Semtex41 Thanks for the suggestions which I have now put into the master template (UID and change to eth0). I guess that many of us were not having issues due to running it before and manual tweaks etc. The changes to the template should update shortly.

excellent bug reporting! Please can other people add their experiences if relevant.

Hi Guys As mentioned, this is just a template for the docker image that is built here https://github.com/pi-hole/docker-pi-hole/. Please can you raise an issue on the github? cheers Tony

many thanks - will take a look

The Template has been updated and pushed .... Check for updates in the next few hours. Welcome to v4! (if it didn't update for you, change the repository to: pihole/pihole:latest )

I managed to get it working but I cannot get a reliable way of exposing the data inside the docker as volumes on the unraid filesystem..... @cedricverst could do with some help from you...!

Thanks for doing this!. It will make life easier. BTW, is onvif fully supported now?

I am looking at this again.... Will report back soon.

I see that someone is attempting to build a zerotier controller module for PFsense..... that would be great for me. Currently very alpha though.

This is the problem: /etc/pihole/setupVars.conf: line 4: 9.9.9.9: command not found What is in your setupVars.conf file?

Have you also checked diginc's github page for help?

digiinc updates his docker images quite frequently. If you check your Repository points to: diginc/pi-hole:latest The versions of pihole that you have are the latest for the docker image. The diginc release notes are here: https://github.com/diginc/docker-pi-hole/releases https://store.docker.com/community/images/diginc/pi-hole/tags shows that the latest branch was updated 3 months ago. There is a prerelease branch if you want to be brave. Note that the versions will trail the standalone versions due to the work involved in converting them to docker images

I used the "manage pallete" option in node red to install node-red-node-ping. Works well.

Ok, have you tried the Console command on the nodered icon to install Bonjour and then node red "manage pallete" option to install homekit?

Is nodered bridged? Try host network mode

Is unraid using dhcp from your router and router using unraid? If so, set static address in unraid networking and dns to 8.8.8.8 or whatever

Guys, any enhancements for this, please raise it against the docker owner, diginc. I just wrote a simple template for unraid. The diginc github is here:https://github.com/diginc/docker-pi-hole

It might be worth asking here: https://github.com/diginc/docker-pi-hole/issues The template is just a wrapper for his docker image.

The docker is the official standard one so it should work. I don't use https as it just on an internal home network . Wondering if your paths are correct for the certs and/or permissions? I will try and have a look over the weekend ....

take a look here: https://www.hardill.me.uk/wordpress/2015/05/11/securing-node-red/

re the logs: Possible fix here.... https://github.com/diginc/docker-pi-hole/issues/271#issuecomment-389591390

I used to use the script below with the userscripts plugin to delete the logs once a day. It looks like pihole stores a log in /var/log in the docker. The recent Docker from digiinc was supposed to put these on a volume mount. #!/bin/bash DOCKER_NAME=pihole PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # Download any updates from the adlists docker exec $DOCKER_NAME pihole updateGravity > /dev/null # Pi-hole: Update the Web interface shortly after gravity runs # This should also update the version number if it is changed in the dashboard repo #docker exec $DOCKER_NAME pihole updateDashboard > /dev/null # Pi-hole: Parse the log file before it is flushed and save the stats to a database # This will be used for a historical view of your Pi-hole's performance # docker exec $DOCKER_NAME dailyLog.sh # note: this is outdated > /dev/null # Pi-hole: Flush the log daily at 11:58 so it doesn't get out of control # Stats will be viewable in the Web interface thanks to the cron job above docker exec $DOCKER_NAME pihole flush > /dev/null