eightysixed

I also upgraded to 6.12.10 from 6.12.9 without any issue, even though I had zero issues with .9. People smarter than I obviously fixed and changed things that needed to be implemented, so why not?

Why is this container all of a sudden using more than 50% of CPU Usage and jacking up the processor temperature to 140F? I've tried reinstalling, starting from scratch, same thing. It used to be 2% max. What am I missing here? Does anyone have any ideas? edit: Immediately disabling it puts everything back to normal, but obviously I want to use it edit2: "Not sure what happened to the support here, but I just ran into this issue as well. The solution is to check Unraid -> Settings -> Docker and make sure "Host access to custom networks" is enabled. Turning that on fixed it for me." This didn't work for me.

I had no idea. Thank you! edit: holy cow, I didn't even notice I was posting in the NerdTools thread. So easy to read over. Thanks again

So should I just go ahead and uninstall? I don't want any security vulnerabilities or things of that nature. Is it still being actively maintained?

Worked for me too! Thanks @Gragorg

I'm being alerted that there is an update for Tautulli, but on the Docker page it says "Not Available." Does anyone know how/what's going on here? Thanks!

It is sort of ironic we have all this chit-chat back and forth about unRAID being a backup or not, but literally on unraid.net, they literally call it a backup solution. https://unraid.net/backups The irony in this thread is amazing

Wait, it works in Chrome, but no longer on Safari - what am I missing here? edit: It works in Safari in Private Browsing mode. What in the world is going on? Sheesh. edit2: Cleared cache, it works again. What a weird thing.

I'm running into a weird problem out of nowhere with binhex-krusader. It won't load, I didn't change anything or update anything. Log files show: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 540 Tried restarting, didn't work. Tried full stop, then manually restart, didn't work. Tried uninstalling the entire container and re-installing. How can I fix this?