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 webUI after 6.12.0 update.

Featured Replies

Solved by ljm42

I Think i am having the same issue here as this.

10 hours ago, cferra said:

I Think i am having the same issue here as this.

 

We'll need your diagnostics.zip to check. See earlier in this thread for details.

  • Solution

Hey everyone, Unraid 6.12.1 should resolve the issues in this thread:

https://forums.unraid.net/topic/140824-unraid-os-version-6121-available/

 

Well, unless you are running SSL on port 445, you'll still need to tweak that setting to prevent a conflict:

https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735

 

If you can't currently access the webgui in 6.12.0, see the manual upgrade process here:

https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

 

If you continue to have issues, please start a new thread and be sure to include your diagnostics.zip from 6.12.1

  • Author
3 hours ago, ljm42 said:

Hey everyone, Unraid 6.12.1 should resolve the issues in this thread:

https://forums.unraid.net/topic/140824-unraid-os-version-6121-available/

 

Well, unless you are running SSL on port 445, you'll still need to tweak that setting to prevent a conflict:

https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735

 

If you can't currently access the webgui in 6.12.0, see the manual upgrade process here:

https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

 

If you continue to have issues, please start a new thread and be sure to include your diagnostics.zip from 6.12.1

Updating to v6.12.1 fixed it for me. Everything is working as intended now. 😁

 

Thank you so much for working through this with me and finding a solution so quickly!

Hello,

 

I still have no webui. I did an SSH manual upgrade per the above instructions.

 

The upgrade to 6.12.1 completed successfully. The server rebooted and came up running 6.12.1. The dockers, and vms on auto-start came up and worked fine.

 

However, I still can't connect to the webui from a PC or a Mac. I've also tried using the local IP address https://10.0.0.224:54443/Dashboard and get "This site can’t be reached"

"10.0.0.224 refused to connect."

 

What next?

 

Thanks, Carlos

I forgot to mention that, booting Unraid in GUI mode, Firefox only displays "Unable to connect" "An error occured during a connection to local host"

 

Sorry I hadn't posted the server diagnostics.  My Unraid server has 2 built-in NICs configured in redundant mode.  Everything seems to be working but the webui interface.

 

Thanks, Carlos

tower-diagnostics-20230625-1159.zip

13 hours ago, cluengas said:

My Unraid server has 2 built-in NICs

Both NICs have the same IP address, correct that and it should work after.

Ok, thank you Jorge! I'm a bit puzzled because my server had been working flawlessly with the current network configuration until I upgraded to 6.12.0

 

Anyway, please let me know which file I need to edit to change the network configuration. I attempted to change one IP using "ip addr add 10.0.0.223/24 dev br0" but it didn't change anything. I'm thinking I could temporarily remove bond0, br0, and eth0 to get access to the webui.

 

root@Tower:~# ifconfig

bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500

        ether e0:d5:5e:65:b3:e4  txqueuelen 1000  (Ethernet)

        RX packets 98556  bytes 12180708 (11.6 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 330  bytes 121637 (118.7 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

bond1: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500

        ether e0:d5:5e:65:b3:e2  txqueuelen 1000  (Ethernet)

        RX packets 26834229  bytes 32714654885 (30.4 GiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 17357886  bytes 15549789731 (14.4 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 10.0.0.224  netmask 255.255.255.0  broadcast 0.0.0.0

        ether e0:d5:5e:65:b3:e4  txqueuelen 1000  (Ethernet)

        RX packets 98356  bytes 10782869 (10.2 MiB)

        RX errors 0  dropped 10  overruns 0  frame 0

        TX packets 323  bytes 120619 (117.7 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 10.0.0.224  netmask 255.255.255.0  broadcast 0.0.0.0

        ether e0:d5:5e:65:b3:e2  txqueuelen 1000  (Ethernet)

        RX packets 25979320  bytes 32186911931 (29.9 GiB)

        RX errors 0  dropped 10  overruns 0  frame 0

        TX packets 10793772  bytes 15010107947 (13.9 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

br-7cd89d9eb953: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255

        ether 02:42:53:7f:5f:e1  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255

        ether 02:42:0b:a3:fb:eb  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether e0:d5:5e:65:b3:e4  txqueuelen 1000  (Ethernet)

        RX packets 98556  bytes 12180708 (11.6 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 330  bytes 121637 (118.7 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 18  

 

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether e0:d5:5e:65:b3:e2  txqueuelen 1000  (Ethernet)

        RX packets 26834229  bytes 32714654885 (30.4 GiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 17357886  bytes 15549789731 (14.4 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  memory 0xef700000-ef720000  

 

2 minutes ago, cluengas said:

I'm a bit puzzled because my server had been working flawlessly with the current network configuration until I upgraded to 6.12.0

Due to network changes v6.12.0 now needs that to be correctly configured.

 

3 minutes ago, cluengas said:

Anyway, please let me know which file I need to edit to change the network configuration.

Edit /boot/config/network.cfg change one of the IP addresses and reboot.

That did it!! 

Jorge, thank you very much!

I'm still having the issue on 6.12.1 and i only have 1 ip assigned. diagnostics attached. It seems sort of random, sometimes it works sometimes it doesn't, usually starts to work after i goto my lan ip instead of the name but even that is hit or miss

unraid-diagnostics-20230628-1703.zip

Edited by Lygris
details

9 hours ago, Lygris said:

I'm still having the issue on 6.12.1 and i only have 1 ip assigned

I would try without the bond.

  • 2 weeks later...
9 minutes ago, namida said:

but you can’t access it after a few hours after booting up.

Try closing all browser windows, then open it after a few hours and see if the GUI is up, if yes close browser again and keep re-testing.

1 hour ago, namida said:

You can access the webui just after booting up, but you can’t access it after a few hours after booting up.

 

We are working on issues related to ipv6. For now I'd recommend going to Settings -> Network and configuring the system for ipv4 only

 

Also, it looks like you might be having issues when stopping the array. See https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063

 

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.