[Support] binhex - qBittorrentVPN


binhex

1327 posts in this topic Last Reply

Recommended Posts

Out of curiousity, are the IP Leak issues with qBittorrentvpn still a thing? Since the update was made about the ip leakage and an update to this container was released, my USG4P has been throwing DHT announce messages out once every 4 minutes. ie.

 

Threat Management Alert 1: Potential Corporate Privacy Violation. Signature ET P2P BitTorrent DHT announce_peers request. From: 192.168.1.100:20541, to: 172.98.71.202:20541, protocol: UDP

 

172.98.71.202 points to the PIA endpoint for Montreal.

 

I've also tested this with the binhex-rtorrentvpn container and do not get these logs, which to me means it's specific to this container. I'm unable to swap to rtorrentvpn however for other reasons (not relevant to this issue).

 

Prior to the update, this wasn't happening at all. If this is expected behaviour, I'll learn to live with it but every 4 minutes for over a week is a lot of log file.

 

 

Edited by evakq8r
Link to post
  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

@binhex Does the container only use a single .ovpn file from the appdata directory for configuration? Can I put all of the PIA port-forwarding capable server .ovpn files in there so that it can try th

Support for multi remote endpoints and PIA 'Next-Gen' networks now complete, see Q19 and Q20 for details:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Create a necessary folder in   \\yourservername\appdata\binhex-qbittorrentvpn\qBittorrent    Create a folder called ssl     Open up terminal and type,  

Posted Images

6 hours ago, evakq8r said:

Out of curiousity, are the IP Leak issues with qBittorrentvpn still a thing? Since the update was made about the ip leakage and an update to this container was released, my USG4P has been throwing DHT announce messages out once every 4 minutes. ie.

 


Threat Management Alert 1: Potential Corporate Privacy Violation. Signature ET P2P BitTorrent DHT announce_peers request. From: 192.168.1.100:20541, to: 172.98.71.202:20541, protocol: UDP

 

172.98.71.202 points to the PIA endpoint for Montreal.

 

I've also tested this with the binhex-rtorrentvpn container and do not get these logs, which to me means it's specific to this container. I'm unable to swap to rtorrentvpn however for other reasons (not relevant to this issue).

 

Prior to the update, this wasn't happening at all. If this is expected behaviour, I'll learn to live with it but every 4 minutes for over a week is a lot of log file.

 

 

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.

Link to post
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!

Link to post
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

Link to post
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! :)

Link to post

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)

362418861_ScreenShot2021-03-19at12_17_39PM.thumb.png.bdc988594c85596acc1c621b7ddc8b7e.png

 

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

Link to post

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 by TexasUnraid
Link to post

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

Link to post

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 by Kishin
Link to post

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.

Link to post

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

1519937760_sonarr1-working.thumb.png.f7597e21cc981d8f3cd7c274aa85e504.png

 

Sonarr #2 - not working

836549365_sonarr2-notworking.thumb.png.d932202e2e740a124bdac29c9538f2fd.png

 

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

 

579158245_sonarr-both.png.29da10b201c73270ab9813df3b4ec5ec.png

 

qbittorrentvpn - Sonarr #1 - working

working.png.7f38113126af2436fb5b2875bbcbfa12.png

 

 

qbittorrentvpn - Sonarr #2 - not working

121497244_notworking.png.8ed0f653691165bf79c8c7fdf356b57c.png

 

Additionnal ports in qbittorrentvpn

 

1490292312_addiports.thumb.png.40b0b033a47f2ed99018c1925da748e2.png

 

 

 

Link to post
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

1519937760_sonarr1-working.thumb.png.f7597e21cc981d8f3cd7c274aa85e504.png

 

Sonarr #2 - not working

836549365_sonarr2-notworking.thumb.png.d932202e2e740a124bdac29c9538f2fd.png

 

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

 

579158245_sonarr-both.png.29da10b201c73270ab9813df3b4ec5ec.png

 

qbittorrentvpn - Sonarr #1 - working

working.png.7f38113126af2436fb5b2875bbcbfa12.png

 

 

qbittorrentvpn - Sonarr #2 - not working

121497244_notworking.png.8ed0f653691165bf79c8c7fdf356b57c.png

 

Additionnal ports in qbittorrentvpn

1490292312_addiports.thumb.png.40b0b033a47f2ed99018c1925da748e2.png

 

 

 

Are they all using the same appdata folder?

image.thumb.png.65af6f460527621f5128053dffd6c29c.png

Link to post
22 hours ago, sittingmongoose said:

Getting a new issue with qbittorrent.  Was working fine yesterday.  Using PIA with Wireguard.238996247_ScreenShot2021-04-02at11_30_59AM.thumb.png.6be35ddaeaa1ae2f06600676b84dd069.png

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...

Link to post

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 by jellytotz
Link to post
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?

 

Link to post
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.

Link to post
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

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.