Funny718

I see thanks, but still doesn't seem to answer my question as to what cause my cache drive to jump up from 11.49 GB up to 75.7 GB and how can I fix this.

Ah I see I currently have all my container setup like this example (/mnt/cache/appdata/radarr) as I thought that would be the fastest and the best.

I have it currently set to 20 GB at the moment.

I see and that makes perfect sense I do remember setting it up this way, I just uninstalled Unifi reborn Controller hoping that would resolve my issue but no joy, is there anything else I could do to fix this issue? I think my unifi reborn controller was filling up the cache drive so I uninstalled the container and deleted folder form appdata as well.

I think I found something du -sh /mnt/cache/system/docker/* 35G /mnt/cache/system/docker/docker.img I did install unifi reborn and a new version of nextcloud

Hey T0ruqeWr3nch thanks this is the output I received :~# du -sh /mnt/cache/* 22G /mnt/cache/appdata 0 /mnt/cache/domains 0 /mnt/cache/isos 36G /mnt/cache/system is this normal?

Normally my cache drive sits anywhere from 11 - 13 GB after mover runs, but all of a sudden it just keeps filling up and am sitting at 80.9 GB at the time of writing this post and wondering how I can get it to go back down to normal. I attached my diagnostic file hopefully some one smarter than me can some insight as to what I screwed up here. Thanks in advance for any and all help reptarflixs-diagnostics-20240206-1523.zip

Hey just want to let everyone know that the only way I was able to solve this was by switch over to swag. And wow I'm amazed at how easy it was to setup. Well using video from ibracrop on YouTube. Lol love them

I've got the calibre-web container running and can access it locally just fine. Problem I'm having is trying to setup a reverse proxy via (Nginx Proxy Manager) it keeps giving me an internal error. I followed janeczku gudie https://github.com/janeczku/calibre-web/wiki/Setup-Reverse-Proxy#nginx-proxy-manager to no avail and was wondering if anyone else has got this to work? I attached a pic of my npm setup can any one see where I went wrong? thanks

Ok just wanted to let everyone know that I did get this fixed, it was a permissions issue and thanks mikl for pointing me in the right direction. Remember I'm really new to unraid so when I was told to use new permissions tool that's what I used! But what actually fixed it and might have been what mikl meant this whole time was for me to use Docker Safe New Perms. Which is in the same tools tab once I ran that my HW transcoding was working like normal. Big thanks again Mikl Remember anyone having a similar problem use Docker Safe New Perms not new permissions tool. And that should fix your issue best of luck.

Still new but assuming that you meant the new permissions tool founded in tools tab, I used it on both the appdata folder and on the docker folder but still did not fix the HW Transcoding issue in plex! Thank you for you're help though really appreciated, I'll just revert back and wait and hopefully someone else might have and idea.

Any one else having the same issue?

Hey Guys, Like the title says when I updated from 6.9.2 to 6.10.0 Plex Transcoding IGPU stopped working!!! Recently updated to 6.10.0 and 6.10.1 and for some reason Plex HW Transcoding isn't working, as soon as I rolled back to 6.9.2 Plex HW Transcoding started working as normal. as I am still very new to this amazing OS is this a know issue and if so is there a work around yet? I'm using the official Plex docker image With PlexPass founded on the community apps page, but I also tried bin-hex PlexpPass and linuxserver's Plex and Hotio's Plex image and could not get any of those to work with Plex HW Transcoding. Oh gosh one last thing I also checked that /dev/dri return what was expected on both 6.10.0 and 6.10.1 and it did so I can verify that's still working. thanks for any help in advance. FuNnY718