spants

Community Developer
  • Posts

    586
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by spants

  1. 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 ....
  2. take a look here: https://www.hardill.me.uk/wordpress/2015/05/11/securing-node-red/
  3. re the logs: Possible fix here.... https://github.com/diginc/docker-pi-hole/issues/271#issuecomment-389591390
  4. 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
  5. Have you set DNS1 and DNS2 variable to point to 8.8.8.8 or 1.1.1.1 ? If pihole doesnt need to block it, uses DNS1 and DNS2 to do the look up. Try posting a screenshot of your settings if not.
  6. maybe its because of https://github.com/diginc/docker-pi-hole/issues/265? My template just calls diginc's docker so I have no control over it. Don't forget that you can change the repository to use a specific version by using tags https://hub.docker.com/r/diginc/pi-hole/tags/
  7. The best way is to find the author of the node on flows.Nodered.org and raise an issue on github/slack/Google groups Tony
  8. My node red template is for the official docker.... I used to work with the guys that wrote node red!... The mqtt one needed work to support passwords - these are imported and encrypted when the docker starts.
  9. It is strange! I used to run it on the unraid ip with the unraid port changed. I then moved to separate ips and that works great for me. I do have two nics installed....
  10. Why would you create another nodered docker and mosquito docker? What was missing from mine?
  11. I just turn mine off just in case I want to use a normal dns ....
  12. Nope - you have to wait until diginc tests and updates the docker
  13. **** Spaceinvader One has created a setup video.. See it here ***
  14. If you set dns1 and dns2 to Unbound, it gets changed?
  15. Is your server at 192.168.1.22? (mine is!) Also a few post back it was found that unraid VM install pinches poet 53. I think if you disable VM, install, re-enable VM it should work (I think that was how people did it). I didnt have the problem....
  16. strange, mine works well. Try clearing browser cache?
  17. You have no queries or clients to graph.... are the clients pointing to your pihole server? When you go to Tools/Tail pihole.log, are things being added?
  18. It shouldn't introduce latency, all it is doing is providing a dns lookup- the traffic should behave as normal
  19. Look at the query log on the UI when visiting the site. It will tell you what is being blocked.
  20. good to hear. I will create a script that people can run when the docker is updated. 1. Not sure why. As mentioned before I just made the simple template, digiinc did the hard work. It might be worth checking the github for it https://github.com/diginc/docker-pi-hole. (reminds me that I need to see if the bug for debian was fixed) 2. The script will need to be run again as it modifies the docker rather than being just data 3. I dont, sorry.
  21. Your server ip is wrong, key 1 should be your pi-hole server ip. Currently the ads are being replaced by the unraid ui hence the password prompt
  22. Hi guys, can you try the following to see if it speeds things up for you. I will roll it into a batch file so that you can run it after the docker is updated. 1. SSH to your Unraid server with pihole docker running 2. Copy and paste the following lines docker exec -it pihole apt-get update docker exec -it pihole apt-get --reinstall install iptables docker exec -it pihole apt-get install iptables-persistent docker exec -it pihole iptables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole iptables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole iptables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole ip6tables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole iptables-save > /etc/iptables/rules.v4 docker exec -it pihole ip6tables-save > /etc/iptables/rules.v6 Not sure if I need to change the "apt-get install" to "apt-get -y install" to accept the defaults - let me know...
  23. I'm back from travelling... Will have a look over the next couple of days....