cferra Posted June 17, 2023 Share Posted June 17, 2023 I Think i am having the same issue here as this. Quote Link to comment
ljm42 Posted June 17, 2023 Share Posted June 17, 2023 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. Quote Link to comment
Solution ljm42 Posted June 20, 2023 Solution Share Posted June 20, 2023 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 1 Quote Link to comment
moosedookie Posted June 20, 2023 Author Share Posted June 20, 2023 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! 1 Quote Link to comment
cluengas Posted June 25, 2023 Share Posted June 25, 2023 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 Quote Link to comment
cluengas Posted June 25, 2023 Share Posted June 25, 2023 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" Quote Link to comment
JorgeB Posted June 25, 2023 Share Posted June 25, 2023 Please post the diagnostics. Quote Link to comment
cluengas Posted June 25, 2023 Share Posted June 25, 2023 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 Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 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. Quote Link to comment
cluengas Posted June 26, 2023 Share Posted June 26, 2023 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 Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 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. Quote Link to comment
cluengas Posted June 26, 2023 Share Posted June 26, 2023 That did it!! Jorge, thank you very much! 1 Quote Link to comment
Lygris Posted June 28, 2023 Share Posted June 28, 2023 (edited) 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 June 28, 2023 by Lygris details Quote Link to comment
JorgeB Posted June 29, 2023 Share Posted June 29, 2023 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. Quote Link to comment
namida Posted July 10, 2023 Share Posted July 10, 2023 You can access the webui just after booting up, but you can’t access it after a few hours after booting up. The edge display keeps loading without returning any errors. The ports on the docker service are accessible, such as port 8096 of jellyfin. , the ip configured by the direct network card in the virtual machine is also accessible, but the unraid webui cannot be accessed Using the commands provided in the post, I did not find the same error as in the post hope that can provide a solution thanks The virtual machine is not currently enabled, and unraid has only one network card root@UNRAID:~# cat /etc/nginx/conf.d/servers.conf # # Listen on local socket for nchan publishers # server { listen unix:/var/run/nginx.socket default_server; location ~ /pub/(.*)$ { nchan_publisher; nchan_channel_id "$1"; nchan_message_buffer_length $arg_buffer_length; } location ~ /nchan_stub_status$ { nchan_stub_status; } } # # Always accept http requests from localhost # ex: http://localhost # ex: http://127.0.0.1 # ex: http://[::1] # server { listen 127.0.0.1:81; # lo listen 127.0.0.1:444; # lo listen [::1]:81; # lo listen [::1]:444; # lo # include /etc/nginx/conf.d/locations.conf; } # # Port settings for http protocol # ex: http://tower (IP address resolved via NetBIOS) # ex: http://tower.local (IP address resolved via mDNS) # ex: http://192.168.1.100 # ex: http://[::ffff:192.168.1.100] # server { listen 192.168.31.100:81 default_server; # br0 listen 10.253.0.1:81 default_server; # wg0 listen [fd00:6868:6868::63c]:81 default_server; # br0 listen [fc00:253::1]:81 default_server; # wg0 # location ~ /wsproxy/81/ { return 403; } include /etc/nginx/conf.d/locations.conf; } root@UNRAID:~# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.31.100 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::4ecc:6aff:fe6d:b221 prefixlen 64 scopeid 0x20<link> inet6 fd00:6868:6868:0:4ecc:6aff:fe6d:b221 prefixlen 64 scopeid 0x0<global> inet6 fd00:6868:6868::63c prefixlen 128 scopeid 0x0<global> ether 4c:cc:6a:6d:b2:21 txqueuelen 1000 (Ethernet) RX packets 1741654 bytes 711537620 (678.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4726591 bytes 4640681486 (4.3 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-7d53774d62c8: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.31.200.1 netmask 255.255.255.0 broadcast 172.31.200.255 ether 02:42:18:13:c2:d1 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=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fd17::1 prefixlen 64 scopeid 0x0<global> inet6 fe80::1 prefixlen 64 scopeid 0x20<link> inet6 fe80::42:6fff:feaa:aae1 prefixlen 64 scopeid 0x20<link> ether 02:42:6f:aa:aa:e1 txqueuelen 0 (Ethernet) RX packets 3720971 bytes 4414205020 (4.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1546794 bytes 688495753 (656.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet6 fe80::4ecc:6aff:fe6d:b221 prefixlen 64 scopeid 0x20<link> ether 4c:cc:6a:6d:b2:21 txqueuelen 1000 (Ethernet) RX packets 1929172 bytes 756811557 (721.7 MiB) RX errors 0 dropped 52 overruns 0 frame 0 TX packets 4817604 bytes 4665284252 (4.3 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xfb400000-fb420000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 92855 bytes 18026544 (17.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 92855 bytes 18026544 (17.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth008b021: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::4c29:23ff:fe1f:6df3 prefixlen 64 scopeid 0x20<link> ether 4e:29:23:1f:6d:f3 txqueuelen 0 (Ethernet) RX packets 1112 bytes 1379724 (1.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6226 bytes 1221527 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth101c5a4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::a0a3:13ff:fe2a:f801 prefixlen 64 scopeid 0x20<link> ether a2:a3:13:2a:f8:01 txqueuelen 0 (Ethernet) RX packets 163 bytes 19923 (19.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5303 bytes 968467 (945.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth1defc4b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::9018:2cff:feeb:400 prefixlen 64 scopeid 0x20<link> ether 92:18:2c:eb:04:00 txqueuelen 0 (Ethernet) RX packets 2869 bytes 69385968 (66.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12127 bytes 1746656 (1.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth2bb588f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::48b8:bcff:fe90:6205 prefixlen 64 scopeid 0x20<link> ether 4a:b8:bc:90:62:05 txqueuelen 0 (Ethernet) RX packets 49 bytes 4003 (3.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5175 bytes 922882 (901.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth3763cde: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::7cd8:1eff:fe23:281d prefixlen 64 scopeid 0x20<link> ether 7e:d8:1e:23:28:1d txqueuelen 0 (Ethernet) RX packets 25 bytes 1846 (1.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5201 bytes 920114 (898.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth3cafa97: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::1c07:4bff:fe12:a763 prefixlen 64 scopeid 0x20<link> ether 1e:07:4b:12:a7:63 txqueuelen 0 (Ethernet) RX packets 26 bytes 1916 (1.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5160 bytes 916304 (894.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4f334c3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::4e2:87ff:fe56:d56b prefixlen 64 scopeid 0x20<link> ether 06:e2:87:56:d5:6b txqueuelen 0 (Ethernet) RX packets 25 bytes 1846 (1.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5172 bytes 917296 (895.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth76cf176: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::9877:22ff:fe84:4ac9 prefixlen 64 scopeid 0x20<link> ether 9a:77:22:84:4a:c9 txqueuelen 0 (Ethernet) RX packets 54 bytes 4585 (4.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5165 bytes 922327 (900.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth917b0fd: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::6c33:fcff:fe67:753f prefixlen 64 scopeid 0x20<link> ether 6e:33:fc:67:75:3f txqueuelen 0 (Ethernet) RX packets 7002 bytes 6963248 (6.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2978 bytes 562652 (549.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb9e6800: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::d823:7cff:fe26:bc50 prefixlen 64 scopeid 0x20<link> ether da:23:7c:26:bc:50 txqueuelen 0 (Ethernet) RX packets 272845 bytes 24683640 (23.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 245238 bytes 521066078 (496.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethc205716: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::a85b:3ff:feea:fac8 prefixlen 64 scopeid 0x20<link> ether aa:5b:03:ea:fa:c8 txqueuelen 0 (Ethernet) RX packets 92098 bytes 8838175 (8.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 73810 bytes 7836864 (7.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethd7569b0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::c1b:94ff:fe00:382d prefixlen 64 scopeid 0x20<link> ether 0e:1b:94:00:38:2d txqueuelen 0 (Ethernet) RX packets 4231337 bytes 4417078024 (4.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1232190 bytes 160587844 (153.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethdbb5ea1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::60a9:2ff:fec8:b817 prefixlen 64 scopeid 0x20<link> ether 62:a9:02:c8:b8:17 txqueuelen 0 (Ethernet) RX packets 25 bytes 1846 (1.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5109 bytes 912146 (890.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:4f:9e:e4 txqueuelen 1000 (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 wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420 inet 10.253.0.1 netmask 255.255.255.255 destination 10.253.0.1 inet6 fc00:253::1 prefixlen 128 scopeid 0x0<global> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 3704 bytes 429384 (419.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11373 bytes 13111268 (12.5 MiB) TX errors 9 dropped 0 overruns 0 carrier 0 collisions 0 unraid-diagnostics-20230709-1748.zip Quote Link to comment
JorgeB Posted July 10, 2023 Share Posted July 10, 2023 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. Quote Link to comment
namida Posted July 10, 2023 Share Posted July 10, 2023 22 minutes ago, JorgeB said: 尝试关闭所有浏览器窗口，然后在几个小时后打开它，看看 GUI 是否启动，如果是，请再次关闭浏览器并继续重新测试。 I tried different devices, devices that did not open the browser just after booting up, Android, etc., all showed that they could not be loaded (there was no error message in the browser, this problem has appeared since I updated unraid on the 6th. And I just entered The diagnostics command is not available. The ssh interface has been stuck, and it will not show that the log collection is complete after waiting for an hour. So I can only provide yesterday’s log files (helpless I just restarted unraid and it's definitely accessible now, but I'm not sure if it will happen after a while Quote Link to comment
ljm42 Posted July 10, 2023 Share Posted July 10, 2023 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 Quote Link to comment
namida Posted July 19, 2023 Share Posted July 19, 2023 On 7/11/2023 at 12:39 AM, ljm42 said: 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 thank you Quote Link to comment
Recommended Posts
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.