whauk

Maybe, but I simply do not understand why rolling back is the only way to solve the issue. In my, potentially naive, worldview entering the new password in all the right places should connect radarr and sonarr on the one hand and qbt on the other again. It does not. Why? Edit: It does now - though I have no idea why. It may have something to do with uppgraded containers, but I am not sure.

Turns out that even after changing the password in qbt 4.2.0 - with following container restart - and also in radarr and sonarr to the new one, both containers still cannot connect to qbt (Authentication failure). And I'd wager a guess that this is also the reason why Transdroid can't connect to my qbt container (even though its error message is "internal error building request"). I am clearly missing something here, but Ihonestly have absolutely no clue, what. Has anyone already solved this problem?

Right, but copy your conf file to some other place first and afterwards compare the old and the new one. Transfer all the missing lines (with the exepction of the PW line) to the new one, else you lose all your changed settings.

Just wanted to say that I have the exact same problem. In addition, Sonarr (I assume) creates an additional subdirectory "tv-sonarr" under the directory that I set it to look into, which it fills with the TV downloads. However, even if I move the downloaded files one directory level higher (where they should land anyway), Sonarr does not import them anymore. So far that was no biggie for me (and I thought it was just my usual stupidity) since manual import always worked.

Thanks again, got it. But then, just out of curiosity, since I have to remap both qBT paths to host paths (which do not come out of the box) - what is th "data" path for?

I assumed it would be Host Path 2 (Container Path: /data) which I mapped to /mnt/cache/Downloads/Bittorrent as in the rutorrent container but somehow that didn't do the trick. The directory is being created but the downloads still land in /appdata/binhex-qbittorrentvpn/qBittorrent/downloads/. I can't find any other possible path in the settings section. As regards the rutorrent container: Can't tell for certain, sorry about that.

Wow. just wanted to let you know that today I switched from your rtorrent/rutorrent container (broken for the time being) and, while I originally wanted to use someone else's, I noticed this spankingly brand-new one and decided to give it a whirl: It worked out of the box! I don't find an option though to move the downloads path somewhere else, as your rtorrent/rutorrent container provided. Am I missing something?

? I took this to be some kind of heading.... ...and it works!

Where can I state a different port no. in Transdroid? So far it seems hardwired: Either 80 for http or 443 for https.

? And I thought I was done....doing it via the browser on my phone. But thanks one more time - I'll give it a try, hoping that the GUI will be somewhat more accommodating than your average browser interface on a phone.?

Ah, yes, of course., two completely different things....?

Correct - it's NAT, so the external IP address is the same for all machines, but the port is forwarded ok.... Oha: If I change the protocol from UDP to TCP it works. Now I will just have to exchange the VPN server UDP file for a TCP one, restart and I should be all set. Again thanks a lot! Edit: Yup, works like a charm!?

Thanks, tried the port forwarding already, but no luck. supervisord.log says "2018-05-01 15:15:50,871 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables" - but I guess that's not it?

rtorrent and rutorrent are running without a problem and I did not touch port 5000 at all - so to my understanding it should be handed straight through. Edit: Shit, I just saved the Sickrage configuration file again - and now it works. Stranger things.... Thanks for the help! One other question: If I wanted to access rtorrent remotely, via a DynDNS, I assume the Container Variable: LAN_NETWORK will keep me from doing so unless it is set to a value that accepts all incoming IP addresses (I deleted the standard user, created my own and avoid using standard ports, so I figure I am reasonably safe). If that assumption is correct: What value would I have to use?

Thanks, I'll give it a shot.

It does.

I still can't make Sickrage talk to rTorrent, sorry. My torrent host/port line is scgi://10.0.0.47:5000/ (I use 10.0.0.0/24). I do not quite understand " I was using the username and password and it wasn't working. Without it works fine." Which username and PW?

Take mine - I have the same problem..;-}qbittorrent.log