spants

Thanks for the feedback!. I threw this template together in 2017 for a project that needed it at the time.... I havent really looked at it since. 1) This is an easy change to make 2) I thought that the v2 template already uses this? Let me know!

They must have had a tidy up!. Will do. Note that I dont use this anymore as I am running Adguard on my Opnsense firewall instead.

try chmod -R 777 /mnt/appdata/nodered or what every you have called it..... The more recent versions of unraid restrict the permissions a bit. Note that this is a security gotcha as it enables execute too - you could also just change the r/w for all and leave execute alone

how did you get around the permissions/ownership of the downloaded files so that radaar can import?

Thanks - Still working on it in the background 🙂 I use Proxmox as a Hypervisor with unRaid as a VM. I was in the process of removing encryption from my drives for the possibility of moving the drives to a MergerFS and Snapraid system on the host instead of unRaid (or possibly ZFS).

I had the same problems - I spent hours trying to fix and ordered a replacement drive. It is the potential loss of online data and TIME that caused me headaches.

Please check with the owner of node-red-contrib-power-monitor as it may be an issue there (npm/node version?). The template just loads the official nodered docker so there is nothing that I can do to fix it.

There is a "transporter" option for saving configs

I havent pulled any templates! My pihole template pulls the offical pihole docker and I have not modified that in any way. Unraid 6.10+ caused some issues with permissions with docker data files that the template doesnt change because I am not modifying the docker. Work arounds have been discussed previously. Note that I have moved to Proxmox, with unRaid as a VM and Adguard as an LXC, so I dont use pihole anymore. Hopefully existing users can support if I can't. For people with 'port already in use' errors - you need to give pihole its own IP address on a custom/bridged network as it cannot share the same address as unraid.

all looks good. (I am also looking at another solution for MQTT with a webui for users and authorisations-will post here after finishing my tests)

Hi all, As you are discovering, this docker is quite old and needs to be updated. If you can bear with me, please try the manual steps to get a later version of MQTT and solve permissions problems. Please follow these steps and stop any existing MQTT container. I am using a directory called "/mnt/user/appdata/mos/" for my config - change if you wish. 1) In a shell on unRaid, create the mosquitto directories mkdir -p /mnt/user/appdata/mos/config mkdir -p /mnt/user/appdata/mos/data mkdir -p /mnt/user/appdata/mos/log 2) create a configuration file nano /mnt/user/appdata/mos/config/mosquitto.conf with the following text persistence true persistence_location /mosquitto/data/ user mosquitto # Listen on all interfaces listener 1883 #Allow connection without authentication allow_anonymous true log_dest file /mosquitto/log/mosquitto.log log_dest stdout 3) Set the ownership of the directories to nobody:users chown -R nobody:users /mnt/user/appdata/mos 4) download and start the docker (called mqttnew for testing) sudo docker run -itd -p 1883:1883 -e PUID=1000 -e PGID=1000 \ --name=mqttnew \ --net=bridge \ -v /mnt/user/appdata/mos/config:/mosquitto/config \ -v /mnt/user/appdata/mos/data:/mosquitto/data \ -v /mnt/user/appdata/mos/log:/mosquitto/log \ eclipse-mosquitto If you want to add users and disable anonomous logins: 5) On the running docker icon, right click and choose CONSOLE and type: (replace <username>) mosquitto_passwd -c /mosquitto/config/credentials <username> 6) stop the docker 7) edit the /mnt/user/appdata/mos/config/mosquitto.conf file nano /mnt/user/appdata/mos/config/mosquitto.conf to look like: persistence true persistence_location /mosquitto/data/ user mosquitto # Listen on all interfaces listener 1883 #Allow connection without authentication allow_anonymous false log_dest file /mosquitto/log/mosquitto.log log_dest stdout password_file /mosquitto/config/credentials 8 - test and let me know how you get on. I will template this if it works for all.

I have now virtualised my unraid in proxmox. I passed through the sas falcon controller (ibm something flashed to IT mode), GTX 1060 for Emby transcoding, a couple of usb devices including the unraid usb stick, enocean usb and usb zigbee controller. I created a BOND network interface and used this as an E1000 network card. The paravirtualised network card dropped packets (as detailed before). It is all working great! On the same proxmox - Opnsense (in is dedicated network port, out is network BOND), MQTT LXC container, Home Assistant Virtual machine, NodeRed LXC for testing, and Zorin VM. Server is a Asus Strix x570-F board, AMD 5900 with 64GB ram.

interested to see how this goes. I have just virtualised unraid on proxmox to also play with lxc alongside....

Yes you could do that. I had to CHMOD my directory as the persistence db wasnt saving. Just rename it after stopping the docker.... and then restart. You may have to set the permissions on the new directory.

if you shell on to unraid can you see the directory? can you use the filemanager plugin to see if the files are there? You might have to CHMOD -r 777 (or just RW privs) on the mqtt app directory (beware of the consequences!) as unraid changed the permissions/owners for appdata a while back Let me know how you get on. I use 6.10 with lots of mqtt clients with this. I should really get around to looking at building a more modern mqtt broker and template....

Strange! What version of unraid are you using?

If you use the "by-id" serial identification this won't happen as it uses the identity of the printer. If you use ttyACM0 or ttyUSB1 methods, these can change

I have no idea - it should work! (sorry, I know that isn't a proper answer. I will reinstall my setup and check in a couple of days)

You probably could by adding extra keys, but you can also spin up another docker (use one for each printer)-that is what I did!

Bridge network gives you that option

best to use the /dev/serial/by-id/ method rather than usbtty as the port may change if you plug the printers in differently

just create a strong user/password and use port forwarding from your router to the mqtt port?.

yes, I see a few people on the internet see the same problem. I wonder if adding --user="nobody:users" to extra parameters would make a difference?. Otherwise you may have to chmod the data directory = https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence

Its not my docker, but did you fix it? I use the zigbee2mqtt docker as well so I will try and help

You can change your own: chgange the repository field to nodered/node-red:2.1.6-16