I'm not sure what is going on. I'm on 7.1.3 and have been since about a week after release. Today I discovered that it can't reach mothership.unraid.net with a 'Socket closed' error. If I turn off the Docker service, everything is fine. Plugins can be update, app store is accessible, etc. I've checked all my network settings and they are valid and unchanged since I first installed Unraid on this box several years ago with the 6.x release.

I saw someone reference having the vpn manager in 'active' mode and turning it off. I checked that, but it was already in inactive mode. Before I closed the page it wanted me to generate keys, so I did, but left the tunnel manager in inactive mode. The problem went away for a few minutes after applying the config with generated keys, but eventually came back (Docker service still running during this). The VM service doesn't affect this situation at all.

Only having the Docker service running with our without any containers active causes this issue. I'm going to look at the network configs for the containers and switch to them all to bridge to see if that makes a difference. I have a few on a custom network behind nginx proxy manager, but that hasn't been a problem before.

My docker service is configured for 'ipvlan' at the moment, no changes to that since wayback when 'macvlan' was causing problems.

Should i switch back to 'macvlan' now?

I'm hesitating to update to 7.1.4 until I can solve this unless the new update fixes things like this.

pinkfloyd.local-diagnostics-20250627-1303.zip

Update to 7.1.4, a few users have connectivity issues with 7.1.3