spants

@Mlatx I have just changed the couchdb v2 template so it should be picked up soon. If you cant wait, click edit on the icon and change the Repository to apache/couchdb

I will take a look at this for you. I use 2.0.0 and have a _users db. I see that the registry moved hence the upgrade to 2.1.1 didnt happen. My template just fronts the dockers built by klaemo. It may take a day or two as I am travelling at the moment. Tony

I use a non-standard port number with user/pass. The url is maintained by a dynamic dns service. You can also limit the Topics and actions by username to restrict access

change flow to flows for each.... (keep a backup) ie to: flows.json flows_cred.json

Great! thanks for the info .... Will be putting pihole and other stuff on it

many thanks for looking at this ..... [email protected]:~# docker network inspect br0 [ { "Name": "br0", "Id": "f07c68001ad177b9071f64b1837b4cad117f60b7e3648adbc539bef41ac08ff1", "Created": "2017-12-06T15:59:21.310581567Z", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.1.0/24", "IPRange": "192.168.1.0/25", "Gateway": "192.168.1.1", "AuxiliaryAddresses": { "server": "192.168.1.22" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "br0" }, "Labels": {} } ]

NETWORK ID NAME DRIVER SCOPE f07c68001ad1 br0 macvlan local d8cefac70d2c bridge bridge local 84413264ada5 host host local 0fbf02a8dfac none null local

I wish I could get this to work!..... 2 network interfaces eth0: has Ip address 192.168.1.22, gateway 192.168.1.1, ipv4 only, bridge enabled eth1: IPV4, no IP, bridge enabled I am trying to do: docker network create \ -o parent=br1 \ --driver macvlan \ --subnet 192.168.1.0/24 \ --ip-range 192.168.1.64/28 \ --gateway 192.168.1.1 \ localnetwork ...and get "Error response from daemon: failed to allocate gateway (192.168.1.1): Address already in use"

I seem to remember that the default name for the flows/creds changed some time back....now flows.json and flows_cred.json

Sorry - I cant find any log details on the diginc docker website. I guess that the userscript will work but havent tried it. edit: Looks like I will have to look into it as my logfile refuses to load (probably too big)

On the old version, you had to create a couple of empty files before it would start You can now set an interface to listen to (Dual nic setup maybe?) It now creates 2 new directories in the appdata folder that you have assigned. If you used the same appdata folder, it will have your existing files in the root of that folder which include your whitelist and blacklist files. Print them out or copy each entry into the new pihole by the web interface. Re port change, was it an error that 80 was in use or 53 DNS?. I didnt have the problem but some people have said previously that they turn off the VMs and then installed pihole and it works. Otherwise give it a new IP (and can you tell FixCommon to ignore?)

New version 2 template added. No need to create files anymore. Easier to define listening NET interface

wondering if this is related to the permissions problem a couple of others have noted .... Will have a look at solutions.

Ok, just started having the same permissions problem- at least I have something to work on now!

looks like a permissions problem on the appdata directory for the docker.... (maybe try doing a newperms on that directory (only)). Have you changed the appdata directory to where you need it to be? Just tried it on mine and it is still working well

Unfortunately I dont use home-assistant... I built all my Home Automation on NodeRed (and mqtt)

Passwords for Mosquitto ======================= Mosquitto likes encrypted passwords, but these are difficult create for a docker instance. In the mosquitto.conf file, you will see the password file is called passwords.mqtt. Do not change this. To add passwords to the MQTT instance, just store a file called passwords.txt in this directory and restart the docker. The passwords will be encrypted and stored in passwords.mqtt and the old passwords.txt file will be deleted. The contents of passwords.txt should look like this: bob:bobpassword fred:fredpassword The new passwords are added to the top of password.mqtt when they are encrypted. MQTT uses the first username/password combo that it finds. You can delete the old passwords manually if you wish. 1) stop the mqtt docker 2) ssh to the unraid server and navigate to the appdata directory 3) type nano passwords.txt and add your user:password 4) save file and exit nano 5) restart docker = it should import and create the users and put them in passwords.mqtt (use MC, highlight passwords.mqtt and press F3 Hope that helps

Glad you are getting it working. Perhaps I should rename ServerIP in the template to PiHoleServerIP?

What are you trying to do? My template just is a loader for the diginc docker.... no changes are made The URL is: https://hub.docker.com/r/diginc/pi-hole But just use my template! EDIT: you do have the Community Applications plugin installed, do you?

I believe that you can do this with 6.4 but I havent tried it as yet. My system is very stable and I dont want to tweak it whilst I sort out an intermittent network switch problem on my network!

Not tried it, but: https://discourse.pi-hole.net/t/how-do-i-block-ads-on-youtube/253

did an update happen at the same time? I know that there is now a drop down menu that you select what network the docker is attaching to on the latest 6.4 rc. I have a dual nic server but only one is connected and I dont have an issue....

what version of unraid are you using?

k, I have to go offline now. Maybe a value was added to the allowed networks settings on the plex server via web interface (or automatically). Plex doesnt like the "not fully formed" ip address and is refusing to let you in.... Good luck!

Yes - I need to add proper labels on those! Thanks Tony