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/

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

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

Please start a new thread for your issue rather than reviving one from last year. Be sure to include your diagnostics. Since you don't have access to the webgui, use SSH, telnet or a local keyboard/monitor and type "diagnostics". This will save the file to the "logs" folder on your flash drive where you can then grab them and upload to your new post.

In recent versions, the Unraid webgui *always* binds to the SSL port (defaults to 443). If you need something else to be on port 443, then you need to change the port that the webgui uses. This comment explains how to fix an SSL port conflict (everywhere it says "445" you can substitute "443"): https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735

Please follow the directions here to manually upgrade to 6.12.1: https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade If you continue to have trouble after the upgrade, from telnet, SSH, or a local keyboard/monitor, sign in and type "diagnostics", it will put the file in the "logs" directory on the flash drive. You can then upload those to a new thread in general support where you describe the issue. It is very difficult to troubleshoot in the release thread, so a new thread is best.

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

Please see https://docs.unraid.net/connect/remote-access

We need to see the logs in order to troubleshoot. In the current version of the plugin, the Settings -> Management Access -> Unraid Connect tab has instructions on how to send those

Totally agree, when we are ready for folks to start using the api directly we will definitely have documentation