strike

It's actually real easy to do this and yes you're right, the answer lies within the logs. Just stop the delugevpn container then do a search for a movie/show in sonarr/radarr or whatever then look at their logs. You should see they are unable to search for anything and if you start delugevpn again everything should be working.

Have you checked Q6 here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

lol, well glad you got it sorted

Please check your login credentials and make sure they only contain a-z, A-Z, 0-9 characters. Also make sure your subscription is active and have not expired.

What about if you click the container and select "logs", can you paste the output here?

Please take a look at link in the second post above yours.

Just map a directory in RAM to a directory inside he container, then choose that directory in the emby transcode settings. I have mine mapped like this:

Afaik the LabelPlus plugin is a more enhanced 3rd party version of the label plugin included with deluge. I only need the label plugin which is included in v1. Are you saying this plugin doesn't work either?

I haven't really been following this thread after the v2 release, but can anyone using v2 confirm if the label plugin is working? That's really the only plugin I need.

https://forums.unraid.net/topic/53520-support-linuxserverio-ombi/?do=findComment&comment=771317

Known issue, fixed in next unraid release: https://forums.unraid.net/bug-reports/stable-releases/dockers-wanting-to-update-but-dont-in-the-end-r618/

Yes, that's the one. I've haven't tested it but I think if you have this you'll be fine even on the first big transfer (I think). But I want to rephrase my previous statement a little. In my previous statements I've been saying this is an issue only on the first big transfer, but that's not correct. Once again to be clear this issue happens if your split level is not set to "Automatically split any directory as require?" and you're trying to rsync a large batch of files. It don't even have to be that large of a transfer to trigger this. What happens when you do a rsync transfer is that rsync will create ALL the folders on the first available disk according to allocation method BEFORE transferring any files. Split level is about trying to keep files together so they don't end up on different disks, so if you have the wrong split level unraid will try to force some files to a disk which is already full, trying to keep the files together according to set split level. Since this is just a backup I wouldn't worry about where files end up anyway. So if you take those two paragraphs and put them together you'll see that this issue can happen on even a small transfer. Lets says you have transferred all your files and in 2 months time you have 500 new folders with pictures in them, roughly 5 gig in total. Which you want to back up. The next disk in line to get new files based on allocation method is disk 3, which only has 2 GB available space left. Your split level is set wrong and because of that and this rsync issue all 500 folders will be created on disk 3, even if some of the files in those folders won't make it to disk 3 because it's completely full by the time rsync gets to them and it won't choose another disk either because split level goes before everything, so the transfer will just fail with out of space errors. So for this to be set it and forget it you will have to choose the first split level like mentioned, you will have to set a min free limit so that unraid will choose another disk if that disk has less space then the limit. Since this is just a backup I think I would set the allocation method to fill up. If you're not concerned about evenly filling the disks that is. I try to keep at least 30 GB of available space left on all my disks.

The password for the webui is "deluge". The auth file is for configuring the user/pass for connecting to the deluge daemon (thin client).

Any news on adding the geoip2 module? I see from this link that @aptalca submitted a PR https://gitlab.alpinelinux.org/alpine/aports/issues/10068 Edit: Maybe I should try and update the container, clicking the PR link I see it was added to 3.10. Yup, update was all that was needed. I love you guys! 😍

I was under the impression that it would always speed up writes (assuming all disks has good read performance) but I haven't really used turbo write so I'll take your word for it