So I was asked to post my diagnostics here since it might be a different issue than stated in https://forums.unraid.net/bug-reports/stable-releases/713-unraid-connect-error-r3898

Since upgrading from 7.1.2 to 7.1.3, I am having same error but instead of the error being solved when downgrading, it remains in 7.1.2.

Occasionally loosing connection (internet and wireguard tunnel) for several minutes (usually 20+ min). Connection comes back for some minutes and loosing it again afterwards.

I reverted with this method and not with the Unraid Connect Tool but I think it should do the same thing?!

After upgrading to 7.1.3:

unraid-diagnostics-20250606-1634.zip

After reverting to 7.1.2:

unraid-diagnostics-20250606-2023.zip

After reverting, on a trial basis, I changed the DNS in the Unraid Network Setting from router (192.168.0.1) to 1.1.1.1, but it didn't help.

#Edit: Just created a fresh new 7.1.2 version with USB Creater Tool onto my flash device and put my config folder in it. Still same issue with similar error:

unraid-diagnostics-20250606-2223.zip

Edited June 6, 20251 yr by shodeira

12 hours ago, shodeira said:

Just created a fresh new 7.1.2 version with USB Creater Tool onto my flash device and put my config folder in it. Still same issue with similar error:

Try the same but without restoring the config folder, this will confirm if it's a config issue, if it is, you can just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

I ended up reverting back to an old backup from 7.0.1 and it solved the issue. I first tried to narrow down the problem by running on bare minimum which worked. Then enabled docker and wireguard tunnel and suddenly the issue came back. Then deactivated wireguard but still no connection. Only stopping the array brought the connection back. At this point, reverting back was much easier for me.

Since others reported reverting back to 7.1.2 solved their issue, I am still clueless how the update could have an effect on my config folder. My next step would be to upgrade to 7.1.2 and see if the issue will stay away. If not, I maybe need to go the first route again piece by piece.

Edit: Additionally, on every reboot, there is the following line in the logs even with reverted version 7.0.1

ntpd[1443]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

I tried all NTP servers but nothing changed. Also ntpq -p always responds with

timed out, nothing received

***Request timed out

only synchronizing manually with ntpdate -u pool.ntp.org works.

Edited June 7, 20251 yr by shodeira

I finally managed to find the culprit of my internet connection issue! So my config in my fresh install 7.1.2 was the same as in 7.0.1 EXCEPT my docker.cfg from version 7.1.3 which I copied onto my fresh install 7.1.2. And this file was the problem for the connection issue. That is also why disabling docker or stopping the array brings the connection back....So I started again with a fresh 7.1.2 install and fresh config folder but leaving docker.cfg this time and voila. No issues anymore.

So comparing both docker.cfg, there are two entries that differ:

DOCKER_ALLOW_ACCESS="yes" was added in the 'broken' docker.cfg and DOCKER_AUTHORING_MODE="yes".

Disabling "Host access to custom networks" in Docker Settings removes DOCKER_ALLOW_ACCESS="yes" and solved the issue for me in 7.1.2. I can't tell if the solution works also for 7.1.3 but its worth a try.

Maybe this setting broke something in 7.1.2 and 7.1.3

I have encountered the same issue after the 7.1.3 update. How ever I have 2 servers, one upgraded fine the other produced this issue. I tried what I saw above but still had issue. A reboot would correct the issue but after about 30 min it would start happening again. Most network features just would work. I have rolled back to 7.1.2 for now and everything is fine. It has to be something specific on this server as the other is running 7.1.3 just fine. The only real difference between server is PLEX is on the server that is having issues with 7.1.3.

19 hours ago, eric.ruck said:

I have encountered the same issue after the 7.1.3 update. How ever I have 2 servers, one upgraded fine the other produced this issue. I tried what I saw above but still had issue. A reboot would correct the issue but after about 30 min it would start happening again. Most network features just would work. I have rolled back to 7.1.2 for now and everything is fine. It has to be something specific on this server as the other is running 7.1.3 just fine. The only real difference between server is PLEX is on the server that is having issues with 7.1.3.

That could be interesting. You might consider posting the diagnostics as well of both servers in here for the devs to help investigate the issue.

Edited June 9, 20251 yr by shodeira

I can also confirm in my case that downgrading from 7.1.3 -> 7.1.2 still didn't fix the connectivity issue for me. Almost immediately after reboot or after a few minutes the outbound connectivity got lost on host , but strangely not inside docker containers, lxc containers , or VMs.

For me disable "Host access to custom networks" is not a solution since the feature is used. What fixed for me was to downgrade back to 7.1.1.

Just to confirm ...having the same problem with V. 7.1.3 and I lost my shared CIF drives to home assistant

Anyone having connectivity issues, please retest with 7.1.4-rc.1 and see if it helps:

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-714-rc1-available-r3912/

just updated to 7.1.4 and lost access entirely

shim-br0 only gets an 169 ip.. looks like it does not even query the dhp server. setting static one via the cli, also did not work.

Please post the diagnostics.