Not sure if this is the correct section for this - so I apologize in advance if it is not. I had a power outage the other day that was long enough to have my UPS initiate a graceful shutdown of my tower and router and modem. The system has been rock solid for years - until this recent power outage. I can no longer access the WebGUI. At first, I thought it was a docker Hdhrdvr causing this issue as it and only two others were in Host mode (Plex and Home Assistant). The reason why I thought it was that docker was due to the fact that every time I tried to access my UnRaid dashboard, the HDHomeRun DVR configuration page would appear instead of the WebGUI. All of my other dockers I can connect to fine <IP:Port> and even the dockers that use VNC show up without issue. I'm able to SSH/PuTTy into the terminal without issue as well. I've run nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful then nginx -s reload: nginx: [error] invalid PID number "" in "/var/run/nginx.pid" I also tried: nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:15 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:16 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:16 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:17 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:17 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] still could not bind() Message from syslogd@CozsNAS at Jul 5 13:24:18 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: still could not bind() running netstat -nalp | grep -i 'nginx: master' returned nothing what-so-ever Then trying: netstat -nalp | grep -E 'tcp\s.*(:80|:443).*LISTEN\s' tcp 0 0 0.0.0.0:8091 0.0.0.0:* LISTEN 22673/docker-proxy tcp 0 0 0.0.0.0:8010 0.0.0.0:* LISTEN 14385/docker-proxy tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 13325/docker-proxy tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 13733/docker-proxy tcp 0 0 0.0.0.0:8089 0.0.0.0:* LISTEN 17567/docker-proxy tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN 13311/docker-proxy I've pinged TOWERNAME from my WindowsPC and it resolves with the static assigned IP address I managed to figure out how to disable the hdrhomerun docker from auto starting and rebooting the tower. Since disabling the hdhomerun docker and rebooting the server and typing in nginx nothing happens. Entering nginx -s reload no errors show up either. Entering in docker network inspect host: "Name": "host", "Id": "937fbdeca1b4fcaf5d1930f1fbbc740461b25c5699070a79cfc49b6755722d24", "Created": "2020-12-09T11:07:08.920604571-05:00", "Scope": "local", "Driver": "host", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "79c3c4cbb2fa30b3a9bec0a621e56e2f51032c120096c115bdead6aa7a881c25": { "Name": "home-assistant", "EndpointID": "01d6247f536f7cfa0a70cb2314197ec344038e9e975f19c3f862946717ebf5b f", "MacAddress": "", "IPv4Address": "", "IPv6Address": "" }, "d236e30221155a37809b821e4dfb64aa37ced3ee1834a6f950ffd9940ed747c3": { "Name": "PlexMediaServer", "EndpointID": "1ceb127b22c6a92f8975b57f9695382d222b383e8cd472290f38179a764d11c 4", "MacAddress": "", "IPv4Address": "", "IPv6Address": "" } }, "Options": {}, "Labels": {} shows that the HDHomeRun docker is no longer starting on reboot. I am still unable to access the GUI. Looking at the "MyServers" plugin on the forums, it reports that my Tower is online. Trying to access it from the hyperlink on that webpage also just simply timesout. I've exhausted everyone's knowledge and my own trying to figure out what could possibly be wrong now. Some folks on /r/UnRaid were helping but they have since gone silent - I guess they have run out of ideas as to what to try? So now I turn to you fine folk. If it makes any difference I am running an Ubiquiti UDM router (UniFi OS1.12.22 / Network7.1.66) in case the power outage and subsequent reboot of everything might have an effect on something, somewhere. I've also power cycled the cable modem and rebooted the router a few times as a just in case type of thing. I really could use some help here. Thank you, in advance.

Replying to this for posterity’s sake. The issue has now been resolved. It was, indeed the HDHomeRun Docker causing the issue. It took over port80 when the author of said docker updated it due to Silicon Dust releasing a GUI for the DVR hardware. Unforseen consequence he has stated on GitHub after I opened an issue. In order to access the webgui since the docker took over port 80 the following commands were used: nano -w /boot/config/ident.cfg then looking for the PORT line entry and changing it to a random number and saving the file. /etc/rc.d/rc.nginx restart Then typing in the IP:Newly Assigned Port of the UnRaid server into Edge / Firefox. Going into the Docker tab, stopping the offending Docker and then unchecking "autostart" Reverse the commands above, changing the PORT line entry back to the default of 80 and rebooting the server allowed access once again.

Skip to content

View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS

Tap the Share icon in Safari
Scroll the menu and tap Add to Home Screen.
Tap Add in the top-right corner.

To install this app on Android

Tap the 3-dot menu (⋮) in the top-right corner of the browser.
Tap Add to Home screen or Install app.
Confirm by tapping Install.

Unraid Unleash Your Hardware

Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Unraid Unleash Your Hardware

WebGUI after reboot no longer loads/connects

Followers

Solved by CoZ

July 8, 20224 yr

Go to solution

April 2, 20251 yr

Ive just now getting this issue and none of the mentions above helped me either.

Quote

April 2, 20251 yr

Community Expert

Can you access the command line?

Quote

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.

Followers

Go to topic listing

Where:

Search:

Date Created:

Use:

Last Updated:

Chrome (Android)

Tap the lock icon next to the address bar.
Tap Permissions → Notifications.
Adjust your preference.

Chrome (Desktop)

Click the padlock icon in the address bar.
Select Site settings.
Find Notifications and adjust your preference.

WebGUI after reboot no longer loads/connects

Featured Replies

Solved by CoZ

Join the conversation

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)