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
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unable to access WebGUI directly

Featured Replies

Running Unraid 7.1.4

I CAN access the WebGUI through my configured Unraid Tunnel (yes I know. shouldn't have it accessible outside my network) and all other docker containers work fine both internally and through respective configurations externally. Checking nginx logs, I get these repeated:

nginx: 2025/08/09 11:21:17 [emerg] 522212#522212: bind() to 192.168.1.74:443 failed (98: Address already in use)

nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use)

nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)

nginx: [emerg] bind() to 192.168.1.74:80 failed (98: Address already in use)

nginx: [emerg] bind() to 127.0.0.1:443 failed (98: Address already in use)

nginx: [emerg] bind() to 192.168.1.74:443 failed (98: Address already in use)

I've attached my diagnostics file. As far as I can tell, no other service/container are utilizing 80 or 443. Nothing was changed prior to this error starting from my knowledge, unless it was a plugin/docker update.

Results of netstat -tulpn | grep 80 :

tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 41034/nginx: master

tcp 0 0 192.168.1.74:80 0.0.0.0:* LISTEN 41034/nginx: master

tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN 17666/docker-proxy

tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 17650/docker-proxy

tcp6 0 0 :::8090 :::* LISTEN 17673/docker-proxy

tcp6 0 0 :::8080 :::* LISTEN 17658/docker-proxy

Neither rebooting nor reloading/restarting nginx have resolved it. I did also remove the Unraid connect plugin as I've seen where that would cause similar issues for others. Would greatly appreciate any insight/help here.

executor-diagnostics-20250809-1120.zip

Edited by cynikai

  • Community Expert

Disable docker service, reboot in safe mode, and post new diagnostics.

  • Community Expert

I no longer see the nginx errors, can you acces the GUI like that?

  • Author

No I was not able to access the GUI in safemode either. Still getting 404 errors.

  • Community Expert

That suggests to me a config issue, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.