Jake G

It was the tailscale plugin. Even with it configured correctly for 6.12. Removing it allowed me to use my server normally, reinstalling it immediately crashed the webui. Guess I'll wait and see what happens next.

I am running into similar issues after upgrading to 6.12.4. All plugins removed or updated. As soon as the array is started in Maintenance Mode, Normally, with docker on and off, etc. The only way I am able to access the webGUI after array start is within safe mode without plugins. I thought I'd held off long enough to upgrade to avoid breaking issues, but I guess not. I was able to get it working initially. I installed the new appdata.backup plugin. Halfway through the first backup is when issues began. Docker runs in safe mode. It is something in the plugins. I already attempted altering the SSL port suggested above. Can provide full syslogs if needed. Right now managing to get by without plugins but I can't stay this way. Shortly after Party tips & tweaks starts and you see remote shares mounting is the point where the WebGUI dies. servers.conf ungootmedia-diagnostics-20231025-1507.zip ungootmedia-diagnostics-20231025-1510.zip

I ran into this same issue also despite not having an encrypted btrfs cache drive, and switching to linuxserver config seems to have resolved it, I'll report back in a couple days if the issue persists. I'm not the person you asked, but plex is very flexible in this regard. I just stopped the official docker, and pointed the linuxserver one to my existing appdata folder and hit start.

You're right, and I wish I saw this reply earlier, I finally figured that out 3 hours ago and forgot to check back here. I hadn't paid attention to deluge versions since 2.0 never came out ( set my previous server up 4 years ago, deluge was always up to date until I stopped checking when they stopped updating). I installed 2.0 on my windows machine and got in instantly.

I am also having this issue, however I am able to access another windows machine on my network this way without an issue, so I suspect it is definitely something with the Unraid config. I've played around with switching networking to Bridge and forwarding all the ports manually, but it did not resolve the issue.