ljm42

> If I SSH to my server and run `diagnostics` it just hangs... How long do you wait? Most of the commands diagnostics runs have 30 second timeouts, so if 5 commands have issues that would add 2.5 minutes. Let it run for say 10-15 minutes before killing it to see if it is able to gather diags

Can you show the output of: ls -al /boot/config/wireguard/

Nothing nefarious here, just folks trying to help. One person was going off the release notes and said "nothing changed". Another person realized a change they made did affect NFS but they forgot to list it in the release notes. Diagnostics are a critical part of the troubleshooting process. We ask for them because it helps understand what the problem is so we can reproduce it. We don't have time to play 20 questions to get the right details, if someone refuses to provide diagnostics then it often means their issue can't be resolved until someone else has the same issue and provides them, looks like that is what happened here. BTW, much of Unraid is available in our public repo: https://github.com/unraid/webgui You can match up commit dates with the 6.12.1 release to see the exact changes if you are interested.

Instructions to manually upgrade/downgrade are here: https://docs.unraid.net/unraid-os/manual/upgrade-instructions#manual-upgrade-or-downgrade Please test again when Unraid 6.12.2 is available.

This sounds like something that is going to take a bit of back and forth, not ideal for a release thread. Your best bet is to start a new thread and be sure to upload your diagnostics.zip (from Tools -> Diagnostics)

Sorry, I am realizing this is 6.9.2 (I just added that to the title). It has been years since most people have looked at that, especially with the version customized for nvidia. You might have luck booting in safe mode, or reverting to stock Unraid 6.9.2 rather than the custom nvidia version. Maybe someone else will have more specific advice. Ultimately you'd want to upgrade to the current release to get back into a supported environment.

6.9.0-beta22 is really old, I would not go anywhere near that or its config folder. Stick with your current version and current config folder. In that config folder, carefully edit ident.cfg and change: USE_SSH="no" to: USE_SSH="yes" Then boot the system. With that change you should be able to SSH to the system and run 'diagnostics'

I don't know

The webgui needs to work on a variety of screen sizes and the search bar takes up a significant amount of space. There are no additional mouse clicks with this method, you click once on the icon and then start typing. Or you can keep your hands off the mouse entirely and press CMD/CTRL-K. I don't see this changing back.

This is an old thread so the UI has changed a bit. You can now press the search button in the toolbar, or press CTRL-K

This is safe. Updating plugins before rebooting into the new OS is a good idea, doesn't matter if that is before or after you download the new OS to the flash drive.

From the 6.12.0 release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.0

Every time someone types "diagnostics" in the forum, it generates a link to https://docs.unraid.net/unraid-os/manual/troubleshooting/#system-diagnostics

Thanks for the help. If you are able to live without the webgui for a bit, @bonienl might have more questions for you when he comes online. But TBH there is probably enough info here so if you need to get the webgui back ASAP, here is how to revert to 6.12.0: https://docs.unraid.net/unraid-os/manual/upgrade-instructions#manual-upgrade-or-downgrade

Would you mind typing: cat /etc/nginx/conf.d/servers.conf and copy/pasting the result back here?

And `start` didn't report any errors? Would you mind uploading a new set of diagnostics so I can see if there are errors in the syslog after running that command?

@Juise99 This may help: https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735

Are you able to get to the console of the running system, using telnet, SSH or a local keyboard/monitor? If so, please run: /etc/rc.d/rc.nginx renew and let me know if that solves the problem

> IIRC something that used an older OpenSSH could cause that. The "extra" directory on the flash drive includes this: openssl11-solibs-1.1.1t-x86_64-1.txz If that was installed via Nerd Tools, I'd remove it. If you put it there manually, delete it. Then reboot.

Yes, copy everything from previous The release notes do mention some steps to do if you downgrade, but I'd guess the system didn't boot far enough to need them. Before doing that though, would you mind taking a picture or video of what happens when booting and posting it here? Right now there isn't much to go on.

Fix Common Problems has the answer: Fix Common Problems: Error: macvlan call traces found See this from the 6.12.0 release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.0#call-traces-related-to-macvlan

This is part of a call trace related to macvlan. See this part of the 6.12.0 release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.0#call-traces-related-to-macvlan

Changed Status to Solved

Changed Status to Retest

Please retest in 6.12.1