Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


spants last won the day on August 29 2021

spants had the most liked content!

1 Follower


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

spants's Achievements


Enthusiast (6/14)



  1. what does /data/.npm/_logs/2023-08-31T12_10_04_289Z-debug-0.log contain? can you ping from inside nodered container?
  2. This is a very useful site
  3. I use unRaid as a vm in Proxmox now. unRaid has all my docker technology covered. Proxmox has all my VMs (HomeAssitant, opnsense) covered Proxmox is also used for LXC - primarily Tailscale
  4. Strange error - one drive is not automounting and the manual button does not make it mount. Latest 6.12.3 unraid and UA plugin. Logs show my first drive (external LUKS usb) mounting successfully, the second (internal sata LUKS) shows an error. Jul 18 10:50:46 Tower unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/TowerBackup'... Jul 18 10:50:46 Tower unassigned.devices: Using luksKeyfile to open the 'crypto_LUKS' device. Jul 18 10:50:49 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/mapper/TowerBackup' '/mnt/disks/TowerBackup' Jul 18 10:50:49 Tower kernel: XFS (dm-4): Mounting V5 Filesystem Jul 18 10:50:50 Tower kernel: XFS (dm-4): Ending clean mount Jul 18 10:50:50 Tower unassigned.devices: Successfully mounted 'TowerBackup' on '/mnt/disks/TowerBackup'. Jul 18 10:50:50 Tower unassigned.devices: Device '/dev/sda1' is not set to be shared. Jul 18 10:50:54 Tower unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks/urbackup'... Jul 18 10:50:54 Tower unassigned.devices: Partition 'urbackup' is already mounted. Jul 18 10:50:54 Tower unassigned.devices: Partition 'urbackup' cannot be mounted. urbackup is not mounted - it doesnt show under /mnt/disks/ *** solved *** It seems that the partition/mount point cannot now be the same name as the disk drive
  5. Did you fix it? Looks like a Alexa credentials issue but that shouldnt stop NR from loading. Depending on the age of your template - do you have the safe mode option? If not, add a variable to the docker tempate NODE_RED_ENABLE_SAFE_MODE and set it to true. You can then startup NR without it starting the flows.
  6. 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!
  7. 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.
  8. 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
  9. how did you get around the permissions/ownership of the downloaded files so that radaar can import?
  10. 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).
  11. 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.
  12. 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.
  13. There is a "transporter" option for saving configs
  14. 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.
  15. 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)