More context, after my server was manually shut down and powered back on I’ve had trouble login into the server. At first when I would power the server back on I wouldn’t be able to log into the server at all. Then, after a few rounds of powering it down and powering it back up, I was able to access the web ui log in page, but only briefly before my connection would stop responding. At one point I was able to power it back on and put it into safe mode, where things seemed to be fine again, I did a proper system reboot. After that I've been going through the same set of problems, not able to log in, or when I can it is only briefly before the web ui stops communicating. I have a monitor hooked up, and some of the time it will give me a different ip address, some times it give me the correct ip. At one point I was able to ping my old ip and it responded, and could access my shares via smb, but that is no longer the case. I also don’t seem to be able to boot into safe mode.

 

I was able to see this message "

Message from sys logdeTower. at May 5 09:06:19 ...
nginx: 2025/05/05 09:06:17 [emerg ) 972989729 : Sind() to 100.65.219.19:413 failed (98: Address already in use)
Message from sys logdeTower at May nginx: fros sy:30%88 106 :5, " Lemergs Sr2Desras: bindts to traTa:di5o :6160: ic3o1 iab141 :443 falled (st: madress already in uses
Message from sys logdeTower at May nginx: 2025/05/05 09:06:17 (emerg) 972919729: still could not bind c)"

 

 

To make things more complicated, I tried to created a diagnostic zip, but I'm unable to locate it on my thumb drive. I'm still pretty new to Unraid, but I'm wondering if the web ui isn't holding stable because a service I hadn't totally set up is trying to use port 443.

 

Any help is greatly appreciated.

1 minute ago, pastalavista said:

but I'm unable to locate it on my thumb drive

It should be in the /logs folder.

3 minutes ago, pastalavista said:

100.65.219.19:413

Why is this a public IP?

Thank you for point where the diagnostics zip would be.

The 100.65.219.19 is my tailscale ip, but I don't know why the system as a whole is trying to connect via it, and sometimes trying to connect via the correct ip 192.168.X.XX

tower-diagnostics-20250505-0902.zip

The general diagnostics don't include Tailscale-specific data, but I'm going to take a guess here that you might have run a command that looks like this at some point:

 

tailscale serve
 - or -
tailscale funnel

 

Those commands will cause Tailscale to run a reverse proxy on port 443, which then interferes with the WebGUI.

 

If you're not sure, you can run this:

tailscale serve status

 

If that shows that serve is enabled, you need to turn it off:

 

tailscale serve reset
tailscale funnel reset

 

 

14 hours ago, EDACerton said:

The general diagnostics don't include Tailscale-specific data, but I'm going to take a guess here that you might have run a command that looks like this at some point:

 

tailscale serve
 - or -
tailscale funnel

 

Those commands will cause Tailscale to run a reverse proxy on port 443, which then interferes with the WebGUI.

 

If you're not sure, you can run this:

tailscale serve status

 

If that shows that serve is enabled, you need to turn it off:

 

tailscale serve reset
tailscale funnel reset

 

 

This seems to have worked. Thanks so much!