JieKie

I have the same issue, removed all plugins except for unassigned devices. rolled back to 6.10. I have some dockers using an unassigned drive for downloading. melchior-diagnostics-20221020-1810.rar

thanks, indeed the same issues. For now i have downgraded back to v6.10

melchior-diagnostics-20221020-1810.rar

So it happend again. I can't shut it down. When I ssh into the server and use poweroff i get the "The system is going down for system halt NOW!" but the server keeps running. When I use umout -a it says target is busy for most services

The issue has returned. Can I assume the unassigned devices plugin is causing issues? i'm afraid i can't download the log as the UI pages are mostly unresponsive and i will have to force restart the server. update: managed to snag the logs melchior-diagnostics-20221020-1810.zip

So far so good running only the unassigned devices and unassigned devices plus plugin. Maybe you could try monitoring with only the unassigned devices plugin. If you still have problems you can assume its this plugin.

After a forced reboot i was able to reboot into safe mode. So far i had no more issues, parity check completed. What can i do to determine if a plugin is causing issues?

I will follow this thread as I have the exact same problem for a couple of days now. Dockers themselves work fine, but i cant load the docker page. The server does not respond to shutting down, stopping the array, pausing parity check, even pressing the power button does nothing except for the "beeb". When i close a notification it pops back up after a few seconds. I had to forse shut down, problem cam back. Great server name btw.

Hhm, the ony thing i did since last time i used them (couple of months ago) was adding 2 disks, move the docker file to cache, and maybe an update. Anyway, doesn't matter, glad its ok now, thanks again.

Got it back up and running again. How is it possible this changed? My network always has been 192.168.0.0/24. I've been using these dockers for over a year, always worked. thanks a lot for the help

It's from different devices, different browsers, all in the same range. It's on DHCP but right now it's 192.168.0.20. Unraid is fixed. I tried clearing cache, incognito, etc..

it's briged

My apologies, added the log. So in short, I can't get into the UI (same for qbittorrentvpn an rtorrentvp. the regular binhex deluge works fine) supervisord.log

I have the same problem, none of the binhex vpn torrent clients seem to work. I tried removing these IP's but the problem is percisting.

Yeah, kind of. Ok, then everything checks out as it should be, nothing to worry about (except finding a new spot for my server, my little toddler is fascinated by flashing lights). I expected to just pop it back in and continue with my day. Thanks for the quick help and info!