[Support] binhex - qBittorrentVPN


binhex

1327 posts in this topic Last Reply

Recommended Posts

New to Unraid and this is my first docker! I'm envious of anyone who can set this up in 15 mins! I've finally got myself logged into the Qbit WebUI and I started my first torrent but after an initial bump of speed it quickly drops to 0 and stalls indefinitely! I'm not sure where to go from this point and I think I need a break, 3 hours+ so far? lol. I'm not seeing anything in the logs to help me out. Do any changes have to be made in the connection tab or is the default port and all those settings already optimal?

Also did you guys know that it looks like Netherlands and Toronto are no longer in the port forwarding list according to the log? I had to connect to Sweden and use the PIA OpenVPN configurator for it with the 1st recommended option.

I can post logs if needed. Any help would be appreciated! I'd really like to retire my dedicated torrenting laptop now that I have an Unraid server!

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

8 hours ago, 404_BalancedLifeNotFound said:

I started my first torrent but after an initial bump of speed it quickly drops to 0 and stalls indefinitely!

Without logs or diagnostics we are shooting in the dark, but first thing to check is your path mapping. Make sure QB is saving files to the folder listed on the container side the the mapping, and the host side of the mapping is set to a spot on your array with enough space and correct permissions.

Link to post
13 hours ago, jonathanm said:

Without logs or diagnostics we are shooting in the dark, but first thing to check is your path mapping. Make sure QB is saving files to the folder listed on the container side the the mapping, and the host side of the mapping is set to a spot on your array with enough space and correct permissions.

You might have gotten right to the heart of it...I just installed binhex rtorrent vpn and I left the path mapping at default...As soon as i figured i had to switch off some (rcp?) stuff it started up and the torrent began downloading fine into the appdata/data folder. I was confused between host path and container path...I set the host path to where I wanted the download to go and I left the container path to /data...

Is the container path supposed to be the same as the last part of the host path perhaps?

If so I think I might just try to get that set correctly for rtorrent now, I haven't seen a DL speed over 10 MiB for a long time and that's what I'm getting now!

This is certainly tricky vs just using windows forever but I'm finding this interesting...especially when I can get it to work!

Link to post

Just switched servers since Canadian ones are broken (for port forwarding). According to supervisord.log, everything is working. I don't see anything special in qBittorrent.log either aside from the correct VPN IP. However, the webUI doesn't work, despite both logs saying it's now listening on port 8080. Is there a different log for the webUI hidden somewhere?

Link to post

Just noticed the VPN IP is part of RFC 1918 reserved IPs for private (local) networks, is that normal? Tried Spain and Israel servers.

2020-04-12 10:02:52,603 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2020-04-12 10:02:52,666 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 38328
[debug] qBittorrent incoming port is 38328
[debug] VPN IP is 10.12.11.6
[debug] qBittorrent IP is 10.12.11.6

That's confusing. As for qbittorrent.log, 10.1.1.54 being the docker IP:


(N) 2020-04-12T10:02:52 - qBittorrent v4.2.3 started
(N) 2020-04-12T10:02:52 - Using config directory: /config/qBittorrent/config/
(N) 2020-04-12T10:02:52 - qBittorrent v4.2.3 started
(N) 2020-04-12T10:02:52 - Using config directory: /config/qBittorrent/config/
(I) 2020-04-12T10:02:52 - Trying to listen on: 0.0.0.0:49121,[::]:49121
(N) 2020-04-12T10:02:52 - Peer ID: -qB4230-
(N) 2020-04-12T10:02:52 - HTTP User-Agent is 'qBittorrent/4.2.3'
(I) 2020-04-12T10:02:52 - DHT support [ON]
(I) 2020-04-12T10:02:52 - Local Peer Discovery support [ON]
(I) 2020-04-12T10:02:52 - PeX support [ON]
(I) 2020-04-12T10:02:52 - Anonymous mode [OFF]
(I) 2020-04-12T10:02:52 - Encryption support [FORCED]
(I) 2020-04-12T10:02:52 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Tue Mar 31 19:49:13 2020.
(N) 2020-04-12T10:02:52 - Using built-in Web UI.
(N) 2020-04-12T10:02:52 - Web UI translation for selected locale (en) has been successfully loaded.
(N) 2020-04-12T10:02:52 - Web UI: Now listening on IP: *, port: 8080
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 127.0.0.1, port: TCP/49121
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 127.0.0.1, port: UDP/49121
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.12.11.6, port: TCP/49121
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.12.11.6, port: UDP/49121
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.1.1.54, port: TCP/49121
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.1.1.54, port: UDP/49121
(N) 2020-04-12T10:02:52 - Web UI: Now listening on IP: *, port: 8080
(N) 2020-04-12T10:02:52 - Web UI: Now listening on IP: *, port: 8080
(I) 2020-04-12T10:02:52 - Trying to listen on: 0.0.0.0:38328,[::]:38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 127.0.0.1, port: TCP/38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 127.0.0.1, port: UDP/38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.12.11.6, port: TCP/38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.12.11.6, port: UDP/38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.1.1.54, port: TCP/38328
(I) 2020-04-12T10:02:52 - Successfully listening on IP: 10.1.1.54, port: UDP/38328
(I) 2020-04-12T10:02:55 - Detected external IP: 185.77.248.2

 

Link to post

Also note that the webUI works perfectly with VPN_ENABLED set to no. I'm accessing the docker from the same VLAN/subnet so the firewall shouldn't be an issue here (everything is allowed on that VLAN/subnet anyway).

Link to post

All downloads are stalled. I'm using PIA and connected to Sweden after port forwarding went down on Montreal this week. I have tested via windows using PIA windows application and QBIT works fine behind a PIA VPN connection so its something to do with the docker. Has been working fine for months, now every torrent defaults to stalled.

 

Link to post
On 4/12/2020 at 3:05 PM, dnLL said:

Just noticed the VPN IP is part of RFC 1918 reserved IPs for private (local) networks, is that normal?

perfectly normal, this is part of the internal routing for the vpn provider's network.

Link to post

Hi all,

 

Familiar with qbt from windows, but a bit new to unraid and docker.  Got this set up and working well with Radarr and Sonarr (all via unraid docker), but I have one weird issue.  I wish I could search this post in case other people have seen this too, but I can't see a way to do that...

 

Anyway, I can't seem to start any downloads from the Search page.  Search runs fine, and the download options window pops up, but when I click Download, it isn't added to the Downloads.  Is this a known issue or does anyone have an idea of what's going on?

 

Thanks for any help!

Link to post
2 hours ago, Amorbellum said:

for the love of god and all that is holy, why did you share port 8080 between SAB and qbitorrent? this is brutal man, I cant get Qbitorrent to run

There is a paragraph for that at the end of the readme:

Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.

For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090

 

Link to post
3 hours ago, Amorbellum said:

why did you make it the same port as sab?

binhex doesn't control either qbittorent or sab, he just sets up the docker containers and templates. He has no control over what the application authors decide to use as their default port.

 

If you want help resolving your issues, you need to provide more information, like the docker run command for both applications. Normally you would just change only the host port to a unique number for your system, and access the application on the new port that you specified.

 

I understand you are frustrated, but your approach of blaming binhex for something that's not in his control isn't helping.

Link to post
3 hours ago, Amorbellum said:

I changed host port 3 to 9090 and the webui is just blank, not even an error

As documented in the container's readme, the WEBUI_PORT variable needs to match the port setting and you can't remap the port

 

so set 9090=9090 and set the variable WEBUI_PORT=9090

Link to post
11 hours ago, jonathanm said:

binhex doesn't control either qbittorent or sab, he just sets up the docker containers and templates. He has no control over what the application authors decide to use as their default port.

 

If you want help resolving your issues, you need to provide more information, like the docker run command for both applications. Normally you would just change only the host port to a unique number for your system, and access the application on the new port that you specified.

 

I understand you are frustrated, but your approach of blaming binhex for something that's not in his control isn't helping.

youre right, I apologize, I had some external factors stressing me out and I was being an asshat, sorry about that

Link to post
4 hours ago, Amorbellum said:

but the webui shortcut takes me to SAB? how to fix?

flip the Basic View/Advanced View togle top right in the docker config.  It's configured in the webui field to use the variables declared in the form but instead of http://[IP]:[PORT:8080]/ you should be able to enter http://[IP]:9090/

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.