Hello!

I noticed that after a router reboot my Unraid instance goes unresponsive: it throws all SSH connections, and WebGUI / API are resetting connection. Hosted web services are, however, continue to work.

Issue started when I updated to 7.x (currently on 7.2.3).

My Unraid is hosted on Kingnovy R1 and wired through one of it's ethernet ports. Firstly I thought that it might be that Unraid tries to switch into second one as a backup, but this setting happened to be disabled in the UI. I think that on 7.0, for some reason, it didn't locked me out of SSH - and I could log in. One time I tried to troubleshoot the issue by myself - and found out that unraid's built-in nginx service tried to put itself on a already taken 80 (by docker) port instead of configured 83. Unfortunately, nowadays I can't ssh anymore (not in a zombie state)

I'll try to assign non-standart port for SSH next time. I'll be happy to provide any logs.

Edited February 17Feb 17 by Drun
1. I deleted notices about 502, because this error was thrown by Nginx PM when I tried to access unraid ui / api by it's domain name.

Please post the diagnostics after that happens again and before rebooting.

2 hours ago, JorgeB said:

Please post the diagnostics after that happens again and before rebooting.

Here we go:
before-tower-diagnostics-20260217-2345.zipafter-tower-diagnostics-20260217-2350.zip

Had to go rescue to not lock myself after rebooting the router. Took a very sad picture after.

There appears to be a racing condition between getting a new IP and starting the services, possibly because it took a long time for the DHCP server to provide a new one. If this is a typical occurrence, my suggestion would be to set a static IP, and you should no longer have issues.