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 GUI - Recently updated after long hiatus to 6.12.13 ?

Featured Replies

I had not done anything with my unraid server for several years- everything was running just fine no need for any changes to unraid anything.

 

However, i recently decided to get on and decided to upgrade as i had put it off for so long, IIRC It was previously running on v5 something or maybe even 4?

 

Anyways, the server i running just fine under the hood. I can SSH into it normally, login via direct access as well. Something seems to be broken however as I can not access my Web GUI. All my dockers and everything are running just fine however.

I saw some release notes mentioning turning ssl off > (If memory serves me here:

use_ssl off

 

but i am still unable to access the web ui. performing netstate -grep returns:

 

~# netstat -grep
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         OPNsense.kronoc 0.0.0.0         UG    0      0        0 shim-br0
default         OPNsense.kronoc 0.0.0.0         UG    1008   0        0 br0
REDACTED      0.0.0.0         255.255.255.255 UH    0      0        0 wg0
REDACTED      0.0.0.0         255.255.0.0     U     0      0        0 docker0
REDACTED      0.0.0.0         255.255.0.0     U     0      0        0 br-e2d3fd4035e1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 shim-br0
192.168.1.0     0.0.0.0         255.255.255.0   U     1008   0        0 br0
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0

 

I feel as though the br0 interfaces dont quite seem right?

 

I am attaching the diagnostics zip to my post as customary. Anything else i can provide please let me know.

tower-diagnostics-20241125-1308.zip

  • Community Expert
PORT="8008"

 

Are you trying to connect to this port?

  • Author
8 minutes ago, JorgeB said:
PORT="8008"

 

Are you trying to connect to this port?

That is correct sir. I have tried utilizing my local ip: http://192.168.1.64:8008 to no success but also tower.local

  • Community Expert

I would recommend booting with a different flash drive suing a stock install, no key needed, then retest, that will confirm if it's a config issue or an external problem.

You have ssh access? Do these command and report back with the output:

 

netstat -anp | grep LISTEN | grep 80

 

netstat -anp | grep LISTEN | grep 8008

 

netstat -anp | grep LISTEN | grep 443

 

/etc/rc.d/rc.nginx restart

 

emhttp stop


emhttp start

 

wget 127.0.0.1:8008

 

wget 127.0.0.1

Edited by DivideBy0

  • Author

 

9 minutes ago, DivideBy0 said:

You have ssh access? Do these command and report back with the output:

 

netstat -anp | grep LISTEN | grep 80

 

netstat -anp | grep LISTEN | grep 8008

 

netstat -anp | grep LISTEN | grep 443

 

/etc/rc.d/rc.nginx restart

 

emhttp stop


emhttp start

 

wget 127.0.0.1:8008

 

wget 127.0.0.1

Please hold, will be shutting down and putting my original flash drive in to try this.

Edited by powderwt
included two quotes

  • Author
52 minutes ago, JorgeB said:

I would recommend booting with a different flash drive suing a stock install, no key needed, then retest, that will confirm if it's a config issue or an external problem.

Just tried as you directed utilizing a fresh imaged usb with the new unraid usb creator tool. Able to access the web UI no problem both via tower.local and my set IP of

192.168.1.64

  • Author

@DivideBy0
 

Quote

netstat -anp | grep LISTEN | grep 80

 netstat -anp | grep LISTEN | grep 80
tcp        0      0 0.0.0.0:9897            0.0.0.0:*               LISTEN      16880/docker-proxy
tcp        0      0 0.0.0.0:8070            0.0.0.0:*               LISTEN      15821/docker-proxy
tcp        0      0 0.0.0.0:8060            0.0.0.0:*               LISTEN      15854/docker-proxy
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      13238/docker-proxy
tcp6       0      0 :::43803                :::*                    LISTEN      6396/rpc.statd
tcp6       0      0 :::8070                 :::*                    LISTEN      15830/docker-proxy
tcp6       0      0 :::8060                 :::*                    LISTEN      15861/docker-proxy
tcp6       0      0 :::1880                 :::*                    LISTEN      13246/docker-proxy
unix  2      [ ACC ]     STREAM     LISTENING     40671    16493/containerd-sh  /run/containerd/s/f0d79bea468cd1831218588ccab627d193c780425a6e2bc9e8462896e72c2b98
unix  2      [ ACC ]     STREAM     LISTENING     45434    17451/containerd-sh  /run/containerd/s/3398050e0b58bfe0434e7d4262fb539d3fa9b4fb8f274c4fcc34fc6202792a15

 

Quote

netstat -anp | grep LISTEN | grep 8008

 

**Nothing Returned here**

 

Quote

netstat -anp | grep LISTEN | grep 443

 

 netstat -anp | grep LISTEN | grep 443
tcp        0      0 0.0.0.0:18443           0.0.0.0:*               LISTEN      13194/docker-proxy
tcp6       0      0 :::18443                :::*                    LISTEN      13201/docker-proxy

 

Quote

/etc/rc.d/rc.nginx restart

 

# /etc/rc.d/rc.nginx restart
Nginx is not running

 

Quote

emhttp stop

 

emhttp stop
Nginx is not running
Gracefully shutting down php-fpm  done
Stopping emhttpd
rmmod: ERROR: Module md_mod is in use

 

Quote


emhttp start

 

**Brief pause, but did not output anything**

 

Quote

wget 127.0.0.1:8008

 

 wget 127.0.0.1:8008
--2024-11-25 15:05:58--  http://127.0.0.1:8008/
Connecting to 127.0.0.1:8008... failed: Connection refused.

 

Quote

wget 127.0.0.1

 

 wget 127.0.0.1
--2024-11-25 15:06:19--  http://127.0.0.1/
Connecting to 127.0.0.1:80... failed: Connection refused.

 

  • Community Expert
12 hours ago, powderwt said:

Able to access the web UI no problem both via tower.local and my set IP of

192.168.1.64

That confirms it's a config issue, if you don't find what causing the problem, you can redo 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, confirm it's still working, and 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.    

  • Author
8 hours ago, JorgeB said:

That confirms it's a config issue, if you don't find what causing the problem, you can redo 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, confirm it's still working, and 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.    

Any suggestions for where to look as far as what could be causing the problem? It was all fine until i updated, really prefer to not have to go through all the trial and error that involves as it will mean alot of up and down of the things im hosting.

  • 2 weeks later...

Did you fix this? I found my solution it was GPU Statistics. I read several posts on reddit pointing to this pluggin and I removed. No more GUI issues, so far.

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.