livingonline8

ok here is the sys log for what's going on as soon as I start Adguard Home docker, I timed it at 13:17 the unraid server had this IP 192.168.1.250 and as soon I started Adguard Home docker, my server switched IP to 192.168.1.251 few minutes later it is 192.168.1.252...then few more minutes and it is 192.168.1.249 Please check the new attached diagnostics May 9 13:17:47 Tower kernel: eth0: renamed from veth846d0ed May 9 13:17:47 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:47 Tower kernel: device br0 entered promiscuous mode May 9 13:17:48 Tower dhcpcd[4443]: br0: 02:01:4e:36:f1:43(02:01:4e:36:f1:43) claims 192.168.1.250 May 9 13:17:49 Tower dhcpcd[4443]: br0: 02:01:4e:36:f1:43(02:01:4e:36:f1:43) claims 192.168.1.250 May 9 13:17:49 Tower dhcpcd[4443]: br0: 10 second defence failed for 192.168.1.250 May 9 13:17:49 Tower dhcpcd[4443]: br0: deleting route to 192.168.1.0/24 May 9 13:17:49 Tower dhcpcd[4443]: br0: deleting default route via 192.168.1.1 May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] May 9 13:17:49 Tower rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2002.0 try https://www.rsyslog.com/e/2354 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), next retry is Mon May 9 13:18:19 2022, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.2002.0 try https://www.rsyslog.com/e/2007 ] May 9 13:17:49 Tower dhcpcd[4443]: br0: rebinding lease of 192.168.1.250 May 9 13:17:49 Tower dhcpcd[4443]: br0: probing address 192.168.1.250/24 May 9 13:17:50 Tower dhcpcd[4443]: br0: 02:01:4e:36:f1:43(02:01:4e:36:f1:43) claims 192.168.1.250 May 9 13:17:50 Tower dhcpcd[4443]: br0: DAD detected 192.168.1.250 May 9 13:17:50 Tower ntpd[2439]: Deleting interface #46 br0, 192.168.1.250#123, interface stats: received=27, sent=27, dropped=0, active_time=187 secs May 9 13:17:50 Tower ntpd[2439]: 216.239.35.0 local addr 192.168.1.250 -> <null> May 9 13:17:50 Tower ntpd[2439]: 216.239.35.4 local addr 192.168.1.250 -> <null> May 9 13:17:50 Tower ntpd[2439]: 216.239.35.8 local addr 192.168.1.250 -> <null> May 9 13:17:50 Tower ntpd[2439]: 216.239.35.12 local addr 192.168.1.250 -> <null> May 9 13:17:51 Tower dhcpcd[4443]: br0: soliciting a DHCP lease May 9 13:17:52 Tower dhcpcd[4443]: br0: offered 192.168.1.251 from 192.168.1.1 May 9 13:17:52 Tower dhcpcd[4443]: br0: probing address 192.168.1.251/24 May 9 13:17:57 Tower dhcpcd[4443]: br0: leased 192.168.1.251 for 28800 seconds May 9 13:17:57 Tower dhcpcd[4443]: br0: adding route to 192.168.1.0/24 May 9 13:17:57 Tower dhcpcd[4443]: br0: adding default route via 192.168.1.1 May 9 13:17:59 Tower ntpd[2439]: Listen normally on 47 br0 192.168.1.251:123 May 9 13:17:59 Tower ntpd[2439]: new interface(s) found: waking up resolver tower-diagnostics-20220509-1334.zip

Also I noticed the server is acting funny getting a new IP every few minutes as soon as I start the Pi-hole or Adguard Home dockers! although in my previous ASUS router this was not the case

My server does have two eth ports but I am connected to router using one only. Can you tell me how can I stop bonding on the unpaid server since I am not using it I think it is active in my settings for some reason. Please check my screenshot that I attached

@MAM59 also note, I lose access to my server even if I set it up with a static IP address from my router I checked the diagnostic file and it does show errors about claiming IP but defense failed!! whatever that means

Thank you for your reply I just checked the DHCP Lease Time on my router and it is set to 28800 seconds that is 8 hours! this setting is fine, it must be something else that makes my router change the unraid IP server every few minutes

I am really lost here... I tried everything I can think of Expected behaviour: Start the unraid server, it gets an IP address from USG router, access your unraid server at anytime from GUI and shares. Current behaviour: Start the unraid server, it gets an IP address from USG router(i.e. 192.168.1.88), I can access the GUI and shares, Thenfew minutes after starting my unraid server, I cannot see the shares in my network tab on my Macbook pro and the GUI is unreachable! checking the USG router through the controller, I find out the unraid IP was changed to (i.e. 192.168.1.92). Now, I can access the unraid GUI again using that ip address, few minutes after that, I lose access to unraid GUI, Checking USG router, I find out the unraid IP was changed to new IP address (i.e. 192.168.1.74) Troubleshooting steps: Rebooted the network and server multiple time Assigned static IP address ( I still lose access to GUI although the unraid server IP did not change because I made it static) Stopped dockers checked access management for ports checked network settings on unraid @bonienl @limetech I am completely lost in here, Please I would really appreciate the help

Hello everyone, I have an unraid server running the latest stable version. My router died so I swapped it with a Ubiquiti USG router that I was using in the past just fine. The problem is after turning on the server, I can access the GUI and shares in the first couple of minutes and then the server IP gets changed randomly every few minutes!! So, I decided to use a static IP, Same issue with one minor difference, still I can access the GUI and shares in the first couple of minutes but then I cannot access anything although the IP does not change!! (I check if the server IP changed in the router) This Unifi USG router was working fine with this server a couple years ago. But, now that my ASUS router died and wanted to g back and use USG, all I did, connected it, updated it and it has this issue with randomly changing my server IP. all my other devices are working fine. is the problem in my server? is it my router? I would really appreciate the help, I have attached the diagnostics file tower-diagnostics-20220509-0558.zip

Ok, I fixed that by removing Nginx docker and reinstall it Everything is working perfectly now... Thanks

Ok that works 😍 But now, Nginx Proxy Manager does not work and when I looked into the logs, I saw the following: [nginx] starting... nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

guys, I really need some help here 😅

I have the latest version of unraid and I have Nginx proxy manager working perfectly well... I can access radarr, sonarr and Bitwarden outside my network. Now, I installed unraid.net plugin (beta) and I love how useful it is but when I want to access my server outside my network I have to set Use SSL/TLS to AUTO... that breaks Nginx and I cannot access radarr, sonarr and Bitwarden!! any ideas? is there something I should be doing? Also, I have another question both Nginx proxy manager and unraid.net plugin (beta) use 443... does that have anything to do with this issue?

@DZMM I am posting all the details here to make it easier for you to help me this is my mount script...it used to work perfectly but now I am getting an error The current mounting script: #!/bin/bash ####### Check if script is already running ########## if [[ -f "/mnt/user/appdata/other/rclone/rclone_mount_running" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: Exiting script already running." exit else touch /mnt/user/appdata/other/rclone/rclone_mount_running fi ####### End Check if script already running ########## ####### Start rclone google mount ########## # check if google mount already created if [[ -f "/mnt/user/mount_rclone/google_vfs/mountcheck" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: Check rclone vfs already mounted." else echo "$(date "+%d.%m.%Y %T") INFO: mounting rclone vfs." # create directories for rclone mount and unionfs mount mkdir -p /mnt/user/mount_rclone/google_vfs mkdir -p /mnt/user/mount_unionfs/google_vfs mkdir -p /mnt/user/rclone_upload/google_vfs rclone mount --allow-other --buffer-size 256M --dir-cache-time 72h --drive-chunk-size 512M --fast-list --log-level INFO --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off media_vfs: /mnt/user/mount_rclone/google_vfs & # check if mount successful # slight pause to give mount time to finalise sleep 5 if [[ -f "/mnt/user/mount_rclone/google_vfs/mountcheck" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: Check rclone google vfs mount success." else echo "$(date "+%d.%m.%Y %T") CRITICAL: rclone google vfs mount failed - please check for problems." rm /mnt/user/appdata/other/rclone/rclone_mount_running exit fi fi ####### End rclone google mount ########## ####### Start unionfs mount ########## if [[ -f "/mnt/user/mount_unionfs/google_vfs/mountcheck" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: Check successful, unionfs already mounted." else unionfs -o cow,allow_other,direct_io,auto_cache,sync_read /mnt/user/rclone_upload/google_vfs=RW:/mnt/user/mount_rclone/google_vfs=RO /mnt/user/mount_unionfs/google_vfs if [[ -f "/mnt/user/mount_unionfs/google_vfs/mountcheck" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: Check successful, unionfs mounted." else echo "$(date "+%d.%m.%Y %T") CRITICAL: unionfs Remount failed." rm /mnt/user/appdata/other/rclone/rclone_mount_running exit fi fi ####### End Mount unionfs ########## ############### starting dockers that need unionfs mount ###################### # only start dockers once if [[ -f "/mnt/user/appdata/other/rclone/dockers_started" ]]; then echo "$(date "+%d.%m.%Y %T") INFO: dockers already started" else touch /mnt/user/appdata/other/rclone/dockers_started echo "$(date "+%d.%m.%Y %T") INFO: Starting dockers." docker start binhex-emby docker start binhex-sabnzbd docker start binhex-radarr docker start binhex-sonarr fi ############### end dockers that need unionfs mount ###################### exit Then all of sudden, after 2 years of working perfectly...I started getting the following error message: 27.02.2021 15:00:01 INFO: mounting rclone vfs. 2021/02/27 15:00:03 Fatal error: Directory is not empty: /mnt/user/mount_rclone/google_vfs If you want to mount it anyway use: --allow-non-empty option 27.02.2021 15:00:06 CRITICAL: rclone google vfs mount failed - please check for problems. Script Finished Feb 27, 2021 15:00.06 Full logs for this script are available at /tmp/user.scripts/tmpScripts/rclone_unionfs_mount/log.txt so as suggested in the error message I added "--allow-non-empty" and the mounting script looks like this: rclone mount --allow-non-empty --allow-other --buffer-size 256M --dir-cache-time 72h --drive-chunk-size 512M --fast-list --log-level INFO --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off media_vfs: /mnt/user/mount_rclone/google_vfs & Now, I am getting this error: 27.02.2021 15:07:21 INFO: mounting rclone vfs. 2021/02/27 15:07:22 mount helper error: fusermount: unknown option 'nonempty' 2021/02/27 15:07:22 Fatal error: failed to mount FUSE fs: fusermount: exit status 1 27.02.2021 15:07:26 CRITICAL: rclone google vfs mount failed - please check for problems. Script Finished Feb 27, 2021 15:07.26 Full logs for this script are available at /tmp/user.scripts/tmpScripts/rclone_unionfs_mount/log.txt Many people tell me stop trying to mount to non-empty folder but I cannot... first of all, this was working for more than 2 years so why it stopped all of a sudden " I just want to understand " the main reason I have to mount to non-empty folder is because I am combining two folders of my media, one on google drive and the other on my unraid....they are both not empty and I have to mount to my non empty media folder

Thank you for your patience with me... please forgive me but I am not tech guru... I bet you are 😊 it is true that I was told not to mount to a non-empty folder but my setup was working fine for 2 years and I have to mount to non empty folder because I am combining “unionfs” media folder in google drive with media folder on my unbraid why did this break all of a sudden and again I really have no option but to mount to non-empty because all my media is there

@DZMM yeah I pasted everything in my subject in the rclone support but I couldn’t get an answer please click on the linked subject and you will find all the details you need

@Waseh please tell me where to look... I looked around the forums but I did not find an answer