hawkcfa

I'm not seeing any evidence of a storm in the last 18 hours. And using those outputs there isn't anything that is filling up the logs. So it seems for me, the storm isn't happening at least now. How long after reboot did you lose GUI?

The USB backup I have is from about a week ago when I changed from booting via USB to booting from an internal hard drive. But I must of got lucky somehow, I powered down my server for about 5 minutes, reseated the USB and the connection to the internal boot hard drive and powered back up and luckily got the GUI back. I have no idea if the reseat of them had anything to do with it or not but after powering back up the GUI is up and running. Nothing I did make sense of why it would interfere with the GUI or help it get up and running.

DIag zip unraid-diagnostics-20260717-1423.zip

I'm having an issue and I have no idea what to do. I rebooted my Unraid server because I was moving up in the rack. Now when I boot up the server, I have no GUI. When I go to http://x.x.x.x in my browser I just get This site can’t be reached. x.x.x.x refused to connect. I tried rebooting and select to boot it to GUI using a local keyboard and I just get a _ at the top left of the screen. I reboot it into Safe Mode with GUI and I get that localhost cannot be reached. localhost refused to connect. One thing I do notice is in safe mode it is defaulting to HTTPS instead of HTTP and even if I turn of HTTPS-On-Always on the FF browser, it still goes to HTTPS. From what I can tell, my dockers, VMs and array all start up, but for some reason I can't get into the GUI anymore. I really don't know what to do or how a reboot did this. I'm so-so when it comes to linux CLI, but I can get into the server via CLI.

My MongoDB1 won't start anymore. I tried to upgrade to unraid 7.2.0 and it didn't come up, so I went back down to 7.1.4 and it still won't come back up. Any idea's what I need to do? {"t":{"$date":"2025-11-02T09:13:34.550-06:00"},"s":"F", "c":"CONTROL", "id":20573, "ctx":"initandlisten","msg":"Wrong mongod version","attr":{"error":"UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: Location4926900: Invalid featureCompatibilityVersion document in admin.system.version: { _id: \"featureCompatibilityVersion\", version: \"7.0\" }. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility. :: caused by :: Invalid feature compatibility version value '7.0'. Expected one of the following versions: ''8.2', '8.1', '8.0'. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility.). If the current featureCompatibilityVersion is below 8.0, see the documentation on upgrading at https://docs.mongodb.com/master/release-notes/8.0/#upgrade-procedures."}}

Just upgraded to 7.2.0 from 7.1.4 and MongoDB broke. There is no update for MongoDB docker yet. Doesn't seem 7.2.0 isn't compatible with the MongoDB Docker. {"t":{"$date":"2025-11-02T09:13:34.550-06:00"},"s":"F", "c":"CONTROL", "id":20573, "ctx":"initandlisten","msg":"Wrong mongod version","attr":{"error":"UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: Location4926900: Invalid featureCompatibilityVersion document in admin.system.version: { _id: \"featureCompatibilityVersion\", version: \"7.0\" }. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility. :: caused by :: Invalid feature compatibility version value '7.0'. Expected one of the following versions: ''8.2', '8.1', '8.0'. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility.). If the current featureCompatibilityVersion is below 8.0, see the documentation on upgrading at https://docs.mongodb.com/master/release-notes/8.0/#upgrade-procedures."}}

I had the same problem! Same fix too. Thx for the info.

I have the same problem. Just updated to 6.12.0 and the same browser width that had 3 columns on 6.11.5 is now only 2 on 6.12.0. I tried resetting the Dashboard and have even done clearing of my Chrome browsing data. If I zoom the tab out to 90% instead of 100% then I get 3 columns back but that seems kind of stupid when I had 3 on 6.11.5 but only 2 on 6.12.0.

After shutting down Dockers and VMs disabling and re-enabling IPv6 then restarting the unraid-api, it came up on IPv6. <-----UNRAID-API-REPORT-----> SERVER_NAME: UNRAID ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 3.0.1 UNRAID_API_STATUS: running API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: hawkcfa CLOUD: STATUS: [ok] IP: [2606:4700:20::681a:375] MINI-GRAPH: STATUS: [CONNECTED] SERVERS: ONLINE: UNRAID[owner="hawkcfa"] OFFLINE: ALLOWED_ORIGINS: http://localhost, https://localhost, http://unraid.local, http://IPV4ADDRESS, http://unraid, https://connect.myunraid.net, https://staging.connect.myunraid.net, https://dev-my.myunraid.net:4000 </----UNRAID-API-REPORT----->

The Unraid server IPv6 broke. I couldn't ping mothership.unraid.net from the server when it was using IPv6. But I could ping mothership.unraid.net's IPv6 IP from other workstations on my network. root@UNRAID:~# ping mothership.unraid.net PING mothership.unraid.net(2606:4700:20::681a:275 (2606:4700:20::681a:275)) 56 data bytes From 2604:2d80:500a:6200::949 icmp_seq=1 Destination unreachable: Address unreachable From 2604:2d80:500a:6200::949 icmp_seq=2 Destination unreachable: Address unreachable Flushed the IPv6 on the interface and restarted the API root@UNRAID:~# ip -6 addr flush dev br0 root@UNRAID:~# unraid-api restart Via v4 I can get to mothership.unraid.net. And it is showing connected and online on connect.unraid.net root@UNRAID:~# ping mothership.unraid.net PING mothership.unraid.net (172.67.69.176) 56(84) bytes of data. 64 bytes from 172.67.69.176 (172.67.69.176): icmp_seq=1 ttl=54 time=17.6 ms 64 bytes from 172.67.69.176 (172.67.69.176): icmp_seq=2 ttl=54 time=15.1 ms 64 bytes from 172.67.69.176 (172.67.69.176): icmp_seq=3 ttl=54 time=14.6 ms 64 bytes from 172.67.69.176 (172.67.69.176): icmp_seq=4 ttl=54 time=15.9 ms --- mothership.unraid.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 15069ms rtt min/avg/max/mdev = 14.644/15.812/17.627/1.133 ms <-----UNRAID-API-REPORT-----> SERVER_NAME: UNRAID ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 3.0.1 UNRAID_API_STATUS: running API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: hawkcfa CLOUD: STATUS: [ok] IP: [104.26.2.117] MINI-GRAPH: STATUS: [CONNECTED] SERVERS: ONLINE: UNRAID[owner="hawkcfa"] OFFLINE: ALLOWED_ORIGINS: http://localhost, https://localhost, http://unraid.local, http://IPV4ADDRESS, http://unraid, https://connect.myunraid.net, https://staging.connect.myunraid.net, https://dev-my.myunraid.net:4000 </----UNRAID-API-REPORT-----> I still can't ping outside my internal network via IPv6 from Unraid. So it is only band-aided to connect via v4. It still can't/won't connect via v6 because the Unraid server itself IPv6 is broken. I have VMs on the Unraid that get IPv6 from my DHCPv6 server and they are working just fine. So the problem is definitely with IPv6 on Unraid itself. It really is acting like the Unraid server has lost or unable to implement the default route for v6.

I do have a firewall, but have not made any changes to the firewall or any rules in several months. Long before the API stopped working. My DNS servers on my internal network are Pihole's but I have turned off the blocking of them to allow queues to go directly to CloudFlare or OpenDNS's DNSSEC. Got another update to Unraid Connect. Now version 2023.04.25.1448. Restarted the API again after the new update and still no dice. <-----UNRAID-API-REPORT-----> SERVER_NAME: UNRAID ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 3.0.1 UNRAID_API_STATUS: running API_KEY: invalid MY_SERVERS: authenticated MY_SERVERS_USERNAME: hawkcfa CLOUD: STATUS: [error] MINI-GRAPH: STATUS: [PRE_INIT] ERROR: [API Disconnected] SERVERS: ONLINE: OFFLINE: UNRAID[owner="hawkcfa"] ALLOWED_ORIGINS: </----UNRAID-API-REPORT----->

Didn't help me. Running 6.11.5 and Unraid Connect 2023.04.25.0813 and still have the Unraid API Error Network:Unable to connect. Server shows offline on connect.myunraid.net as well.

same issue and restarting the API or unregistering and re-registering with unraid.net has not fixed it for me.