I just started using UnRaid to replace my simple single-drive server. However, I cannot keep it functioning properly for more than 24hrs. Every morning the Web GUI has completely died and is no longer functional, refusing any connections to it or timing out until I reboot the machine completely. This includes connections via the hostname and the ip address directly. The shares continue to be hosted, however, I can no longer administrate the machine at all. Given I don't have a monitor hooked up to it, or an SSH setup yet, this has been an enormous headache.

I'm surprised this has been an issue given UnRaid's reputation for reliability so I imagine it's some nuance with my setup or hardware. I'm a bit lost, however, where to begin troubleshooting its GUI. I haven't seen much on the forums about the Web GUI refusing connections on the latest version, but I did see some comments mentioning something similar used to be an issue on UnRaid 7.1.x. I'm unsure if this remains relevant to my issue or not. If it's relevant I'm using the motherboard's integrated gigabit NIC.

Key machine details:

Intel Core i7-8700

ASUS Z390-P Mobo

16GB DDR4 Non-ECC @ 2667MHz

3x 12TB WD Drives, 1x Red Pro, 2x Gold

UnRaid v7.2.3

I've attached the anonymized diagnostic logs but please let me know if there's anything else I can provide to help narrow down what's going sideways here!

Thank you,

HMG

cloudspire-diagnostics-20260213-1606.zip

Edited February 14Feb 14 by HomeMediaGuru

Enable the syslog server and set the persistent log to be saved to a share, then post that after the next crash

Enable the syslog server and set the persistent log to be saved to a share, then post that after the next crash

Thanks, got that enabled now we'll wait and see. Of course for the first time in a couple days it didn't die this morning, the only thing that comes to mind is that I hadn't left the browser open and logged into its management dashboard. Might try doing that again tonight and see if it goes down overnight again.

Alrighty well after a few days waiting for it to cease functioning again, because of course a watched pot never boils, it finally happened again! I am a little bit confused as I don't see any logs saved into the share I selected, but I was able to find both the syslog and syslog-previous reports under the System Log section. Now the syslog-previous that I found is dated a few days before this crash but has some interesting warning lines such as the below within it:

Feb 16 06:00:31 CloudSpire nginx: 2026/02/16 06:00:31 [emerg] 1152183#1152183: bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 16 06:00:32 CloudSpire nginx: 2026/02/16 06:00:31 [emerg] 1152183#1152183: bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 16 06:00:32 CloudSpire nginx: 2026/02/16 06:00:31 [emerg] 1152183#1152183: bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 16 06:00:33 CloudSpire nginx: 2026/02/16 06:00:31 [emerg] 1152183#1152183: bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 16 06:00:33 CloudSpire nginx: 2026/02/16 06:00:31 [emerg] 1152183#1152183: bind() to 0.0.0.0:80 failed (98: Address already in use)
---
Feb 16 06:00:34 CloudSpire nginx: 2026/02/16 06:00:34 [error] 1153587#1153587: MEMSTORE:01: tried adding WAITING chanhead 00000000009EBCC0 m/
Feb 16 06:00:34 CloudSpire nginx: 2026/02/16 06:00:34 [error] 1153587#1153587: MEMSTORE:01: tried adding WAITING chanhead 00000000009186A0 m/
Feb 16 06:00:34 CloudSpire nginx: 2026/02/16 06:00:34 [error] 1153587#1153587: MEMSTORE:01: tried adding WAITING chanhead 00000000009186A0 m/
Feb 16 06:00:34 CloudSpire nginx: 2026/02/16 06:00:34 [error] 1153587#1153587: MEMSTORE:01: tried adding WAITING chanhead 00000000009186A0 m/
---
Feb 16 06:01:29 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 127.0.0.1:80 failed (98: Address already in use)
Feb 16 06:01:29 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 169.254.140.190:80 failed (98: Address already in use)
Feb 16 06:01:30 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 127.0.0.1:80 failed (98: Address already in use)
Feb 16 06:01:30 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 169.254.140.190:80 failed (98: Address already in use)
Feb 16 06:01:30 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 127.0.0.1:80 failed (98: Address already in use)
Feb 16 06:01:30 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 169.254.140.190:80 failed (98: Address already in use)
Feb 16 06:01:31 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 127.0.0.1:80 failed (98: Address already in use)
Feb 16 06:01:31 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 169.254.140.190:80 failed (98: Address already in use)
Feb 16 06:01:31 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 127.0.0.1:80 failed (98: Address already in use)
Feb 16 06:01:31 CloudSpire nginx: 2026/02/16 06:01:29 [emerg] 2779378#2779378: bind() to 169.254.140.190:80 failed (98: Address already in use)
---
Feb 16 06:01:33 CloudSpire nginx: 2026/02/16 06:01:32 [emerg] 2780606#2780606: bind() to 169.254.140.190:80 failed (99: Cannot assign requested address)

I'm sure there are more gems I missed on my quick glance through the logs but from what I gather nginx runs the web server on UnRaid. I so far have no plugins, outside of the 'Community Applications' one, and Docker is not enabled yet on the server.

I've also attached a screenshot of what I have setup for the syslog server, however, the logs don't seem to be visible on the selected share. Are these actually present but hidden from the share's directory, or did I make a mistake here?

Additionally I also noticed that when the web GUI ceases to function the server can no longer connect via SSH either, so I'm left connecting to the device physically. Just in case that's relevant to troubleshooting this!

Thanks for all the help, it's greatly appreciated!
HMG

cloudspire-syslog-previous-20260216-2222.zip cloudspire-syslog-20260216-2220.zip cloudspire-diagnostics-20260216-1416.zip

Feb 15 06:00:04 CloudSpire kernel: r8169 0000:03:00.0 eth0: Link is Down

The link went down. This can cause issues restarting the services sometimes. If the link going down is a common thing, recommend setting a static IP, that will get around the issue.

9 hours ago, HomeMediaGuru said:

I am a little bit confused as I don't see any logs saved into the share I selected

See the instructions; you need to set the server IP.

12 hours ago, JorgeB said:

The link went down. This can cause issues restarting the services sometimes. If the link going down is a common thing, recommend setting a static IP, that will get around the issue.

Aha, I remember now my router reboots nightly to avoid a silly memory leak its software has. Right on, I've set up a static IP within UnRaid now in additon to the existing static IP reservation on the router itself.

12 hours ago, JorgeB said:

See the instructions; you need to set the server IP.

Ah indeed, in one of the detailed lines, mid-sentence, it does mention that. I assumed local syslog wouldn't need it when I first configured it but it's properly setup now.

Given all we've discussed I will assume this issue is resolved. If it comes back to bite me I'll re-open the post.

Thank you,

HMG