Elvin

Unfortunately this did not work for me.

I can confirm the same happened to me. If memory serves, 6.11.5, 6.11.4, 6.11.2 all have the same issue. tower-diagnostics-20221123-2030.zip

OK after trying everything, I refromatted the USB drive and used Unraid USB Creator to create a brand new RC4, then copied files under config to the newly created drive, excpet these two files: docker.cfg domain.cfg Now docker container updates actually pulled down new versions, after updating all containers and check for new version doesn't report false updates any more. If anyone is interested, here are the content of my 'old' docker.cfg DOCKER_ENABLED="yes" DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker.img" DOCKER_IMAGE_SIZE="30" DOCKER_APP_CONFIG_PATH="/mnt/user/appdata/" DOCKER_APP_UNRAID_PATH="" DOCKER_CUSTOM_NETWORKS="eth1 " DOCKER_LOG_ROTATION="yes" DOCKER_LOG_SIZE="50m" DOCKER_LOG_FILES="1" DOCKER_AUTHORING_MODE="no" DOCKER_USER_NETWORKS="preserve" DOCKER_TIMEOUT="10" DOCKER_NETWORK_TYPE="1" For reference, the newly created docker.cfg has only one line: DOCKER_ENABLED="yes" What might be interesting is this line: DOCKER_CUSTOM_NETWORKS="eth1 " I do have two nics but eth1 is disabled, only running eth0 now. Not sure if that's related.

Can confirm that after 6.10 I won't be able to see my Unraid servers. 6.9 is fine. Upgrading from 6.9 or create a brand new 6.10 usb stick are the same, disppears from Network in Win 11.

That's a legitimate guess and those challenges are the PITA. And yes 192.168.50.1 is a VM running OpnSense on another Proxmox box. We have some weird setup to deal with those challenges and I just double checked they are working correctly. With the same setup I can access docker hub just fine. I also tried removing a container (also remove image), and I could install it again just fine, which is safe to assume I have proper access to docker hub? Yet the newly installed container reports update available right after. How does Unraid know if a container has update? What happens when Check For Updates is triggered? Does it go through all containers and check with docker hub one by one? Could there be any kind of cache involved in this process?

attached tower-diagnostics-20220323-2054.zip

Tested the new version of CA and the issue is gone. Thanks to @Squid for the quick fix.

Thanks @Squid Yes this finding is inline with my tests, all tested Windows 11 instances happen to run browsers all in Chinese, and Windows 10 and other linux distros are in English. I also want to add that I just checked again with my friend, he's running in Chinese with CA 2022 03 17a but not experiencing this issue.

regarding the #3 console output, below is what I got from doing this: Open unraid dashboard, wait for it finish loading, right click - inspect - console, then navigate to App page, wait for it, then got this screenshot. btw CA versions is: 2022.03.17a Result checkPlugin community.applications.plg.txt

Firstly appreciate for the suggestions. Below are the feed backs: #1. Tried, didn't work. I even tried a fresh install Windows 11, goes directly to the page without touching anything, and got stuck. #2. Just tried. Still no luck. I noticed the community.applications.cfg file didn't regenerate itself, is that normal? #3. That's not possible, as the browser enters a completely no response state. No response to any mouse clicks at all. Sometimes it gives a prompt "This page is not responding". #4. I'm fine to setup a team viewer for you in the fresh installed VM, if that works for you? I know not all windows 11 has this issue, one of my friend has a nearly identical setup as mine, same Windows 11 desktop / Unraid server, same software and hardware, and he has no issue at all. But for me, for my particular Unraid box, it seems doesn't like to be viewed from Windows 11, at least that's my testings shows so far.

OK I think I'm getting somewhere, one common thing across all the devices that I have issue with is they are all running Windows 11. To verify this, I installed a Win 10 VM and a Win 11 VM both on the very unraid box itself. Win 10 opens the page easliy, but the fresh installed Win 11 still got stuck. I also tried 3 different linux distro on my desktop(which is having issue with Win 11), all worked fine. Can anyone who has the same issue help to verify this? Were it on Windows 11 too?

Now this is getting interesting, I just happened to find out that it works fine on my laptop even my phone. It just freezes on my desktop! No matter what browser I'm using. I don't see much differences between my desktop and other devices despite those are on wifi, so I tried disable all wired nic on my desktop and switched on wifi, still wouldn't work. All DNS & Gateway settings are all the same. Update: Tried with another laptop, which has never accessed the GUI before, and it freeze too!

Oh no it's happening again, so it wasn't IPMI plugin. I'm starting to wonder if might be more related to docker. Do you have the other issue that many containers reporting false updates?

OK after removing IPMI plugin the App page works. Do you mind giving it a try?

Yeah I was meant to say this is certainly not a browser compatibility issue, otherwise it wouldn't have worked with array stopped. Just tried setting safemode to default in Syslinux config and reboot, it caused both of my onboard i211 and pcie RTL8125 not connecting, not sure what happened. Need to try with a kb and monitor tomorrow when I can have physical access to the box. Meanwhile tried to remove some random plugins, no luck so far.

and I'm not using FF, but Chrome and Edge, latest version, both failed.

Same here. RC2 was fine, this issue starts with RC3

OK FCP updated and the error is gone.

The only content in that file is this line include /syslinux/syslinux.cfg Wonder is it needed? or can I just remove the file?

I got this message after upgrading to 6.10.0-rc2 ERRORS FOUND /boot/config/syslinux.cfg corrupted SUGGESTED FIX Your flash drive has possible corruption on /boot/config/syslinux.cfg. Post your diagnostics in the forum for more assistance I'm posting a diag as suggested. tower-diagnostics-20220309-1257.zip

+1 for opnSense

Very glad to see this and frankly it restores my confidence in unraid (the software and the community as a inseparable whole). Hope this situation ends up making things even better.

This is sad, very sad only. unRAID is a unique product, but it's the community what really makes it shines. As a ordinary user, what really makes me feel safe is not that i'm running a perfect piece of software(it's not, no software will ever be), but having a reliable community always have my back when I'm in trouble, and constantly making things better. I'm not in a place to judge, but I do see some utterly poor communications. This could have been a happy day yet we are seeing the beginning of a crack. Guess who gets hurt? LOYAL USERS! Guess who gets hurt after users are hurt? Please, look at the bigger picture, fix it when it's not too late. Don't bury what together you have archived just for miscommunication. It's not worthy.