Daxter

Mine was actually cp /boot/config/plugins/unbalance/unbalance.hist /boot/config/plugins/unbalanced/unbalanced.hist

Ok so I can start unbalanced but the button to open the WebUI is now gone? Is that what you meant by only serving it on the http port? My server opens in https.

Yeah, it's still doing it on mine when over https

This is what was happening for me, didn't realize it was opening on the wrong port.

@jbrodriguez I can't seem to get into the WebUI of the new plugin. Do I have to uninstall the old one for the new one to work?

Awesome, thanks man.

@jbrodriguez Same question as the previous one, but with the Scatter function. Can I scatter while Plex is running?

I need to transfer 4.8TB, and the drive I'm going to have 6.7TB free, so yeah space shouldn't be an issue.

Hi, I have an unBALANACE question that I saw a vague answer of somewhere else and wanted to get more details. Can I keep Plex running while using the Gather function to move 4.8TB of data from 2 drives to 1? It's all video files, and I want to move them from my disk1 & disk2 to disk3, but when I tried it unBALANCE said it would take 20 hours. I have several friends and family who use my Plex daily and I would prefer not to take it offline for that long. Thanks in advance

Update on this topic. The issue came back within a week or so of it going away again, but I wondered if upgrading from Unraid 6.11.5 to 6.12.4 would fix it, and it has for about a week now. No idea what caused this, nothing changed on my router so..... Yeah. Maybe restarting the server fixed it? I don't know.

I didn't realize there was an unraid connect section, thanks. Funny story, I still get this error when checking... But I am connected remotely right now.

Does it still work natively with Unraid Connect? I like using Unraid Connect and if it doesn't I'd like another answer to this issue.

For some reason, even though UPnP is on and working, and the port is forwarded, I still can't remotely access my server. Attached diagnostics too. Any help would be appreciated, thanks! tower-diagnostics-20231017-1228.zip

Quick update: Was waiting until after Thanksgiving to do anything more since it was stable with tdarr turned off. I had done this before and found I only needed to enable the "Typical current idle" setting to fix my issue before. I went to change the RAM speed from 3600 down to 2667 but decided to double check the PSU setting.. and it was reverted back to auto! So we'll see what happens now with it put back to "Typical current idle". Edit so as not to bump (Nov 30th 2022): Setting PSU back to typical current idle didn't seem to fix the issue like last time, but also setting RAM to proper settings (In my case RAM set to 2667Mhz) per the thread mentioned did seem to fix it.

Here's another log, crash was around 22:11. I'm gonna try changing nvidia drivers to production branch from latest. syslog-192.168.1.42_2022-11-22_22.30.txt