This night my unraid server crashed. This morning i couldn't access it nor with webgui nor with ssh. It only answered ping. So i had to hard reboot.

When it came back online my NPM docker refused to start because port 80 is already in use.

typing "netstat -tulpn | grep 80" tells me that unraid is listenning to port 80  with the same pid that used for webgui which is set to port 3080.

Whenever i kill this pid it's started again and listen to port 80 and 3080. The process is nginx worker.

I never had this problem before.

Could this be a bug?

 

edit: ihave this lines in syslog at the time of reboot:

 10:43:47 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 127.0.0.1:3080 failed (98: Address already in use)
Jan  4 10:43:47 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 192.168.178.50:3080 failed (98: Address already in use)
Jan  4 10:43:47 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 127.0.0.1:3080 failed (98: Address already in use)
Jan  4 10:43:47 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 192.168.178.50:3080 failed (98: Address already in use)
Jan  4 10:43:48 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 127.0.0.1:3080 failed (98: Address already in use)
Jan  4 10:43:48 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 192.168.178.50:3080 failed (98: Address already in use)
Jan  4 10:43:48 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 127.0.0.1:3080 failed (98: Address already in use)
Jan  4 10:43:48 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 192.168.178.50:3080 failed (98: Address already in use)
Jan  4 10:43:49 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 127.0.0.1:3080 failed (98: Address already in use)
Jan  4 10:43:49 godzilla nginx: 2024/01/04 10:43:47 [emerg] 15223#15223: bind() to 192.168.178.50:3080 failed (98: Address already in use)

but webgui is accessible trough port 80

 

edit2: the webgui is also accessible trough port 80.  i don't understand what's happenning.

Edited January 4, 20242 yr by caplam

Could be that your settings on the USB got corrupted and reverted to the default of Unraid's GUI running on 80, check the settings.

the settings are ok.

Several reboots fixed the problem but that's strange.

I may have a problem on my server. I had to reboot several times to have the server back online. 

My server is on the basement and i'm on the third floor. I don't have ipmi only intel amt which only permits reboot. 

This just happened to me too. Exactly the same, noticed NPM won't start and realized the unraid gui was on both ports 80 and 81 (the one i've configured it to run on). A restart fixed it. weird

This just happened to me as well. I also figured it out because Nginx wouldn't launch, I figured out that the GUI was running on port 80, but when I checked the administration settings, it still showed the proper port. This seems like a bug.

Makes sense to need a reboot to apply a change to the whole way you interact with the server IMO.

Just wanna chime in and say: in the most recent update (7.0.0), this is still an issue. Frontend is set to 8080 on my Server, but it still claims port 80 on some boots.

 

Edit: i forgot to mention: the only reason i know this, is because Portainer actually prints a reason when a container fails to boot, instead of Unraids ominous "Internal Error", which tells exactly nothing.

Edited February 27, 20251 yr by hauskrampf
Forgot a part i wanted to say.

Same thing happened to me now. array is stuck at starting.

My gui worked fine on 80 and 443 for many years. and suddenly now get nginx :80 already used error.

booting into safe mode with UI, and changing ui port to 81 and 444 then start the array has temporary fixed it.

However once booting into normal mode, conflict happens again but on 81 and 444.

Something fucky is going on, when array starts, thats when the error happens. so something is during array startup procedure is trying to bind to the same port UI is configured to bind to.

None of my docker containers are configured to bind to 80 or 81

Edited April 2, 20251 yr by acoop133

Please post the diagnostics.