Community Developer
  • Content Count

  • Joined

  • Last visited

Everything posted by spants

  1. Ok, useful feedback but that wasn't my experience. I changed the repository line and applied.
  2. yes - you should change to this new repository. Unfortunately when I updated the template, this does not roll down to existing users
  3. You can check the Docker release versions here: The latest official "release" was delivered 2 months ago. You can try the dev_amd64 or dev releases if you wish.
  4. I used to do the same - and had a similar problem. Does this solve it for you too? ( add this to the extra parameters in template: --device=/dev/ttyUSB1 --user=root ) or other user.....
  5. see here: Edit the template and set Repository to nodered/node-red-docker:v8 it was mentioned here in the github link you sent:
  6. yes, use the unraid scripts plugin to automate that once a day. It is what I used to set the password before it was exposed to the template
  7. I understand and agree - I guess that in future I should just do a v2 template
  8. np, I'm not sure why it doesn't replicate to everyone.
  9. Click on icon and choose edit - you will see the repository
  10. I believe that there is a way of forcing the traffic and dns through openvpn - but its not something I am experienced with. May be best to ask in the OpenVPN topic.
  11. I wrote the template that pulls in the Official Docker Container from PiHole. I swapped over from my unofficial one a long time ago that that a fully supported version could be distributed. Make sure that your repository for pihole is = pihole/pihole:latest and not the old diginc repository. If you use the latest tag, you should have v 4.0.0-1. The release tags are here: The last update to the docker image was 12 days ago. Apparently you should not do an update within the docker image (that was what diginc said - although that may
  12. Hi - I'm stupid!. I made a silly mistake on the changes to the docker template. It should start working soon. Reply here and let me know if the changes happen in the next day or so. If not, change the repository to pihole/pihole:latest
  13. Hi @Squid ==== please ignore. I'm stupid. I left some extra xml tags in the template which confused it ==== For some reason my pihole template doesn't show the changes I made two weeks ago. Is it something that I have done wrong on the template?. cheers Tony
  14. I use the same repo without issues... Is your nodeRed port open to the world?. edit: Add more info from the entry on the NodeRed mailing list that Stupifier created: .... I think that he had left the port 1880 open on his firewall: Be careful out there!
  15. 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
  16. not sure - I use it in bridge mode and forward port 1883
  17. 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.
  18. excellent bug reporting! Please can other people add their experiences if relevant.
  19. Hi Guys As mentioned, this is just a template for the docker image that is built here Please can you raise an issue on the github? cheers Tony
  20. 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 )
  21. 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...!
  22. Thanks for doing this!. It will make life easier. BTW, is onvif fully supported now?
  23. I am looking at this again.... Will report back soon.