On 3/15/2021 at 8:05 PM, binhex said:

So obviously there is no way i can block access to the PIA endpoint at a iptables level otherwise you would not be able to establish a tunnel in the first place, so the only options are try and bind qbittorrent to a particular interface (vpn tunnel interface) or if this doesn't fix it then simply change your logging to ignore that particular traffic type, how to bind to a interface:-

 

open qbittorrent web ui/options/advanced tab/ then change 'Network Interface' to either wg0 (wireguard) or tun0 (openvpn) click on save at the bottom to save the change and then restart the container, let me know if it stops the log messages, if so i can attempt to do this automatically.

 

Thanks for the reply @binhex, sorry for the delay - hectic week.

 

I've made the changes to the qbittorrent container as suggested (changed to tun0) and restarted the container. So far so good! No more P2P logs from my router.

 

I'll keep an eye on it over the weekend and see whether any more spring through, but so far this looks to be a viable workaround. Thanks!

35 minutes ago, evakq8r said:

 

Thanks for the reply @binhex, sorry for the delay - hectic week.

 

I've made the changes to the qbittorrent container as suggested (changed to tun0) and restarted the container. So far so good! No more P2P logs from my router.

 

I'll keep an eye on it over the weekend and see whether any more spring through, but so far this looks to be a viable workaround. Thanks!

no problems I thought this might work so I have actually coded this up and it's now fully automated in the latest image, so you do not need to manually set it anymore it's done for you

1 hour ago, binhex said:

no problems I thought this might work so I have actually coded this up and it's now fully automated in the latest image, so you do not need to manually set it anymore it's done for you

 

Thanks very much!

I noticed none of the containers I have routed through this one could communicate with services on LAN IPs.

 

I found the solution in A27 of the FAQ:

Adding a variable VPN_OUTPUT_PORTS with a list of port exceptions (mine are Emby and SMTP)

 

I didn't see this mentioned here (maybe it's new) so I thought I'd mention it.

I updated awhile ago and it broke things, so I reverted to an older version. This got qbittorrent working but sonarr etc could not connect to it for some reason even though all the settings are the same.

 

So I updated it again to see if things were fixed and first it is still not able to connect but in the logs it is trying to chown my entire media library that is stored under /data??

 

Why is it trying to change permissions on everything under /data?

 

edit: reverting to binhex/arch-qbittorrentvpn:4.3.1-1-03 got it working again but if I clear the appdata folder, it will still try to chown my entire share mapped to /data.

Edited March 21, 20215 yr by TexasUnraid

TexasUnraid,

 

with a tightening of the ip_tables for leakage, you now have to do one of two things as outlines on this page, Q26

 

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

That should fix connecting to your bittorrent client.

5 minutes ago, mooky said:

TexasUnraid,

 

with a tightening of the ip_tables for leakage, you now have to do one of two things as outlines on this page, Q26

 

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

That should fix connecting to your bittorrent client.

 

Ok, cool, that explains that issue, I will try updating again at some point and doing that.

This is a bit of a side question, but since you can only see the web UI in this form of QB, I'm having an issue. I can't find torrents with tracker status 'not registered with this tracker' (i.e. deleted from site) easily. I need to click every torrent and check manually. Does anyone know of a better way to do this?

Hello

I have a question , but I don't know if already asked.

I made the installation, all seems to work, but I can't login from Chrome.

I try with Edge and I manage to login without a problem.

Clear the Chrome cookies etc, the same.

Anyone knows why Chrome blocks?

 

Thank you in advance

Hello, im currently using Deluge and tried Qbittorrent but this one is using 50-60% of my cpu when downloading only (Used docker stats to show it)

I'm using MullVad VPN.

 

How can i fix it ?

 

EDIT : words

Edited March 26, 20215 yr by Kishin

Just wanted to mention that I highly recommend switching to wireguard instead of openvpn. I had a few downloads stuck for days that were stalled even though they were connected to seeders. Once I switched to wireguard they finally started moving.

I finally for things to work with Jackett, Sonarr and Radarr, thanks to all the amazing posts in this thread. However I'm running 3 instances or LinuxServer's Sonarr and can't get things to work with instances 2 and 3. By removing the port allocation of Sonarr, it seems to default back to port 8989, which is already taken from Sonarr's 1st instance. Even if I change the WebUI port to 9090, it doesn't seems to work. If I stop instance #1 and start instance #2, instance #2 is accessible via port 8989 instead of the 9090 where it's to be expected. Anyone has an idea about what I should try?

 

Here's a part of the log of the 2nd Sonarr instance: Fatal] ConsoleApp: Address already in use. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions

 

Thanks!

 

Sonarr #1 - working

 

Sonarr #2 - not working

 

both Sonarrs in Docker view, same port allocated by the system

 

 

qbittorrentvpn - Sonarr #1 - working

 

 

qbittorrentvpn - Sonarr #2 - not working

 

Additionnal ports in qbittorrentvpn

 

 

 

 

Getting a new issue with qbittorrent.  Was working fine yesterday.  Using PIA with Wireguard.

8 hours ago, touz said:

I finally for things to work with Jackett, Sonarr and Radarr, thanks to all the amazing posts in this thread. However I'm running 3 instances or LinuxServer's Sonarr and can't get things to work with instances 2 and 3. By removing the port allocation of Sonarr, it seems to default back to port 8989, which is already taken from Sonarr's 1st instance. Even if I change the WebUI port to 9090, it doesn't seems to work. If I stop instance #1 and start instance #2, instance #2 is accessible via port 8989 instead of the 9090 where it's to be expected. Anyone has an idea about what I should try?

 

Here's a part of the log of the 2nd Sonarr instance: Fatal] ConsoleApp: Address already in use. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions

 

Thanks!

 

Sonarr #1 - working

 

Sonarr #2 - not working

 

both Sonarrs in Docker view, same port allocated by the system

 

 

qbittorrentvpn - Sonarr #1 - working

 

 

qbittorrentvpn - Sonarr #2 - not working

 

Additionnal ports in qbittorrentvpn

 

 

 

Are they all using the same appdata folder?

1 hour ago, barnito said:

Are they all using the same appdata folder?

thank you for your reply, no they are not.

22 hours ago, sittingmongoose said:

Getting a new issue with qbittorrent.  Was working fine yesterday.  Using PIA with Wireguard.

Same error here.

 

A bunch of:

 

2021-04-03 15:55:59,590 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2021-04-03 15:55:59,592 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2021-04-03 15:55:59,592 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error


2021-04-03 15:55:59,594 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2021-04-03 15:55:59,629 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

 

Was working till some hour ago...

17 hours ago, touz said:

thank you for your reply, no they are not.

I would try to give each instance their own IP on your network using br0, see if that changes anything

This allows both dockers to have the same ports, but show up as separate IP devices on your network

Hi all, new to unraid.

Got this docker setup with PIA and using a location that offers portforwarding. I can access the webui on my local internet no problem. But how do I access it remotely via an app to manage torrents away from home?

I'm using nzb360 android app and it's fantastic.  Before embracing Unraid, via windows qbittorent on the webui remote setup, I entered in my VPN port number instead of 8080.  But I can't see what my vpn port is on unraid

Edited April 9, 20215 yr by jellytotz

On 1/20/2021 at 2:37 AM, wgstarks said:

Right click on Categories>All in the left side menu bar and you will get a popup that will let you create a new category as well as set a save location. Example: /data/downloads/tvshows/

 

Go to Settings>Downloads. Scroll down to "Automatically add torrents from" and set a Watch folder. Example: /data/watch/

Any torrent files added to this folder will be added to downloads.

 

Remember the root of these paths must be /data/ (assuming you haven't changed the default in the container settings).

Hi there, if want to add a watch folder, it get not saved (after I hit save button). So if I the open settings and scroll down to "Automatically add torrents from", it looks like nothing changed. What am I doing wrong?

 

8 minutes ago, gizmer said:

Hi there, if want to add a watch folder, it get not saved (after I hit save button). So if I the open settings and scroll down to "Automatically add torrents from", it looks like nothing changed. What am I doing wrong?

 

Post a screenshot of your settings.

15 minutes ago, wgstarks said:

Post a screenshot of your settings.

so I'm trying to add the folder /data/Watched/

53 minutes ago, gizmer said:

Hi there, if want to add a watch folder, it get not saved (after I hit save button). So if I the open settings and scroll down to "Automatically add torrents from", it looks like nothing changed. What am I doing wrong?

 

yep i got stuck on this myself and wrote up how to fix it, see Q2:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

I also had to click the little square symbol next to “monitored folder”. That will add your setting and open a new blank line. Click save when done.

3 hours ago, binhex said:

yep i got stuck on this myself and wrote up how to fix it, see Q2:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

thanks, @binhex! It did the trick!