Hi,

I have a problem with my Unraid server. Specifically, almost every hour (or even more often) nginx shuts itself down, which prevents me from accessing the Unraid GUI.

Other services that I have running in Docker work normally — I’m able to access them — but not the Unraid GUI.

In the logs, I found entries regarding a port 80 conflict, which nginx uses.
```
nginx: 2025/11/07 01:43:41 [emerg] 1210807#1210807: bind() to 127.0.0.1:80 failed (98: address already in use) unraid
```

At first, I thought one of the Docker containers might be using it, but I first disabled all Docker containers (the problem still occurred), then I completely shut down the Docker daemon, and the issue still persisted.

I can’t find the reason why the nginx server shuts down. I didn’t find anything in the logs besides the message mentioned above.

Basically, about an hour after nginx starts, it stops running, and I have to run /etc/rc.d/rc.nginx start (when I try to restart it, I get information that nginx is not running).

Additionally, I noticed another issue — I can’t connect to my Unraid server via SSH. Whenever nginx stops, SSH also stops working.

I then have to run:
/etc/rc.d/rc.nginx start

Then, in the Unraid GUI, I have to go to the Access Management tab and first disable SSH, save the changes, and then enable it again.

I’m attaching a diagnostic file from the server. I have no idea how to fix this anymore — I’ve restarted the server several times and the issue still persists.

Maybe it has something to do with the fact that I’m using WiFi to connect to the network instead of Ethernet?

I would be very grateful for any help!

tower-diagnostics-20251127-2115.zip

When the server is in this state, post the output from

lsof -i :80

11 hours ago, Atzon said:

Maybe it has something to do with the fact that I’m using WiFi to connect to the network instead of Ethernet?

I see some disconnect issues with WiFi, so it may also be worth retesting with wired if that's a possibility.

8 minutes ago, JorgeB said:

When the server is in this state, post the output from

lsof -i :80

Right now nginx is down again and I tried to find which process is using port 80, but unfortunately nothing came up:
lsof -i :80

It looks a bit like something is stopping nginx, then starting up on port 80, then nginx tries to start several times but port 80 is already in use, and afterward that process running on port 80 shuts itself down.

Maybe it’s some kind of race condition between two nginx instances during a network disconnect?

I’ll try running it over a cable for testing.

And does ps aux | grep nginx show something?

44 minutes ago, JorgeB said:

And does ps aux | grep nginx show something?

No, it doesn’t return anything, like the nginx had been completely killed

Can you retest with a wired connection?

2 hours ago, JorgeB said:

Can you retest with a wired connection?

I connected the server by cable and the problem did not occur this time. It looks like it is closely related to using Wi-Fi

It may be, the syslog did show some wifi disconnects and reconnects, so that may be the reason.

Okay, over the cable it has been working without any problems for almost the entire day.
It looks like it’s 99% a WiFi issue.

I wrote a simple script that monitors the nginx process and, whenever nginx gets killed, it restarts it. It’s not an ideal solution, but at least it works.
Ultimately, I plan to switch back to a wired connection anyway — I just don’t have the conditions for that at the moment.

If someone runs into this problem and finds a real solution, it would be great to learn about it. Unfortunately, I don’t have anything more than this workaround with the script.

are you installing nginx on the unraid host? Or on a Container? lol

I don't EVER make config changes on the host, not once not ever.