July 24, 20214 yr Not really sure how to properly explain my situation here, however, I am still quite new to unRAID (despite having a server for a few years now, but always learning something new about it.) Anyways, my situation is a bit weird, I am trying to "Force Recheck" on one of my torrents on qBittorrent and it always results in an "Errored: An unexpected network error occurred." Now the files regarding this torrent is on my unRAID server and have noticed that when the error occurs, I can no longer remotely access my unRAID server as if it was disconnected. When I physically am on the server, I have noticed that for some reason the iP Address changes from the default 192.168 to 169. To combat this, I forced a static iP on both my router and the unRAID server itself, however, despite this seems to force a different iP now (I forgot what it changes too but I remember seeing this). If anyone can explain to me why this is happening, that would be greatly appreciated. Quite concerned that perhaps my unRAID server doesn't like the idea of being "thrashed" with data but I doubt this should even be an issue. As always to help give clarification with my issue, my diagnostics files are attached. I should also add that in the logs I think it shows me tinkering with bonding with the ethernet ports as I was testing if this was to happen (as I am moving and direct access would be impossible) that if this happens, could it fail over to another ethernet port, however, this is besides the point as I want to know why this is happening, and rather not have to go to this kind of route. perseverance1st-diagnostics-20210723-1305.zip Edited July 24, 20214 yr by JetRun15 Spelling error.
July 24, 20214 yr 22 hours ago, JetRun15 said: the iP Address changes from the default 192.168 to 169. This likely the DHCP problem, that means client can't renew the IP. 22 hours ago, JetRun15 said: despite this seems to force a different iP now (I forgot what it changes too but I remember seeing this). Not understand this, does Unraid IP not same as your config 192.168.1.142 22 hours ago, JetRun15 said: could it fail over to another ethernet port, however, this is besides the point as I want to know why this is happening, and rather not have to go to this kind of route. I don't think change to failover could help, this just make more hard for troubleshooting. You have 3 NIC, 2 Marvell ( eth0, eth1 ) and 1 Realtek ( eth2 ), suggest you move eth2 be eth0 and check Realtek does any different.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.