Unraid GUI Main/Dashboard not populating. NGINX/Tailscale issue? Diag attached before/after

Having a really weird issue here, think tailscale so posted there but could be anything at this point. To start, my cache became full about a week ago and caused a ton of problems with appdata programs. Had ZFS snapshots of all of them so issue was quickly resolved. Within the last week I started having an issue where my Unraid main page would stop loading all of the drives and the CPU on the dashboard would stop updating usage. Turned out it was related to the built in NGINX and it saying that port 443 and 80 failed to bind to xxxx as they are "Already in use." Tried to reload and restart NGINX several times. When restarting NGINX, issue would go away for about a minute then come back. with the same associated errors that it failed to bind and already in use. Tried turning off Docker and VM manager all together and restarting, no difference. Downgraded Unraid to 6.12.11 from 6.12.12, no change. Nothing was showing it was trying to use 443/80 that should cause issues but kept getting the error. The only change before this occurred was trying to install Gluetun and trying several settings but never got it to work including giving it a tun9 that doesn't exists as a test. Deleted the docker and image and haven't had since. May have broke something in the network though? Not sure. 
 

Removed the tailscale plugin and restarted and issue went away. Reinstalled plugin and erased the settings from tailscale to start from scratch, issue came back. As of the last 30 minutes I have kept "Unraid services listen on Tailscale IP" to No and this appears to solve the problem. Restarted and everything is normal as well. All other tailscale settings are default. 

I don't know what could have caused this if its related to my cache becoming full a week ago or if there was an update etc. Attached my diagnostics before I narrowed it down to tailscale and fixed it and after I "think" I have fixed it. Anyone have any idea what is going on here? I used to keep this setting on so you can access the sever from the tailscale IP and always worked great. 

After Fix-diagnostics-20241006-1749.zip Before Fix-diagnostics-20241006-1521.zip