February 16Feb 16 I'm running into a problem with Unraid where the WebUI is not accessible and neither is the system through SSH. The docker containers running on the system are running and I can access their individual UI with no issues.This has happened before, but i didn't capture logs from previous incidents.NAME="Unraid OS" ID="unraid-os" ID_LIKE="slackware" PRETTY_NAME="Unraid OS 7.2 x86_64" CPE_NAME="cpe:/o:limetech:unraid-os:7.2.3" VERSION="7.2.3 2025-12-18" VERSION_ID="7.2.3" VERSION_CODENAME="stable" HOME_URL="https://unraid.net/" SUPPORT_URL="https://support.unraid.net/" BUG_REPORT_URL="https://forums.unraid.net/" DOCUMENTATION_URL="https://docs.unraid.net/" VENDOR_NAME="Lime Technology, Inc."The only way I'm able to access the system is locally with a connected monitor and keyboard. I noticed that ssh was not running, so I start the service using the following command./etc/rc.d/rc.sshd startThis allows me to access the server remotely, previously when this happened, I've tried to start the nginx service with the following command/etc/rc.d/rc.nginx start root@Tank:~# /etc/rc.d/rc.nginx status Nginx server daemon is not running. root@Tank:~# /etc/rc.d/rc.nginx start rc.nginx: Starting Nginx server daemon... Starting Unraid API service... Starting flash backup service... Starting the Unraid API [PM2][WARN] Applications unraid-api not running, starting... [PM2][WARN] App unraid-api has option 'wait_ready' set, waiting for app to be ready... [PM2] App [unraid-api] launched (1 instances) +--- unraid-api namespace : default version : 4.29.2+c39b0b26 pid : 2918431 pm2 id : 0 status : online mode : fork restarted : 0 uptime : 1s memory usage : 229.8mb error log : /var/log/graphql-api.log watching : no PID file : /var/log/.pm2/pids/unraid-api-0.pid Starting nchan processes... rc.nginx: Nginx server daemon... Started.but the webUI is still not accessible. I've attached the nginx error log as well. Only way i've been able to resolve this is a reboot, not sure what is actually causing the issue. I've seen other post about leaving the unraid dashboard open on browsers might cause this. On this current incident, I've made a point to close out any dashboard tabs i have open, I probably only used the dashboard once since the last incident and I closed the tab on the browser.error.log syslog tank-diagnostics-20260216-1133.zip Edited February 17Feb 17 by Blitztorque
February 16Feb 16 Community Expert When the problem occurs, see if you can get the results of this command line:df -h /
February 16Feb 16 Author This is the outputroot@Tank:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 737M 15G 5% /
February 16Feb 16 Author It's been a couple of hours since I manually started the ssh and nginx process, I'm now able to access the web UI. But would like some help to dig deeper on why this is happening. I've had it happen multiple times, last time was 3 days ago. The syslog shows the eth0 link is down, I verified with my router, its reboot schedule lines up with the link going down at 3am. Then nginx server daemon is reloaded an it fails because binding issues. Unraid nginx ui is set to port 81/444, I have a docker container nginx set to run on port 80/443. I'm not sure why there is the bind issue on reload if it was working perfectly fine before the internet went down.Feb 16 03:00:19 Tank kernel: r8169 0000:03:00.0 eth0: Link is Down Feb 16 03:00:19 Tank kernel: bond0: (slave eth0): link status definitely down, disabling slave Feb 16 03:00:19 Tank kernel: r8169 0000:03:00.0 eth0: left promiscuous mode Feb 16 03:00:19 Tank kernel: r8169 0000:03:00.0 eth0: left allmulticast mode Feb 16 03:00:19 Tank kernel: bond0: now running without any active interface! Feb 16 03:00:19 Tank kernel: br0: port 1(bond0) entered disabled state Feb 16 03:00:20 Tank dhcpcd[1831]: br0: carrier lost Feb 16 03:00:20 Tank dhcpcd[1831]: br0: deleting route to 192.168.68.0/22 Feb 16 03:00:20 Tank dhcpcd[1831]: br0: deleting default route via 192.168.68.1 Feb 16 03:00:20 Tank dhcpcd-run-hooks: interface=br0, reason=EXPIRE, protocol=dhcp Feb 16 03:00:20 Tank update_services: remove queued job 3 Feb 16 03:00:20 Tank update_services: queue new job 9, wait for 20s Feb 16 03:00:20 Tank dnsmasq[12616]: no servers found in /etc/resolv.conf, will retry Feb 16 03:00:23 Tank ntpd[2079]: Deleting 1 br0, [192.168.68.77]:123, stats: received=277, sent=278, dropped=0, active_time=231180 secs Feb 16 03:00:23 Tank ntpd[2079]: 216.239.35.0 local addr 192.168.68.77 -> <null> Feb 16 03:00:40 Tank reload_services: execute queued job 9 Feb 16 03:00:41 Tank rc.ntpd: Updating NTP server daemon... Feb 16 03:00:41 Tank ntpd[2079]: ntpd exiting on signal 1 (Hangup) Feb 16 03:00:41 Tank ntpd[2562997]: ntpd [email protected] Fri Jul 4 19:14:57 UTC 2025 (1): Starting Feb 16 03:00:41 Tank ntpd[2562997]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Feb 16 03:00:41 Tank ntpd[2562997]: ---------------------------------------------------- Feb 16 03:00:41 Tank ntpd[2562997]: ntp-4 is maintained by Network Time Foundation, Feb 16 03:00:41 Tank ntpd[2562997]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Feb 16 03:00:41 Tank ntpd[2562997]: corporation. Support and training for ntp-4 are Feb 16 03:00:41 Tank ntpd[2562997]: available at https://www.nwtime.org/support Feb 16 03:00:41 Tank ntpd[2562997]: ---------------------------------------------------- Feb 16 03:00:41 Tank ntpd[2562997]: DEBUG behavior is enabled - a violation of any diagnostic assertion will cause ntpd to abort Feb 16 03:00:41 Tank ntpd[2562999]: proto: precision = 0.032 usec (-25) Feb 16 03:00:41 Tank ntpd[2562999]: basedate set to 2025-06-22 Feb 16 03:00:41 Tank ntpd[2562999]: gps base set to 2025-06-22 (week 2372) Feb 16 03:00:41 Tank ntpd[2562999]: initial drift restored to 10.037109 Feb 16 03:00:41 Tank ntpd[2562999]: bind(16) AF_INET 127.0.0.1:123 flags 0x5 failed: Address already in use Feb 16 03:00:41 Tank ntpd[2562999]: unable to create socket on lo (0) for 127.0.0.1:123 Feb 16 03:00:41 Tank ntpd[2562999]: cannot bind address 127.0.0.1 Feb 16 03:00:41 Tank ntpd[2562999]: Listen normally on 1 lo [::1]:123 Feb 16 03:00:41 Tank ntpd[2562999]: Listening on routing socket on fd #17 for interface updates Feb 16 03:00:41 Tank ntpd[2562999]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Feb 16 03:00:41 Tank ntpd[2562999]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Feb 16 03:00:41 Tank rc.nginx: Updating Nginx server daemon... Feb 16 03:00:41 Tank rc.nginx: Reloading Nginx server daemon... Feb 16 03:00:41 Tank rc.nginx: Checking configuration for correct syntax and then trying to open files referenced in configuration... Feb 16 03:00:41 Tank rc.nginx: /usr/sbin/nginx -t -c /etc/nginx/nginx.conf Feb 16 03:00:41 Tank rc.nginx: Reloading Nginx server daemon configuration... Feb 16 03:00:41 Tank nginx: 2026/02/16 03:00:41 [emerg] 7297#7297: bind() to 0.0.0.0:80 failed (98: Address already in use) Feb 16 03:00:41 Tank nginx: 2026/02/16 03:00:41 [emerg] 7297#7297: bind() to 0.0.0.0:81 failed (98: Address already in use) Feb 16 03:00:41 Tank nginx: 2026/02/16 03:00:41 [emerg] 7297#7297: bind() to 0.0.0.0:444 failed (98: Address already in use) Feb 16 03:00:42 Tank nginx: 2026/02/16 03:00:41 [emerg] 7297#7297: bind() to 0.0.0.0:80 failed (98: Address already in use) Edited February 16Feb 16 by Blitztorque
February 17Feb 17 Author Solution Looked into my issue more, it seems to be a bug in how nginx is reloaded and started in a network outrage event. I was going to create a BUG report, but seems like someone already beat me too it. https://product.unraid.net/p/nginx-duplicate-server-blocks-after-network-outageA workaround would be to set a static ip.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.