spants
-
Posts
637 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by spants
-
-
13 hours ago, Natrium said:
I can't get this thing to work.
Updated to 6.4rc18f to use the custom IP so.I don't have to change the WebGui port, disabled the VM Manager in the Settings but I still get the following error:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="pihole" --net="bridge" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "ServerIP"="192.168.1.169" -e "DNS1"="8.8.8.8" -e "DNS2"="8.8.4.4" -e "IPv6"="False" -e "TZ"="Europe/London" -e "WEBPASSWORD"="admin" -e "INTERFACE"="br0" -e "DNSMASQ_LISTENING"="all" -p 53:53/tcp -p 53:53/udp -p 80:80/tcp -v "/mnt/user/appdata/pihole/pihole/":"/etc/pihole/":rw -v "/mnt/user/appdata/pihole/dnsmasq.d/":"/etc/dnsmasq.d/":rw --cap-add=NET_ADMIN diginc/pi-hole:alpine
ef6fe6f9920330e35c5f4fa95cdbd1c6dcffcc9b40035b3b853c7d2a8f92ea66
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint pihole (925bd810733853ba4e7ce50fefa1130e787865a32609efa12665970d857e8278): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.
The command failed.Are you starting this from docker manager tab
is ServerIP = the ip of the new ip for the docker that you have given it?
-
19 hours ago, live4soccer7 said:
The node red dash is absolutely perfect for what I need! Thanks for the suggestion.
I have a question regarding node red DELAY node. What is the maximum delay that can be set in this delay node? I have up to 24 hr delays that are feeding in to it, however I just had one that didn't pass through anything after the delay should have run out. I'm thinking that it may have a maximum time delay. Everything else I've done with it on shorter times for testing always passes through my value. Even the other day when I had it setup for maybe 3-4hrs it passed through the msg. On the longer one I just did (8hrs roughly) nothing passed through and there were not messages on the debug resulting in this failure of the output of the delay timer.
Ben wrote this Node - would be best to ask him: https://www.hardill.me.uk/wordpress/2013/10/02/node-red-delay-node-formally-pause-node/.
BTW, You can find all sorts of flows and nodes here: https://flows.nodered.org/
You might want to look at BigTimer by Pete Scargill for controlling lights - It is what I use.
-
yes - all in docker images.
Influx/grafana is great for timeseries data.
NodeRed (with NodeRed dashboard) makes integrating this very easy. Can create switches etc.
the BigTimer node can be use to scheduler things (including offsets to dawn/dusk)
Lots of nice videos on youtube if you are not sure how to use it.
-
I just use voice (via Alexa) to control things. I have used Imperihome (android/ios) and NodeRed dashboard in the past
-
I use:
device -> mqtt -> node red -> influxdb -> grafana (dashboard)
alexa -> node red -> (custom skills)
I havent used Dashing for a while.... Data is still being sent to CouchDB but I may switch that off as I'm not really using it.
Tony
-
On 14/12/2017 at 12:33 PM, PiZZaMaN2K said:
Is there any ETA on ipv6 support? it seems that over 50% of my DNS requests are ipv6 on my network.
It seems that 6.4 unraid supports ipv6, pihole supports ipv6 but even when you choose (in the template) ipv6 = True, the options are greyed out....not sure...
You could try changing the repository to point to one of the other builds https://hub.docker.com/r/diginc/pi-hole/tags/ - but I couldnt get the latest debian_dev to work.
The template uses "alpine" although alpine_dev also works
-
3 minutes ago, Mlatx said:
@spants I'm still having an issue with this setup when it comes to configuring single node. Once you put the parameters in and click configure node, it should give you a message that it successfully completed where it then creates the _users and other db's. Nothing is happening when I click on the green button "configure node." Is that an issue in the template?
Nothing to do with the template as it just deploys the (semi)official docker image, thats all.....
Here are the docs for it: https://github.com/apache/couchdb-docker . Can you see if this helps?
-
@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
-
On 11/12/2017 at 6:32 AM, Mlatx said:
Is couchdb 2.x setup correctly? Under databases on the web interfaces, you are supposed to get a _users database but no pre defined database shows. In addition, hitting the setup as single node button does nothing. Also, is there any chance to get couchdb 2.1.1?
I'm trying to sync a large database, and it is constantly freezing. I'm wondering if this is configured correctly. Thanks.
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
-
7 hours ago, goinsnoopin said:
Spants,
I am looking to use the MQTT docker with the letsencrypt reverse proxy. My goal was to use my domain name mqtt.MYDOMAINNAME.com for MQTT messages for cell phones for location detection and other devices that are not on my local lan.
I have been having difficulty getting this to work...clients are failing to connect. I may have a bust in my letsencrypt config. While investigating this, I came across this website: http://frankfurtlovesyou.com/posts/mqtt-bridge-with-mosquitto-and-nginx.html
Just wondering how you handle MQTT when you are not on your local lan. I am trying to avoid a port forward as I feel reverse proxy is safer. Any thoughts?
Thanks,
Dan
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 .....
root@Tower:~# 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": {}
}
] -
3 minutes ago, meestark said:
@spants What's the output of "docker network ls"?
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
-
On 13/11/2017 at 12:25 AM, H2O_King89 said:
any info about the cornjob for the logs?
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)
-
9 hours ago, H2O_King89 said:
Okay just want to make sure I understand this. ^^^
and this is old^^^ don't see a date on this.
also is there a cornjob still needed for log?
im on 6.4rc10 and change the port to 84 under Identification settings and still can't start in bridge and no other docker is using port 80.
Change to br0 and gave it an ip works but Fix Common Problems is bugging my OCD
- 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
-
On 18/10/2017 at 6:53 PM, MrBaz said:
I'm currently having an issue with this booting up - Had a couple of issues getting to this point but all covered by what others have got.
Currently I am having it crash after Pi-hole blocking is enabled:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful ::: Testing DNSmasq config: ::: Testing PHP-FPM config: ::: Testing NGINX config: ::: All config checks passed, starting ... ::: Docker start setup complete - beginning s6 services ::: ::: Neutrino emissions detected... ::: ::: Pulling source lists into range... done! ::: ::: Getting raw.githubusercontent.com list... done ::: Status: Success (OK) ::: List updated, transport successful! ::: Getting mirror1.malwaredomains.com list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting sysctl.org list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting zeustracker.abuse.ch list... done ::: Status: Success (OK) ::: List updated, transport successful! ::: Getting mirror1.malwaredomains.com list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting sysctl.org list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting zeustracker.abuse.ch list... done ::: Status: Success (OK) ::: List updated, transport successful! ::: Getting s3.amazonaws.com list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting s3.amazonaws.com list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: Getting hosts-file.net list... done ::: Status: Not modified ::: No changes detected, transport skipped! ::: ::: Aggregating list of domains... done! ::: Formatting list of domains to remove comments.... done! ::: 136851 domains being pulled in by gravity... ::: Removing duplicate domains.... done! ::: 113087 unique domains trapped in the event horizon. ::: ::: Adding adlist sources to the whitelist... done! ::: Whitelisting 6 domains... done! ::: Exact blocked domains: 0 ::: No wildcards used! ::: Formatting domains into a HOSTS file... done! ::: ::: Cleaning up un-needed files... done! ::: ::: Refresh lists in dnsmasq...s6 service not found for dnsmasq, exiting... done! netstat: /proc/net/tcp6: No such file or directory ::: DNS service is running ::: Pi-hole blocking is Enabled killall: dnsmasq: no process killed [cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.Any pointers / ideas what could be going wrong would be appreciated .
wondering if this is related to the permissions problem a couple of others have noted .... Will have a look at solutions.
-
On 17/10/2017 at 11:36 PM, Kewjoe said:
My primary server is on 6.3.5
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
-
1
-
-
Unfortunately I dont use home-assistant... I built all my Home Automation on NodeRed (and mqtt)
-
1 hour ago, LordShad0w said:
I am also trying to get MQTT working in Homeassistant and can not seem to do it. I have it working perfectly on my Pi3 but in my UNraid docker it refuses to work. Also, since my install is in appdata/mqtt/ I can not run dockersafe new permissions. Which is rough because I also can not see any files inside that directory even though it is shared. If I use MC, I can see everything but I don't know enough to get in and create the new file for passwords in there.
Any assistance would be appreciated.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
[SUPPORT] pihole for unRaid - Spants repo
in Docker Containers
Posted
I have just updated it - thanks for the heads-up!