[support] Spants - NodeRed, MQTT, Dashing, couchDB


Recommended Posts

Strange....

 

The docker is built on Linuxserver.io base and uses environment variables to set the PGID and PUID to suit Unraid (check the advanced view). If you miss these variables you will get this problem. I always use the docker page to start and stop the docker.

 

To add passwords, create a passwords.txt file  - do not edit the passwords.mqtt directly. Info in passwords.README file.

The way I use it - create the /config directory and everything should be setup.

Stop the docker, create a passwords.txt and then start the docker.

It will encrypt the passwords, add it to the top of passwords.mqtt and then delete passwords.txt.

 

I have a lot of devices using it - hope it works for you

 

If you have to use the cmdline, try the following:

docker run -t -i --net="bridge" -p 1883:1883/tcp -p 9001:9001 -v /mnt/cache/app_config/mqtt/:/config:rw -e PGID=100 -e PUID=99 spants/mqtt

Link to comment
  • 3 weeks later...
  • 2 months later...

Can we easily add new nodes to this docker?

I've tried adding them to the data directory mapping but had no luck.

 

I'd like to try the eibd and knx nodes.

 

I recently updated the docker with the node-red-contrib-npm node to allow you to add npm modules to the flow without a separate install:

http://flows.nodered.org/node/

http://flows.nodered.org/flow/3c17c7bf227d1a8952b7

 

However this might only work for simple modules.

 

Can you send me the Nodes that you need and I will add them for you. I am also working on an update to this docker to allow you to easily add your own....

Tony

Link to comment

The node had a dependency so I guess it won't work with the npm node.

 

It's this node in particular:

http://flows.nodered.org/node/node-red-contrib-eibd

 

However if you are working on updating the docker so we can add them ourselves i should maybe just wait a little while :)

 

Are you updating to node-red 0.12?

 

I have now updated the version to v0.12.4.

 

I had a problem with the EIBD node that you requested - a strange error in the .js file for that Node. Do you have it working elsewhere?

Link to comment

The node had a dependency so I guess it won't work with the npm node.

 

It's this node in particular:

http://flows.nodered.org/node/node-red-contrib-eibd

 

However if you are working on updating the docker so we can add them ourselves i should maybe just wait a little while :)

 

Are you updating to node-red 0.12?

 

I have now updated the version to v0.12.4.

 

I had a problem with the EIBD node that you requested - a strange error in the .js file for that Node. Do you have it working elsewhere?

Thx for the effort!

 

I'll try and set up a test install today to try it.

I'll let you know how it goes.

Link to comment

I got it working.

There was an error indeed regarding an " ) ".

I deleted the ) in question as i did not seem to have a corresponding (.

 

The node seems to connect fine to my eibd server.

 

I have the attached the edited .js file.

 

Would it be possible to mount the user node directory an unraid mountpoint so we can add the nodes manually?

11-eibd.zip

Link to comment

I got it working.

There was an error indeed regarding an " ) ".

I deleted the ) in question as i did not seem to have a corresponding (.

 

The node seems to connect fine to my eibd server.

 

I have the attached the edited .js file.

 

Would it be possible to mount the user node directory an unraid mountpoint so we can add the nodes manually?

 

I have notified the maintainer of that Node as I am doing a standard npm install for the Nodes.

Were there any other dependancies ? (did you also have to do:  npm install eibd)

Link to comment

I have just published unRaid-hole to my docker repository.....

 

This doesn't use the same lists as Pi-Hole but it works the same way - just point your DNS addresses to your unRaid tower and it will forward the valid requests via Googles DNS servers and drop the rubbish ones....

 

These are the lists that it uses:

#advertising

http://hosts-file.net/ad_servers.txt

 

#malware

http://hosts-file.net/emd.txt

 

#browser exploits

http://hosts-file.net/exp.txt

 

#fraud

http://hosts-file.net/fsa.txt

 

#spammers

http://hosts-file.net/grm.txt

 

#browser hijackers

http://hosts-file.net/hjk.txt

 

#misleading marketing (fake flash updates, similar trash)

http://hosts-file.net/mmt.txt

 

#illegal pharmacy sites (fake viagra spam?)

http://hosts-file.net/pha.txt

 

#phishing sites

http://hosts-file.net/psh.txt

 

It is based on https://github.com/arthurkay/sagittarius-A but will have lots of unRaid goodies soon!

Link to comment
This doesn't use the same lists as Pi-Hole but it works the same way - just point your DNS addresses to your unRaid tower and it will forward the valid requests vias Googles DNS servers and drop the rubbish ones....
Can this be configured to do .lan internal dns as well? Also split dns would be nice, so you could use the same names internally and externally for published services on your lan.
Link to comment

This doesn't use the same lists as Pi-Hole but it works the same way - just point your DNS addresses to your unRaid tower and it will forward the valid requests vias Googles DNS servers and drop the rubbish ones....
Can this be configured to do .lan internal dns as well? Also split dns would be nice, so you could use the same names internally and externally for published services on your lan.

 

I dont think so. It is using a blacklist for dns calls rather than acting as a dns server

Link to comment
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unRaid-Hole" --net="bridge" -e TZ="Europe/London" -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN spants/unraid-hole
3b83ade50d4ebadac05a93c8a87d82d4c64d9854d55ac9d2301cd561700b7a0d
Error response from daemon: Cannot start container 3b83ade50d4ebadac05a93c8a87d82d4c64d9854d55ac9d2301cd561700b7a0d: Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use

The command failed.

???

Link to comment

Pulling image: spants/unraid-hole:latest
IMAGE ID [latest]: Pulling from spants/unraid-hole.
IMAGE ID [340b2f9a2643]: Pulling fs layer.
<snip>
IMAGE ID [0752514b4a91]: Extracting. Pull complete.
IMAGE ID [cbbe3318f326]: Extracting. Pull complete. Already exists. Digest: sha256:27e5abac0fc87ea1565e63f1c610caa872409cb97484c043cf3bc0f5bb31824e. Status: Downloaded newer image for spants/unraid-hole:latest.

TOTAL DATA PULLED: 8 MB



Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unRaid-Hole" --net="bridge" -e TZ="Europe/London" -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN spants/unraid-hole
93c6d025391ac856998f86cb1e0cc1aed3be73dc5f3ccf570f43653767f3ccd8

The command finished successfully!

 

What other dockers are you using? And what version of unRaid ( I am on 6.1.6)

Link to comment

same error here spants.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unRaid-Hole" --net="bridge" -e TZ="Europe/Paris" -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN spants/unraid-hole
dd41c3acfdb00217dc528d305f3916e6dbcf93ae8e829233bb8c54aa8ff8259f
Error response from daemon: Cannot start container dd41c3acfdb00217dc528d305f3916e6dbcf93ae8e829233bb8c54aa8ff8259f: Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use

The command failed.

 

Unraid 6.1.6.

Running dockers atm are:

couchpotato

Mariadb

nodered

owncloud

plexmediaserver

transmission

Link to comment

can you try completely removing the unRaid-hole using the docker manager, and then as root on Tower, type:

 

docker run -d --name=unraid-hole -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN spants/unraid-hole 

 

and then, if that doesn't work:

 

docker run -d --name="unRaid-Hole" --net="host" -e TZ="Europe/London" --cap-add=NET_ADMIN spants/unraid-hole 

 

^^^ This is the new settings for unRaid-Hole, using Host mode for faster lookups

 

My Network settings are attached, for reference. I have two nw cards but I am only using one.

 

Thanks!

Tony

Screen_Shot_2015-12-31_at_09_35_12.png.70b29dc50a6fee554a1efe04d57cca09.png

Link to comment

Hey spants,

 

I'm getting the same error fwiw, and my network settings are the same as yours.  Trying to install manually results in the same error, although running as host does work.

 

I wonder whether it's a plugin causing the issue rather than another docker container, but not sure which one yet.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.