Jump to content
binhex

[Support] binhex - qBittorrentVPN

372 posts in this topic Last Reply

Recommended Posts

2 minutes ago, Squid said:

The only way around it is to not delete anything at all on startup and rely upon the app to delete it's own temp files.

im fairly ok with apps deleting their own temp files as this generally does happen without issue afaik, i also use /tmp to store temporary created files that store data that i need to share between users, for instance root and user nobody, for technical reasons in bash this gets difficult and thus i resort to use /tmp as a way of transferring critical information between acconts, its this temporary data that needs to be cleaned up and thus the historic cleaning of /tmp.

Share this post


Link to post

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?

Share this post


Link to post
2 hours ago, whauk said:

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?

Only thing you can do is roll back to the previous version, See my last post if you don't know how.

Share this post


Link to post

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.

Edited by whauk

Share this post


Link to post

How do I set this up to use an ephemeral port from my VPN service (Windscribe)? I requested a matching internal and external port from my VPN service, and within the qBittorrent WebUI I entered it into the field under "Connection > Listening Port" with "UPnP / NAT-PMP port forwarding from my router" off, no port forwarding options added to my router settings, and no added settings in the docker container edit page. If what I'm doing is already correct, do I also need to restart the docker container for the setting to be applied?

 

I think my uploads are now faster, but I'm not sure how to test whether or not it's really working besides I guess just changing ports and eyeballing my upload speeds, but it's hard to fully accept it as not being coincidence. Hopefully I have this setup right and I'll just update that one field every time I get a new port (again, not sure if it requires a container restart), I was just mainly wondering if I have to add that port somehow in the docker container settings. I'm not much of a network person, so I apologize if I'm asking a very basic stupid question. 

 

EDIT: 

I ended up looking at the container log and noticed a line saying: "Successfully retrieved external IP address [blahblah]", so I input that IP address into a port checker with my ephemeral port from my VPN service that I set in the qBittorrent WebUI and it looks like it's open. 

 

Should I be adding any port settings to the container settings? I just left everything besides the setup for Windscribe VPN default and did not add anything else. Do I need to port forward anything to begin with on my router, like any of those default/ephemeral ports?

 

In the log, I also see two different IPs from my new external IP with a line saying: "qBittorrent listening interface IP [blahblah] and VPN provider IP [blahblah] different, marking for reconfigure". Is that okay? My bad for all the questions.

Edited by DoleWhip

Share this post


Link to post
On 12/8/2019 at 8:02 PM, DoleWhip said:

Should I be adding any port settings to the container settings?

nope, you dont forward any ports outside of the vpn tunnel

 

On 12/8/2019 at 8:02 PM, DoleWhip said:

Do I need to port forward anything to begin with on my router, like any of those default/ephemeral ports?

the only port you MAY want to port forward is for the web ui but ONLY if you want to access the web ui outside of your home lan.

Share this post


Link to post
On 12/7/2019 at 10:05 PM, binhex said:

i think for now i will go for a non recursive delete of /tmp and monitor for any rogue folders that might need to be included in the cleanup and add them in when necessary, its the least intrusive approach whilst preventing the issue from re-occurring.

this is now done and a new image is building, fyi i also put in a further check by looking at disk usage, if the disk usage for /tmp exceeds 1GB then /tmp will not be wiped and a warning will be logged instead. as this change is in a global script it will be included in all other images as they are triggered for build (due to version bump).

Share this post


Link to post
1 hour ago, binhex said:

nope, you dont forward any ports outside of the vpn tunnel

 

the only port you MAY want to port forward is for the web ui but ONLY if you want to access the web ui outside of your home lan.

Gotcha, thanks for the confirmation, I appreciate it. Also thank you for maintaining this.

Share this post


Link to post

I've been using this for a while with sickgear and recently I've been getting: 

 

Error: Unable to get qBittorrent authentication, check your config!

 

Using http://ip:8080/

Password is correct and the config.ino looks good. Haven't found anything about it searching sickgear topics. Was wondering if anyone has experience something similar? 

 

I did try sickchill which seemed to work but sickgear is what I'd like to continue using. 

 

Troubleshooting steps I've tried: 

Using hostname

Removing last slash. 

Reinstalling sickgear from scratch deleting my original config. 

Deleting entries for qbittorrentvpn from my ini. 

Setting local subnet to allow without auth to webui. 

 

None of these worked. Any ideas on which side this is on? I didn't manage to notice it after any specific update to either docker so I'm a bit stumped. 

 

 

Edit went to version 4.1.9 and still a no go. 

😁

Edit2: Must've not downgraded to the correct version. binhex/arch-qbittorrentvpn:4.1.9-1-01 worked!

Edited by Chezro

Share this post


Link to post
On 12/10/2019 at 12:02 PM, Chezro said:

I've been using this for a while with sickgear and recently I've been getting:

 

Error: Unable to get qBittorrent authentication, check your config!

 

Using http://ip:8080/

Password is correct and the config.ino looks good. Haven't found anything about it searching sickgear topics. Was wondering if anyone has experience something similar?

 

I did try sickchill which seemed to work but sickgear is what I'd like to continue using.

 

Troubleshooting steps I've tried:

Using hostname

Removing last slash.

Reinstalling sickgear from scratch deleting my original config.

Deleting entries for qbittorrentvpn from my ini.

Setting local subnet to allow without auth to webui.

 

None of these worked. Any ideas on which side this is on? I didn't manage to notice it after any specific update to either docker so I'm a bit stumped.

 

 

Edit went to version 4.1.9 and still a no go.

😁

Edit2: Must've not downgraded to the correct version. binhex/arch-qbittorrentvpn:4.1.9-1-01 worked!

You are probably having issues because Sickgear has not been updated for the new changes with Qbittorent. I no longer use that program as I've moved to Medusa since the Sickrage/Sickgear drama...but thats my best guess as to why 4.2.0 doesnt work for you. 

Edited by DazedAndConfused

Share this post


Link to post

hi. Thank you for this container.

 

I'm writing because I'm having trouble uploading to peers even though it says I'm connecting to PIA and everything seems fine. Downloading works great but my ratio will suffer if I can't get this fixed.

 

please help. Log below:

 

Cheers!

 

[info] OpenVPN started

2019-12-14 01:20:16,414 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:16 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-12-14 01:20:16,416 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:16 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.34:1198

Sat Dec 14 01:20:16 2019 UDP link local: (not bound)

Sat Dec 14 01:20:16 2019 UDP link remote: [AF_INET]172.98.67.34:1198

2019-12-14 01:20:16,504 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:16 2019 [0195d7159dd5e3c495e4dffb60368068] Peer Connection Initiated with [AF_INET]172.98.67.34:1198

2019-12-14 01:20:22,724 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:22 2019 TUN/TAP device tun0 opened

Sat Dec 14 01:20:22 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-12-14 01:20:22,730 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:22 2019 /usr/bin/ip addr add dev tun0 local 10.27.10.10 peer 10.27.10.9

2019-12-14 01:20:22,734 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:22 2019 /root/openvpnup.sh tun0 1500 1558 10.27.10.10 10.27.10.9 init

2019-12-14 01:20:22,747 DEBG 'start-script' stdout output:

Sat Dec 14 01:20:22 2019 Initialization Sequence Completed

2019-12-14 01:20:22,875 DEBG 'start-script' stdout output:

[info] Port forwarding is enabled

[info] Checking endpoint 'ca-toronto.privateinternetaccess.com' is port forward enabled...

2019-12-14 01:20:22,881 DEBG 'start-script' stdout output:

[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2019-12-14 01:20:23,205 DEBG 'start-script' stdout output:

[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2019-12-14 01:20:23,305 DEBG 'start-script' stdout output:

[info] PIA endpoint 'ca-toronto.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2019-12-14 01:20:23,305 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

[info] ca-toronto.privateinternetaccess.com

[info] ca-montreal.privateinternetaccess.com

[info] ca-vancouver.privateinternetaccess.com

[info] de-berlin.privateinternetaccess.com

2019-12-14 01:20:23,305 DEBG 'start-script' stdout output:

[info] de-frankfurt.privateinternetaccess.com

[info] sweden.privateinternetaccess.com

[info] swiss.privateinternetaccess.com

[info] france.privateinternetaccess.com

[info] czech.privateinternetaccess.com

[info] spain.privateinternetaccess.com

[info] ro.privateinternetaccess.com

[info] israel.privateinternetaccess.com

[info] Attempting to get dynamically assigned port...

2019-12-14 01:20:23,314 DEBG 'start-script' stdout output:

[info] Attempting to curl http://209.222.18.222:2000/?client_id=db19900a5cc482c53d1ab63d9d5f6ab81fef785e29cc0f046c826b53b4b77d0c...

2019-12-14 01:20:23,947 DEBG 'start-script' stdout output:

[info] Curl successful for http://209.222.18.222:2000/?client_id=db19900a5cc482c53d1ab63d9d5f6ab81fef785e29cc0f046c826b53b4b77d0c, response code 200

2019-12-14 01:20:24,000 DEBG 'start-script' stdout output:

[info] Successfully assigned incoming port 46735

2019-12-14 01:20:24,002 DEBG 'start-script' stdout output:

[info] Checking we can resolve name 'www.google.com' to address...

2019-12-14 01:20:24,132 DEBG 'start-script' stdout output:

[info] DNS operational, we can resolve name 'www.google.com' to address '216.58.204.68'

2019-12-14 01:20:24,143 DEBG 'start-script' stdout output:

[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-12-14 01:20:24,446 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 172.98.67.34

2019-12-14 01:20:24,957 DEBG 'watchdog-script' stdout output:

[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.27.10.10 different, marking for reconfigure

2019-12-14 01:20:24,964 DEBG 'watchdog-script' stdout output:

[info] qBittorrent not running

2019-12-14 01:20:24,964 DEBG 'watchdog-script' stdout output:

[info] qBittorrent incoming port 6881 and VPN incoming port 46735 different, marking for reconfigure

2019-12-14 01:20:24,965 DEBG 'watchdog-script' stdout output:

[info] Removing session lock file (if it exists)...

2019-12-14 01:20:24,966 DEBG 'watchdog-script' stdout output:

[info] Attempting to start qBittorrent...

2019-12-14 01:20:25,020 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process started

[info] Waiting for qBittorrent process to start listening on port 8080...

2019-12-14 01:20:25,137 DEBG 'watchdog-script' stdout output:

[info] qBittorrent process listening on port 8080

Edited by markwest

Share this post


Link to post

I currently have this downloading to /config/qBittorrent/downloads/Movies/ which is a subdirectory under the appdata/binhex-qbittorentvpn/ directory of my cache drive.

 

Currently my cache drive however is only 120g and obviously has my dockers etc installed on there alongside my VPM. 

 

So 2 questions

 

1. Can i map the downloads out of the docker and onto disk 1 of the array ? /mnt/Disk1/Downloads ?

2. What are the performance issues relating to doing this on point 1 ?

3. How do i map point 1 ?

 

Any help appreciated, sorry extremely new to dockers

Share this post


Link to post
On 12/6/2019 at 2:35 AM, kesm said:

Hi, 

I also have a problem since last update. I cannot access WebUI from outside my network.

 

I have privoxy disabled, LAN_Network configured with 192.168.1.0/24, webui ports changed to 8090, I'm able to access qbt locally on address 192.168.1.xx:8090, port 8090 is opened in my firewall but I cannot access qbt from outside my network on address myunraiddns:8090 or myunraidip:8090 (other apps works well).

I tried to rollback to binhex/arch-qbittorrentvpn:4.1.9-1-01 but I still cannot reach qbt webui


Error message is 
 

This site can’t be reached

myunraiddns took too long to respond.

Strange but this just started happening to me as well. I downgraded the docker a few weeks ago and it was working without issue. Now everything on my LAN is discoverable when I am connected to my pfsense router via vpn, with the exception of the qbittorrent web ui. It has thrown me for a loop

 

edit- Looks like it was a firewall issue, set up port forwarding on 8080 for LAN and it started working again. Not sure why it suddenly stopped in the first place, but I'll take it.

Edited by Dysun

Share this post


Link to post
7 hours ago, danz0l said:

I currently have this downloading to /config/qBittorrent/downloads/Movies/ which is a subdirectory under the appdata/binhex-qbittorentvpn/ directory of my cache drive.

 

Currently my cache drive however is only 120g and obviously has my dockers etc installed on there alongside my VPM. 

 

So 2 questions

 

1. Can i map the downloads out of the docker and onto disk 1 of the array ? /mnt/Disk1/Downloads ?

2. What are the performance issues relating to doing this on point 1 ?

3. How do i map point 1 ?

 

Any help appreciated, sorry extremely new to dockers

1. Yes

2. If Disk1 is part of the array, it will constantly be writing to the Parity drive. You might look into the Unassigned Devices plugin to add a disk outside of the array (you'll need another spare disk for this) and then move your completed download to the array.

3. Edit the docker, then click "Add another Path, Port, Variable, Label or Device"

Change Config Type to "Path"

Enter a Container Path, ex. /new_download_location

Enter a Host Path, ex. /mnt/Disk1/Downloads

Click save

 

The path /new_download_location will show up inside of the container and it points to /mnt/Disk1/Downloads.

Go into the qBittorent webui, Tools > Options > Downloads. Change Default Save Path to /new_download_location.

Share this post


Link to post

I'm fairly new to unraid and dockers.  Everything works great including sonarr interaction, but whenever I have to reboot the server it seems that my preferences aren't saved.  I have to go back into the docker and setup my incomplete/complete download locations again as well as the monitored folder I use to send .torrent files from other sources.  Any ideas?

Share this post


Link to post
4 minutes ago, bchinfoon said:

I'm fairly new to unraid and dockers.  Everything works great including sonarr interaction, but whenever I have to reboot the server it seems that my preferences aren't saved.  I have to go back into the docker and setup my incomplete/complete download locations again as well as the monitored folder I use to send .torrent files from other sources.  Any ideas?

Post your docker run command as explained in the very first link in the Docker FAQ

Share this post


Link to post
11 minutes ago, trurl said:

Post your docker run command as explained in the very first link in the Docker FAQ

My apologies.  I have xxxx'ed out the VPN user and pw for security purposes:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxx' -e 'VPN_PASS'='xxxx' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8080:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/torrents/':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' 'binhex/arch-qbittorrentvpn' 

05f8d53731e0b7cc26d8c8a369d4f096fb35eb8dbfa4812ec3ec891ef983bd59

Share this post


Link to post
On 12/17/2019 at 1:00 PM, a_n_d_y said:

1. Yes

2. If Disk1 is part of the array, it will constantly be writing to the Parity drive. You might look into the Unassigned Devices plugin to add a disk outside of the array (you'll need another spare disk for this) and then move your completed download to the array.

3. Edit the docker, then click "Add another Path, Port, Variable, Label or Device"

Change Config Type to "Path"

Enter a Container Path, ex. /new_download_location

Enter a Host Path, ex. /mnt/Disk1/Downloads

Click save

 

The path /new_download_location will show up inside of the container and it points to /mnt/Disk1/Downloads.

Go into the qBittorent webui, Tools > Options > Downloads. Change Default Save Path to /new_download_location.

This is exactly what I needed to know. Thank you! 

Share this post


Link to post
On 12/8/2019 at 3:02 PM, DoleWhip said:

How do I set this up to use an ephemeral port from my VPN service (Windscribe)? I requested a matching internal and external port from my VPN service, and within the qBittorrent WebUI I entered it into the field under "Connection > Listening Port" with "UPnP / NAT-PMP port forwarding from my router" off, no port forwarding options added to my router settings, and no added settings in the docker container edit page. If what I'm doing is already correct, do I also need to restart the docker container for the setting to be applied?

 

I think my uploads are now faster, but I'm not sure how to test whether or not it's really working besides I guess just changing ports and eyeballing my upload speeds, but it's hard to fully accept it as not being coincidence. Hopefully I have this setup right and I'll just update that one field every time I get a new port (again, not sure if it requires a container restart), I was just mainly wondering if I have to add that port somehow in the docker container settings. I'm not much of a network person, so I apologize if I'm asking a very basic stupid question. 

 

EDIT: 

I ended up looking at the container log and noticed a line saying: "Successfully retrieved external IP address [blahblah]", so I input that IP address into a port checker with my ephemeral port from my VPN service that I set in the qBittorrent WebUI and it looks like it's open. 

 

Should I be adding any port settings to the container settings? I just left everything besides the setup for Windscribe VPN default and did not add anything else. Do I need to port forward anything to begin with on my router, like any of those default/ephemeral ports?

 

In the log, I also see two different IPs from my new external IP with a line saying: "qBittorrent listening interface IP [blahblah] and VPN provider IP [blahblah] different, marking for reconfigure". Is that okay? My bad for all the questions.

 

Thanks for posting, I checked afterwards on Mullvad port forwarding and once I got it setup a few stalled torrents immediately began to complete. 

 

 

Share this post


Link to post

Getting Chrome to send magnet links to qBittorrent WebUI:

 

I was in the middle of posting a question, when I answered my own question... I thought I should share:

[qbittorrent v4.2] In the qBittorrent WebUI, under the Tools section, there is the option to "Register to handle Magnet Links...". At first, this did NOT work properly. It would create a handler in Chrome on the client without issue, but that handler would not work, and constantly returned a 404:Not Found error every time I clicked a magnet link on said client. My first thought seeing a 404 error is that the handler was not using the 8080 port properly (when viewing the handler in Chrome settings, it did not reflect the Port, just the IP/URL of the server.) so I assumed that the 404 error was caused by Chrome attempting to connect to the unraid server on the wrong port, not getting a response, and thus, spits out a 404 error. Made sense to me. I spent a lot of time trying to manipulate the settings in Chrome to rectify this problem... 

 

I discovered that it was actually an authentication issue. Adding the handler from the WebUI actually does include the port used by the WebUI, it's just that Chrome does not reflect that when viewing the handler settings...

 

What I needed to do was to add the IP of my client PC to the Whitelist in qBittorrent! It can be found under Options > Web UI > Authentication > (Enable)Bypass authentication for clients in whitelisted IP subnets.

 

If you only want to add specific clients access to the webui, simply specify the IP or hostname of those pcs.

If you want to allow all pcs on an entire subnet, enter 192.168.1.0/24

 

Do remember that enabling this option bypasses any authentication for those IPs you specify, so anyone using that IP will have god access to your qBittorrent WebUI. 

Edited by SeeGee
Added Title

Share this post


Link to post

Thanks for pointing this out, however when I tried that in Firefox the qbt client told me that my browser does not support this feature.

Anyone any idea why and whether there is a possibility to circumvent this (other than using Chrome)?

Share this post


Link to post
2 hours ago, whauk said:

Thanks for pointing this out, however when I tried that in Firefox the qbt client told me that my browser does not support this feature.

Anyone any idea why and whether there is a possibility to circumvent this (other than using Chrome)?

While I was looking into this, I saw several mentions that this does work with firefox, but I do not use firefox primarily, so I am unable to help you.

This is one place that made this claim: 

 

Share this post


Link to post

Thanks - that almost does it.

Unfortunately the application dialogue window in the current Firefox (71) wants to find either a locally or at least on a network drive installed Windows program to handle the magnet link.

I found no way to have FF directly handle a magnet link directed to a docker container on an Unraid system.

What works, though, is to register the qbt client with a local Chrome installation and direct the magent link in FF to be handled by Chrome - that sends the magnet link to the Unraid qbt.

A bit using the scenic route, but it works.

Edited by whauk

Share this post


Link to post

I'd like some input on something I haven't been able to fix.

On qbittorrent download completion, I am running this command:

cd /mnt/user/downloads/%N/; /usr/bin/unrar e *.rar

I am doing this so sonarr/radarr picks up files where rar's are present, it will unrar it in the directory so it can picked up/moved.

In qbittorent logs, I see it getting executed:

Torrent: Zombieland.Double.Tap.2019.1080p.BluRay.x264-DRONES, running external program, command: cd /mnt/user/downloads/Zombieland.Double.Tap.2019.1080p.BluRay.x264-DRONES/; /usr/bin/unrar e *.rar

However, unrar is not running and no file gets created in the directory. 

But, I login via terminal and manually run the following from any directory it works:

cd /mnt/user/downloads/Zombieland.Double.Tap.2019.1080p.BluRay.x264-DRONES/; /usr/bin/unrar e *.rar

Anyone have any guesses? It could be a permissions issue.  Is there a way I can increase debugging for qbittorrent to see if catches anything?

Share this post


Link to post

Just as an aside for those of you that use Transdroid for connecting to your qbt client: You may have noticed that version 2.5.16 ceased to work due to the changes in qbt 4.20.

There is an interim version to be found here - which unfortunately still produces an "Internal error building request" on my phone but it seems to work for others.

Just saying.

 

Edit: It works on my phones without a hitch, it just cannot be installed as an upgrade of V. 2.15.6.

Edited by whauk

Share this post


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.