pXius

You can roll back to ver 2. here. https://forums.unraid.net/topic/40756-support-linuxserverio-sabnzbd/?do=findComment&comment=884284 But you'll probably need to change your flow going forward.

If you're using Authentication version 3 breaks the ability to log in. You get an HTTP 500 error. SABNZBD forum says it will be fixed in the next version. In the meantime, disable auth, or use your reverse proxy's HTML auth. Alternatively, roll back to version 2 by pasting linuxserver/sabnzbd:2.3.9-0ubuntu1jcfp218.04-ls67 into you template's repository field, instead of linuxserver/sabnzbd:latest Link to the thread. https://forums.sabnzbd.org/viewtopic.php?f=2&t=24885

Did you ever resolve the issue? I'm having the same problems using a Netapp X2065A-R6 HBA and a DS4246. At first I thought it was being caused by a bad interposer, but after reading your thread and having it happen to a second drive, I'm not so sure. I'm considering removing all the interposers and running straight SATA. I've done this in the past but I get issues with drive detection in unRaid on 8TB+ drives when I reboot or power cycle without interposers. edit: UPDATE Ok, I've played around a bit, using "new config" and "parity is valid" to move drives around and add/remove interposers. Interposers changes the drive name, hence the "New Config". Anyway, I'm starting to think I had bad interposers on the drives that got kicked. Having a bunch of extra's, I replaced the interposers on those drives and so far everything seems fine. In a perfect world I'd just not use interposers at all, because I lose most of the smart data, including drive temps and the ability to properly spin up and down (temps did work for awhile but stopped a few updates back), but without interposers I have a hard time detecting drives that are 8TB's and larger. Sometimes I need to replug those drives once or twice before they're detected after a reboot. Interposers solves that issue. To save myself all the headache I've ordered an LSI card and the appropriate cable which will hopefully allow me to run the SATA drives without interposers once again. Looking forward to having SMART data again.

EU Endpoints working again. Quick question, Is there a way to get the webui to function if you're using a custom br ip? When I use a custom IP my web ui no longer loads. Bridge obviously works just fine. Also, I AM using a server that supports port forward. Sweden. Tried Frankfurt as well. PS. Disabling VPN lets web ui function even on a custom IP. I've tried a ton of things but I'm at a loss.

Been pulling my hair out of my head thinking I messed up somewhere. Great....

I'm looking forward to the multiple cache pools. I'm currently running my VM's and Docker containers off unassigned devices because my cache drive exclusively handles the decompression on incoming downloads. Even with an NVME drive, I get media playback issues if I decompress incoming downloads while streaming, and that's with CPU pinning. The drive is the bottleneck. Having multiple cache pools will make life so much easier especially for docker apps that don't like running off any directory that isn't /mnt/user like musicbrainz. As for larger arrays with better redundancy; you could run unRaid on ESXi or Proxmmox and set up ZFS pools to pass through as virtual drives to unRaid. That way you can haz all the storage in raidz (see what I did there) and still use the unRaid array in the way you're used to. The only downside with something like ZFS is that it's best to start off with all your storage drives and not adding single drives over time. I also have no idea if you can pass something like a GPU from say Proxmox to unRiad and then from unRiad into a docker/VM, and whether there's a performance penalty for doing so.

Awesome! Thanks!

Just ran into the error as well. Is there an easy way to roll back to an older release?

Having similar issues. Installed musicbrainz for the first time, can't log into web gui. Just times out. Using port 5000. I've tried using a custom IP for the docker as well as bridge. Musicbrainz itself functions as I can see it doing database work as folders are created etc. Just can't access the web gui. Using Unraid 6.8.2 My appdata is hosted on a Unassigned device using RW/slave. EDIT: Solved - Sort of. It seems that musicbrainz doesn't like being run in unassigned devices. I was able to get it working using /mnt/cahce/musicbrainz/ instead of my normal app data location. My new issues is that Picard can't use my mirror server. It requires a Authentication key only generated by the master site.

Was on 6.8.0- RC5 before trying 6.8.1, so just loaded RC9 out of curiosity. Will probably jump on 6.8 stable tonight.

Ok so the Nvidia 6.8.1 breaks a few things for me as well. The first is I'm guessing the driver for a Intel PRO/1000 Pt Dual Port Server PCIE NIC. So I have to use my on board networking. Not a huge issue. My bigger issue is that my Dell Perc H200 SAS card doesn't work with this build, meaning half of my array isn't detected. Rolled back to 6.8.0 RC9 for now and all is working. Thanks for the awesome work!

I'm having an issue with the BitWarden container. Version 1.9.1-8be2ed62 Unraid Version: 6.8.0-rc 3 Regardless of what I set the port to in the template, it will keep using port 80. This makes my port forwarding tricky considering port 80 is already being used. Any ideas?

Is there any sort of Trim Support for SSD's in Unassigned Devices? I run my Dockers/VM's off a NVME SSD in Unassigned Devices as my normal ssd cache pool is very heavily utilized. Thanks!

You having the same issue I had, how are you trying to connect to your WEBUI? On what IP range is your Deluge and what IP range is the mashine you are trying to connect from? Also, give your Deluge an IP other than that of the Unraid machine.

Download the Firefox container from the APPS section in unraid. If your Deluge docker is using the same IP as your host unraid machine, then use the same IP for firefox as well. If your deluge docker has an ip different from that of the host machine, you will need to use a different IP for the firefox docker as well. It's a security thing. After that you can access the Deluge docker via the firefox docker by entering the deluge IP in the firefox address bar. When outside your network you'll need to access your local network via a VPN of sorts. My router has a openVPN server as a feature, so I just connect to that when away from home.