Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by spants

  1. 32 minutes ago, independence said:

    Hi all,


    when I´m trying to add a new adlist, there is an error:

    "While executing: attempt to write a readonly database"


    Do you already know what went wrong?




    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)

  2. 12 hours ago, TapRackBang said:



    Not sure what happened to the support here, but I just ran into this issue as well. The solution is to check Unraid -> Settings -> Docker and make sure "Host access to custom networks" is enabled.  Turning that on fixed it for me.

    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.

  3. 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


  4. On 6/6/2023 at 9:22 PM, OsoPolar said:

    HI @spants

    No idea been using for a few years it has just stopped opening what ever i try.
    Log as follows

    Cannot see anything that would stop it launching

    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.  

  5. 4 hours ago, own_rhino said:

    Thanks for the couchdb template! A couple of updates need to applied.


    1. From version 3.0 admin needs to be set. Otherwise the container doesn't start. Suggest adding variables for COUCHDB_USER and COUCHDB_PASSWORD to the template.

    2. More importantly the path to store data needs to be updated to:



    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!

  6. 1 minute ago, dreadu said:

    Low importance question here:
    I just noticed today (did work last week), that the link to the support forum seems to be wrong.


    Would you mind fixing it, when you change the template the next time?

    As said before: not high prio, but simply convenient 🙂


    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.


    • Thanks 1
  7. 3 minutes ago, danioj said:

    That makes sense. Loss of data availability and time to fix an issue is I agree something you would prefer to not have to deal with. Hope all is back up and running for you. 

    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).

  8. 2 hours ago, danioj said:

    I’ve stepped back from the forum in recent times but felt compelled to login and respond. 

    (Un)Raid is not for backup, it’s for for availability. If you are sensitive to “Loss” of data you should take appropriate steps to back it up based on your risk appetite for the unexpected. 


    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.

    • Like 1
    • Upvote 1
  9. 21 hours ago, goinsnoopin said:

    Update to post above:  


    I rolled my docker tag from latest to the 3.0.1 release of about a month ago and all functions as it is supposed to.

    The releases 3.0.1-1 (23 days ago) and 3.0.2 (16 days ago) I get the error above.   For now I am staying rolled back to 3.0.1 release.


    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.

  10. 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.

  11. 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 \


    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.



    • Thanks 2
    • Upvote 1
  12. 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.

  13. 12 minutes ago, live4soccer7 said:

    @spants Yes, they are all there. I have done everything suggested in the forum/thread here.




    I'm quite stumped on this. I'm thinking of nuking the whole thing. Deleting the image and the appdata folder for MQTT and installing again from scratch.


    I don't think there is much in the folder itself that would need to be saved. Without persistence, I think it would just be the mosquito.conf and the passwords.mqtt. I could manually open those with nano and copy the contents.



    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.

  14. 34 minutes ago, live4soccer7 said:

    After updating Unraid to 6.10 today, I was unable to start MQTT.


    1653129413: mosquitto version 1.4.8 (build date 2020-01-27 00:25:20+0000) starting
    1653129413: Config loaded from /config/mosquitto.conf.
    1653129413: Error: Unable to open pwfile "/config/passwords.mqtt".
    1653129413: Error opening password file "/config/passwords.mqtt".
    1653129593: Error: Unable to open log file /config/log/mosquitto.log for writing.
    1653129593: mosquitto version 1.4.8 (build date 2020-01-27 00:25:20+0000) starting
    1653129593: Config loaded from /config/mosquitto.conf.
    1653129593: Error: Unable to open pwfile "/config/passwords.mqtt".
    1653129593: Error opening password file "/config/passwords.mqtt".


    I have probably 25 other dockers that didn't have an issue. I've had this MQTT docker installed for years and never ran into this. I checked the GUI UID in the settings and they're proper. I did attempted to do a chown -R, but that was unsuccessful. I am also unable to access the mqtt folder through the Windows Network share on a remote machine on the network. I can access any other folders. I find this a bit strange, any ideas? I have a lot of things that run through MQTT, so it is quite important to get back up and running.


    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....




  15. 1 hour ago, abra5umente said:

    It seems as though every day this breaks for me - when I restart the docker after doing a backup, it moves all the keys around, resulting in the key for the USB ID of the printer being changed to the setting for camera, etc.

    I don't have a camera plugged in and I have removed those entries to allow it to start - it works fine until it restarts and then it dies, so I have to reinstall it again.


    Any workaround?


    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