rernst

i'n not sure which of the above potential causes, is causing the issue; i guess the 'terminal window closing' or connection dropping is the most plausible one. I'll follow this advice and see if it occurs again in the future: 'Use a tool like tmux or screen, or run the command with nohup. This prevents the process from dying if your terminal window closes or your connection drops.' Anyway, I noticed in the log that was created the second time i ran the script (and written to the external disk) , the script continued copying where the first run got stuck. So i ran the script a third time (without any modifications), and now it did copied the remaining files without throwing any rsync errors. Maybe now it doesn't have to copy that much any more in future rsyncs, the errors will not pop up anyway even when using the current unmodified script.

This is from the sys log when i attempted to run the script a second time this morning. Not sure if the last line has anything to do with it: Jan 14 09:43:08 Server unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/External_HDD_1TB'... Jan 14 09:43:08 Server unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdf1' '/mnt/disks/External_HDD_1TB' Jan 14 09:43:09 Server ntfs-3g[3607088]: Version 2022.10.3 integrated FUSE 27 Jan 14 09:43:09 Server ntfs-3g[3607088]: Mounted /dev/sdf1 (Read-Write, label "External HDD 1TB", NTFS 3.1) Jan 14 09:43:09 Server ntfs-3g[3607088]: Cmdline options: rw,relatime,nodev,nosuid,nls=utf8,umask=000 Jan 14 09:43:09 Server ntfs-3g[3607088]: Mount options: nodev,nosuid,nls=utf8,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdf1,blkdev,blksize=4096 Jan 14 09:43:09 Server ntfs-3g[3607088]: Global ownership and permissions enforced, configuration type 1 Jan 14 09:43:09 Server unassigned.devices: Successfully mounted '/dev/sdf1' on '/mnt/disks/External_HDD_1TB'. Jan 14 09:43:09 Server unassigned.devices: Device '/dev/sdf1' is not set to be shared. Jan 14 09:43:39 Server emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/Backup to External HDD/script Jan 14 09:45:42 Server monitor_nchan: Stop running nchan processes

Hi, i have written a backup script to backup at a regular interval, using the User Scripts plugin, selected folders on my shares to an external HDD conencted via USB to my unraid server; this external HDD is mounted as Unassigned Device. When i manually run the script, it seems to be working initially as it is copying using rsync, but the copying (i.e. rsync) seems to get stuck at a certain point when copying my photos; i see following errors in the log that is written to the external hard drive: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(716) [sender=3.4.1] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(519) [generator=3.4.1] files are being copied, i cna see them on my external hard drive, but just until the point that the above rsync errors are thrown. I don't understand these rsync errors, can someone explain what is happening and how to solve them please? Below my script in case anyone is interested: #!/bin/bash SOURCE_BASE="/mnt/user" DEST_BASE="/mnt/disks/External_HDD_1TB" ERROR_FOUND=0 # --- MOUNTING --- # Check if already mounted; if not, try to mount it if [ ! -d "$DEST_BASE" ]; then echo "Attempting to mount $DEST_BASE ..." /usr/local/sbin/rc.unassigned mount "$DEST_BASE" sleep 5 # Give it a few seconds to initialize fi # Now we define log paths after the mount attempt LOG_DIR="$DEST_BASE/logs" DATE=$(date +%Y-%m-%d_%H-%M) LOG_FILE="$LOG_DIR/backup_$DATE.log" # --- EXECUTION --- if [ -d "$DEST_BASE" ]; then #send notification in dashboard /usr/local/emhttp/webGui/scripts/notify -i normal -s "Backup to External HDD" -d "Backup STARTED" # Create log directory if it doesn't exist mkdir -p "$LOG_DIR" echo "--- Backup Log for $DATE ---" > "$LOG_FILE" # Run rsync #photo/Albums echo "Syncing photo/Albums..." >> "$LOG_FILE" mkdir -p "$DEST_BASE/data/media/photo/Albums/" rsync -avX --delete --stats "$SOURCE_BASE/data/media/photo/Albums/" "$DEST_BASE/data/media/photo/Albums/" >> "$LOG_FILE" 2>&1 if [ $? -eq 0 ]; then echo "photo/Albums sync successful." >> "$LOG_FILE" else echo "ERROR: photo/Albums sync failed!" >> "$LOG_FILE" ERROR_FOUND=1 fi echo "----------------------------" >> "$LOG_FILE" #photo/Immich/library # --- 1. STOP CONTAINERS --- echo "Stopping Immich for safety..." >> "$LOG_FILE" docker stop immich sleep 5 # --- 2. RUN THE SYNC --- echo "Syncing photo/Immich/library..." >> "$LOG_FILE" mkdir -p "$DEST_BASE/data/media/photo/Immich/library/" rsync -avX --delete --stats "$SOURCE_BASE/data/media/photo/Immich/library/" "$DEST_BASE/data/media/photo/Immich/library/" >> "$LOG_FILE" 2>&1 if [ $? -eq 0 ]; then echo "photo/Immich/library sync successful." >> "$LOG_FILE" else echo "ERROR: photo/Immich/library sync failed!" >> "$LOG_FILE" ERROR_FOUND=1 fi echo "----------------------------" >> "$LOG_FILE" # --- 3. START CONTAINERS --- echo "Restarting Immich..." >> "$LOG_FILE" docker start immich #music echo "Syncing music..." >> "$LOG_FILE" mkdir -p "$DEST_BASE/data/media/music/" rsync -avX --delete --stats "$SOURCE_BASE/data/media/music/" "$DEST_BASE/data/media/music/" >> "$LOG_FILE" 2>&1 if [ $? -eq 0 ]; then echo "music sync successful." >> "$LOG_FILE" else echo "ERROR: music sync failed!" >> "$LOG_FILE" ERROR_FOUND=1 fi echo "----------------------------" >> "$LOG_FILE" #documents echo "Syncing documents..." >> "$LOG_FILE" mkdir -p "$DEST_BASE/data/documents/" rsync -avX --delete --stats "$SOURCE_BASE/data/documents/" "$DEST_BASE/data/documents/" >> "$LOG_FILE" 2>&1 if [ $? -eq 0 ]; then echo "documents sync successful." >> "$LOG_FILE" else echo "ERROR: documents sync failed!" >> "$LOG_FILE" ERROR_FOUND=1 fi echo "----------------------------" >> "$LOG_FILE" #backup echo "Syncing backup..." >> "$LOG_FILE" mkdir -p "$DEST_BASE/backup/" rsync -avX --delete --stats "$SOURCE_BASE/backup/" "$DEST_BASE/backup/" >> "$LOG_FILE" 2>&1 if [ $? -eq 0 ]; then echo "backup sync successful." >> "$LOG_FILE" else echo "ERROR: backup sync failed!" >> "$LOG_FILE" ERROR_FOUND=1 fi echo "----------------------------" >> "$LOG_FILE" # --- UNMOUNT DRIVE --- echo "Unmounting $DEST_BASE..." >> "$LOG_FILE" sync # Flush any remaining data to the disk hardware /usr/local/sbin/rc.unassigned umount "$DEST_BASE" # --- FINAL NOTIFICATION --- if [ "$ERROR_FOUND" == "1" ]; then #send notification in dashboard /usr/local/emhttp/webGui/scripts/notify -i alert -s "Backup to $DEST_BASE" -d "Backup finished with ERRORS. Check $LOG_FILE" else #send notification in dashboard /usr/local/emhttp/webGui/scripts/notify -i normal -s "Backup to $DEST_BASE" -d "All folders backed up successfully. Log saved." fi else #send notification in dashboard /usr/local/emhttp/webGui/scripts/notify -i alert -s "Backup to $DEST_BASE" -d "Backup FAILED: Destination drive not mounted. Log could not be created." exit 1 fi

turned out that the URL structure for my dahua camera needed to be different than was suggested by default by frigate; i had to use: rtsp://admin:password@ip_address:554/cam/realmonitor?channel=1&subtype=0 For anyone interested in the full solution / steps by steps to have my cameras work with frigate in a dual NIC setup, see solution

I think i managed to have the frigate container have access to both eth0 and eth1 by following instructions from gemini which told me to define a macvlan for br1 (eth1). i did this by puting in the cli: docker network create -d macvlan --subnet=10.1.1.0/24 --gateway=10.1.1.1 -o parent=br1 cam_network then i added the following to the post arguments in the frigate docker container settings: && docker network connect cam_network frigate Now frigate seems to have an IP address both on the bridge network and the cam_network. In order to be able to pign my camera, i first had to install the ping utility in the frigate container, as it seemed to not have it by default, i did so by following these instructions i.e. putting following commands in the CLI: docker container exec -it frigate bash apt update apt install iputils-ping exit then pinging the camera from frigate via the cli gave the following result: the errors in frigate Error opening input file rtsp://:@10.1.1.66:554/rtsp. ERROR : Error opening input files: Server returned 404 Not Found still persist though... Anyone has an idea what i might strill be doing wrong?

Hi, i want to move my Dahua home security cameras from recording to the Dahua NVR to the Unraid Frigate Docker Container. I have installed a second NIC in the server and created an isolated camera subnet 10.1.1.1/24. I am able to ping the cameras from the Unraid main page CLI, but fail to connect to them from Frigate . Below an overview of the setup: i see following errors in the system log: Error opening input file rtsp://:@10.1.1.66:554/rtsp. ERROR : Error opening input files: Server returned 404 Not Found Attached you can find my frigat system logs. the Frigate container seems to be assigned the IP address of my server on the main VLAN, and hence doesn't seem to have an IP address on the camera subnet: Below my docker settings: and my frigate container settings: My frigate container network type is set to host instead of bridge in order to have access to both eth0 and eth1, maybe i need to also configure something else? Or is this not the right approach and should I create a MACVlan or IPVlan? Not sure how to do this though so if someone could provide some guidance please? I also noticed that in the network type options br1 is not shown as an option which leads me to believe that eth1 (br1) is not passed to docker or its containers. is this observation correct? Can someone guide me please what i should do to have docker, and in partical the frigate container, access to both network interfaces? Also can someone explain me please how i can ping from inside the docker / container environment? frigate-logs (1).txt

Update, i have internet connection back by specifying the eth1 static IP address as 10.1.1.0 instead of 10.1.1.1. This eth1 is for a camera subnet which i am still trying to set up, i was suggested by someone on github where i asked help for setting up frigate, that i probably should set my eth1 network interface to 10.1.1.1 instead of 10.1.1.0. But i guess this is not the right way then.

When i ping my router from the server CLI, i am unable to reach it; it seems that he is pinging from the wrong network interface, i.e. eth1, though: eth1 network settings: eth0 network settings: Interface rules: Routing table: how can i fix this?

Hi, my unraid server seems to have lost all internet connectivity after a graceful reboot. i see following two errors in the logs: Dec 30 16:47:18 EY-NAS-Server http_get_contents: Curl error 28: Resolving timed out after 15000 milliseconds. Requested url: 'http://www.msftncsi.com/ncsi.txt' Dec 30 16:47:27 EY-NAS-Server ntpd[2423]: error resolving pool 0.be.pool.ntp.org: Name or service not known (-2) attached my diagnostics file. Connecting over LAN is no issue. Can anyone help me solve this problem please? ey-nas-server-diagnostics-20251230-1742.zip

I got this problem solved with assistance from the Home Assistant Community; for anyone interested in the solution see: solution

With help from the Home Assistant Community i got to the point that: i created a DNS A record for ha.mydomain.com pointing to my unraid server's Tailscale IP. (hence same as for server.mydomain.com). In NGINXProxymanager I created a proxy host pointing to http:[myhomeassistanyellowIP]:8123 , i also created a SSL certificate. however when i surf to ha.mydomain.com, i do not land on the home assistant landing page, but on my unraid's server landing page. Should i somehow use the IP address of the NGINXProxyManager container instead of my server, or why am i not redirected?

Hi, I have attempted to setup secure remote access over https using tailscale (plugin, not docker app) in combination with NginxProxyManager (docker app) and a custom domain following the guide from spaceinvader one: 3 Different Ways to Connect to Unraid over HTTPS . It is working in the sense that i can reach my server over the internet (hence when not connected to my home LAN); of course with tailscale installed on the device that i use to make the connection. However, the connection remains being shown as 'not secure' and i'm not sure what i did wrong. Below some screenshots of my configuration: Containers: NPM container settings: Management access settings: Nginx Proxy Manager settings: Unifi USG PRO 4 port forwarding rules:

Hi, i need help to setup remote acces to home assistant yellow via NginxProxyManager running in docker on an unraid server located in a different VLAN. i have set up remote access to my unraid server, located on my main VLAN, over https using the tailscale plugin and NginxProxyManager (docker) app with a custom (sub)domain server.mydomain.com following this tutorial from spaceinvader one: 3 Different Ways to Connect to Unraid over HTTPS . I applied the third method and it is working in the sense that I can reach the server using my custom domain, but for some reason the connection still isn't secure. (Separate issue for which I will create a different topic) Now i want to achieve the same for my home assistance instance, located on the IOT VLAN, running on a home assistant yellow with (sub)domain ha.mydomain.com. I have tailscale set up on Home Assistant, so next is to configure NGINX. I guess that next in the webgui of the NginxProxyManager app running i ndocker on my unraid server, i need to create a host and SSL certificate for ha.mydomain.com pointing to my home assistant yellow IP. However my Home Assistant Yellow is located on the IOT VLAN (VLAN40), while my unraid server is located on my main VLAN (VLAN60), so this won't work out of the box. How should i configure the NGINX docker app in unraid and which port forwarding should i do in my Unifi Router (USG PRO 4) to allow NGINX to 'see' my home assitant yellow on the different VLAN. FYI, below are currently my configuration settings for the NginxProxyManager container.

I just found out that for the external libraries i just need to write /libraries as the path. the /libraries corresponds to the oath i have defined during the container setup, i.e. /mnt/user/data/media/photo/Albums For the uploads from the Immich smartphone app i found out that seperate folders for myself and my wife are automatically created in the /mnt/user/data/media/photo/Immich/ directory that i defined during contianer setup, the naming and structure is however not very convenient and hence difficult to navigate. i'll have to dig some more to find out how i can get this sorted out, but at least everything is up and running now

hello, I need support with setting up Immich, specifically with 1) configuring external libraries and 2) having seperate folders per user for photos uploaded from a phone. i have installed the Immich Community App (cuda version as i have an nvidia GPU) and the postgreSQL from spaceinvader My data share is organised per Unraid/Jellyfin Trash folder structure, i.e. a single data share with nested folders for organization; i have a photo folder in the following directory /mnt/user/data/media/photo/ where i would like to have both my organised photo albums as the the photos backed up via the immach apps on the phones of my wife and myself. I am unable to get this configured and working... Overview of what i want to achieve: have my album photos (i.e. photos sorted in different folders) imported in Immich as an external library. i keep my album photos in /mnt/user/data/media/photo/Albums have the photos uploaded (i.e. backuped) by the immich phone app in a dedicated folder for each family member. (for now that would be a folder for me and another folder for my wife) i would like to have two folders in the immich folder, one for my wifes phone photo backup uploads, and one for mine: /mnt/user/data/media/photo/Immich/MYNAME /mnt/user/data/media/photo/Immich/MYWIFESNAME and what should i put here as external library path? when i put the directory of the albums folder i receive an error: all help is appreciated.