JonathanM

It's also on the plug page I'm not debating that, just telling you I made an IT10T error... ID10T. Heh.

But at least its something. Looks like a couchpotato problem, not an unraid docker problem. https://github.com/CouchPotato/CouchPotatoServer/issues/5776

SSH to your unRAID and run, docker exec -it Beets bash That should get you started. Old post resurection! ! (I can do that now im out the EU)... This didn't seem to do anything...I still have the beets Web gui appearing...but no interaction. I set the docker settings to point to /mnt/user/ as I have practised this with other dockers and worked for me. With this app do I absolutely have to specify the actual directory. It sounds like you are expecting something that beets is not. Try reading here and see if things are any clearer.

Dockers use their own self contained OS's, they don't interact with the host OS like you are implying. see here. http://lime-technology.com/forum/index.php?topic=40937.msg387520#msg387520 If your docker needs access to a particular program, it needs to be installed inside the docker container, typically by docker exec into the container and installing from there. Installing the binary in unraid isn't going to help.

Ahh, there is the major point of contention for me. I would rather know I lost all of something, than not know which items were gone until I tried to access them. Reripping disks or reloading from backups is much simpler when you know for sure which items you need. I realize this is mostly personal preference, and what causes one person distress is totally different from what causes it for another. Borderline OCD or a compulsion to be in control of as much as possible rather than leaving things up to chance is what drives my philosophy.

This makes sense. Would you separate archival stuff from dynamic stuff onto physical disks as well? Yes. It makes backups easier to manage. With each unraid disk having a standalone filesystem you only have to worry about drive sized chunks of backups instead of trying to manage backing up a user share that could span many drives. Some people prefer to scatter stuff evenly across all their drives, so if they lose a couple drives only a portion of any particular share is gone. That view makes my brain itch. My user shares are confined to only as many drives as absolutely necessary to hold them. Example, disk1 has share a, b, c because they are all small shares. disk 2,3,4 only have movies, disk 5,6,7,8 only have tvshows, etc. The movies drives get filled fillup style, the tv shows are split into ongoing vs canceled so the canceled shows can be packed to the brim while ongoing shows have breathing room.

You didn't say WHICH Saturday. ;D Are you angling for a position at limetech?

IMHO, it's much better to totally fill disks with folders of content that will be mostly static, and allow your most free drives to receive all new content. That way as disks fill up, you aren't juggling files around from disk to disk. Logically separate your archival stuff from your changing and new content.

Post your docker mappings. Does the docker have access to /mnt/user/media/downloads? I gather you got the IPT stuff figured out?

Not sure if you meant first time using docker in general, or this container, but given the tone of the question, I think this is a good place for you to start. http://lime-technology.com/forum/index.php?topic=40937.msg387520#msg387520 By default it doesn't store anything there, you tell the app inside the docker to save to the path you set in the container volume side, and it appears in unraid in the path specified on the host side. If you don't tell the app specifically where to put things and let it use its defaults, you very well may end up downloading stuff inside the docker image itself, and causing yourself headaches. Best to read the docker FAQ's I linked and ask questions if you aren't getting it. BTW, this is a common question, not silly at all, and a little tough to wrap your head around if you've never dealt with something like this before. Better to ask before you make a mess of things. Once you get it, it's simple. Before the lightbulb moment, it's tough.

Deluge 1.3.12 is what IPT shows as user agent on the peers page, successfully seeding through PIA currently. Do you have peer exchange and DHT disabled as required by IPT? (and all private trackers) Correct. Are you using the DelugeVPN container or the actual client for an OS? This delugevpn container.

Deluge 1.3.12 is what IPT shows as user agent on the peers page, successfully seeding through PIA currently. Do you have peer exchange and DHT disabled as required by IPT? (and all private trackers)

The torrents that you show seeding in deluge, how long have they been that way continuously? The IPT status isn't immediate, sometimes it can take a couple hours or more to update. I'd leave it alone, and check back with the IPT status later. Also, I'd have the torrent from this link https://torguard.net/checkmytorrentipaddress.php in your client, that way you can get an an easy update on what IP you are using.

Keep in mind anything using /mnt/user paths will not work with links, you must use /mnt/diskX or /mnt/cache paths to use links.

What is your peers status on IPT? Does it show any of the files in your client currently listed either under seeders or leechers status? As long as the file is listed in the seeders section, you are fine, doesn't really matter whether or not someone is actively pulling data from you.

Which VPN provider and endpoint are you using? I'm using CyberGhost - OpenVPN settings (Netherlands) Per their FAQ, allowing P2P and opening ports are 2 different things. The premium service allows P2P, but they don't open ports for you. Since you do not have an open port to allow unsolicited incoming connections, you are not available for uploading to IPT. The only connections your client is making is to download, and if the peer you are downloading from also needs parts that you have, you will upload to them while you have that connection open, but as soon as the torrent client closes that connection you can no longer seed to them. TLDR, get another VPN provider that allows incoming ports. PIA is the easiest to set up, as all the configuration is done for you in the container.

Which VPN provider and endpoint are you using?

How does your VPN provider handle forwarded ports? This container is set up to handle PIA forwarded ports automatically, if you are using another provider you have to figure out what port number is open and forwarded to you, and manually set the incoming port in the deluge settings. If you don't have it set correctly, that could cause speed (and connectivity) issues.

IPT works just fine with this container and PIA using the default netherlands gateway. No monkeying about with openvpn configs or any special settings, it just works.

Alone or in pairs... Sounds like you have people in mind

Nice! After all the unraid docker advanced view issues, you'd think that would be the first place I'd look.

thats exactly what privoxy is for (built into rtorrentvpn and delugevpn), FAQ Q4. http://lime-technology.com/forum/index.php?topic=45812.msg437678#msg437678 Yes, but the question is, how do you force CP through privoxy when there are no settings exposed in the GUI to set a proxy?

Keep in mind that the longer the processor runs, the more power is used as well, so going full throttle for the entire duration of a short task may well be more efficient overall than running at 10% for 10x the duration. Total power consumed for a specific amount of work done is a very complex thing, especially when you consider the rest of the rig may also be consuming more power waiting for the cpu to finish. I'd rather see the cpu snap to full throttle, get the job done, and go back to idle instead of stepping up and down trying to play catch up.

Any idea why one merchandiser would have higher failure rates than another with the same hard drive manufacturer ? Shipping and handling. I've seen more drives die from mishandling than any other cause, other than plain old age.

http://lime-technology.com/forum/index.php?topic=45811.0 Installation - Step 6.