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!

On 3/28/2020 at 7:52 AM, chrisp1992 said:

how can I check that all of the traffic is truly going through the VPN for this Docker?

Ask an you shall receive. 😃

1. https://am.i.mullvad.net/
2. https://am.i.mullvad.net/torrent

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?

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

 

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

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.

 

I installed this other repo, it works perfectly, no stalled connections

 

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.

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!

12 hours ago, binhex said:

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

So any idea how to debug the webUI not working when vpn is enabled?

5 hours ago, dnLL said:

So any idea how to debug the webUI not working when vpn is enabled?

no idea without a full log, see here:-

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

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

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

 

Im having a really hard time changing the port 8080 to something, anything else.

 

why did you make it the same port as sab?

 

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

 

please can someone help?

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.

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

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

11 hours ago, Gog said:

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

i edited the WEBUI port?

do you mind looking at some screenshots of my configs?

https://imgur.com/a/Ycu6Rpm

48 minutes ago, Amorbellum said:

i edited the WEBUI port?

do you mind looking at some screenshots of my configs?

https://imgur.com/a/Ycu6Rpm

almost there.  click on the Edit button for host port 3.  Container port and host port BOTH need to be 9090

1 hour ago, Gog said:

almost there.  click on the Edit button for host port 3.  Container port and host port BOTH need to be 9090

well I thought so but its Greyed out, wont let me edit.

If I create a new port entry is it the same?

well I thought so but its Greyed out, wont let me edit.
If I create a new port entry is it the same?

remove it and create a new one

Sent from my SM-G930W8 using Tapatalk

4 hours ago, Gog said:

remove it and create a new one

Sent from my SM-G930W8 using Tapatalk
 

alright! that worked if i type in HOSTIP:9090

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

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/

My torrents are all stalling from going to slow. Finally using PIA to have the Strict_Port_Forwarding labeled 'yes'. (Also tried it at 'no with same stalling issue). Torrents coming in from Radarr/Sonarr with Proxy turned on from enabled Privoxy. I have everything set up for a min. of 2 peers, and all qbittorrent settings set up the way I had them on my local machine (not in a docker). Anyone else have similar issues on their initial startup and what did you do to fix this?

 

Here is a snippet from my logs showing the endpoint that I am using is in the list of endpoints supporting port forwarding.

 

2020-04-18 12:16:18,964 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

 

2020-04-18 12:16:18,965 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com

Hi, in the WebUI of qBittorrent the priority field is selected but is not shown.

With the developer tools the table head of priority is set to invisible.

<th title="#" style="width: 30px;" class="column_priority invisible">#</th>