spants

This was a very old (> 4years) template that I put together as one didnt exist. I have marked it as depreciated as there are many others now

well spotted - I dont run any install scripts in the template as it just uses the official docker image. With unraid, you may have to do these tweaks!....

Hi all I created this template many years ago as a wrapper for the offical pihole docker and I am not surpised that a number of items may not work correctly. I changed my setup to use opnsense/adguard hence I have not seen the problems myself as I dont use it. Regarding the logs, try creating a log directory in the pihole appdata directory and add the following path: (run the docker for a while and see if the logs are written to the host instead of the container)

Thank you - solves the SpaceInvader zfs clone script issue !

Upgrade for me was easy and everything started to work ok. I use ZFS pools so being able to remove the last array disk was nice. A couple of people have mentioned the SSL library issue - it also affects @SpaceInvaderOne's scripts for snapshotting:- Starting ZFS replication using syncoid with mode: strict-mirror Sending incremental nvme/appdata@syncoid_Tower_2024-06-28:01:00:08-GMT01:00 ... syncoid_Tower_2024-06-30:21:13:37-GMT01:00 (~ 62.8 MB): mbuffer: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory warning: cannot send 'nvme/appdata@syncoid_Tower_2024-06-30:21:13:37-GMT01:00': Broken pipe cannot receive: failed to read from stream

Hi! My office is in bits at the moment due to a m,ove, so I dont have access to my printers. It may be a month or so.....

I had something similar that bugged me for months. I had moved from standalone unraid to a virtualised system and thought that was the cause and soent ages trying to fix it. The actual problem was a failing ssd that I was using as a cache drive that was not giving any errors, just running really slow for some sectors.

have you tried setting the serverIP variable to the PiHole server IP (192.168.1.20)?

using the built-in filemanager in unraid, try setting the permissions for the pihole file/directories to rw to all groups/users. (I no longer use it, so I cant give you the filenames unfortunately)

Glad you sorted it. Support is by the users. I just created the first template that wrapped the official docker. There are other templates available. I don't use it. I use ubound on opnsense under proxmox.

what does /data/.npm/_logs/2023-08-31T12_10_04_289Z-debug-0.log contain? can you ping https://registry.npmjs.org from inside nodered container?

This is a very useful site https://ikrima.dev/dev-notes/homelab/zfs-for-dummies/

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

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

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.