[[Support] binhex - qBittorrentVPN]

3 minutes ago, binhex said:

yep its simplicity itself!, follow Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Man, I'm sorry for not checking the FAQ beforehand. I usually do. Didn't even think about simply downgrading the whole container. Thank you, as always, for being patient with us.

[[Support] binhex - qBittorrentVPN]

@binhex Is there any easy way to downgrade qBittorrent to < v4.2.5 inside the container without breaking things? Versions >= v4.2.5 permabroke importing stuff in sonarr/radarr due to QBt changing things. E.g. this sonarr PR will fix it: https://github.com/Sonarr/Sonarr/pull/3346

[[Support] binhex - qBittorrentVPN]

2 hours ago, binhex said:

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

Awesome, thanks for that. Works as expected, both multiline and port forwarding on nextgen.

[[Support] binhex - qBittorrentVPN]

Since around the time of the last update, qBitTorrent is stuck at 'Downloading metadata' after the internect connection reestablishes every 2 hours, only a container restart fixes this. Strangely enough, other containers, which use the containers network stack, actually can establish connections.

 

Nothing conclusive in the log afaict, but here it is anyways:

 

log.txt

[[Support] binhex - qBittorrentVPN]

On 8/20/2020 at 3:19 PM, binhex said:

If you do spot a problem then please remove any sensitive info and then attach the entire log, preferably with debug set to true

Sent from my CLT-L09 using Tapatalk
 

Just a quick update, running perfectly fine now. Automatic reconnect and handling of iptables/spinning up of the different program instances works as expected. Cheers!

[[Support] binhex - qBittorrentVPN]

13 minutes ago, binhex said:

If you do spot a problem then please remove any sensitive info and then attach the entire log, preferably with debug set to true

Sent from my CLT-L09 using Tapatalk
 

Wilco!

 

Regarding port forwarding on their NextGen servers, it seems to indeed be possible, it's just a new procedure. Should be fairly easy to implement, I'll try it myself once I got a bit of time on my hands:

https://github.com/thrnz/docker-wireguard-pia/blob/master/extra/pf.sh

[[Support] binhex - qBittorrentVPN]

5 hours ago, binhex said:

i took a look at this image and did spot a long standing issue with pgrep causing issues, this bug has been fixed upstream and the image has been rebuilt with the fix, please pull down the latest image and let me know if it now works correctly when reconfiguration is required (i.e. openvpn drop or port closed).

Just pulled it, will test for a few days and report back! Thanks for your excellent support mate.

[[Support] binhex - qBittorrentVPN]

1 hour ago, thatsthefrickenlightning said:

Thank you very much for this. I had to turn my server off for some maintenance and I thought that was the problem, but it was this. Next-gen config files work for me, but no actual torrent client activity until port forwarding is supported. Any ideas when that will be?

No idea, unfortunately. Though I'll probably switch to a different container, since the binhex containers still tend to hang a lot and don't reconnect automatically, they often get stuck at steps like "marking for reconfigure", requiring daily restarts and horrible availability, even if the VPN servers themselves are stable enough.

[[Support] binhex - qBittorrentVPN]

As we all know, PIA is currently moving their infrastructure, which results in pretty terribly reliability and constant connection issues when using their CurrentGen Network. Today, however, I discovered that they offer OpenVPN confs for their NextGen servers: https://www.privateinternetaccess.com/pages/download

 

AFAICT they work reliable. Only way to use them currently is to set the STRICT_PORT_FORWARD ENV variable to "no", since their NextGen network doesn't seem to support port forwarding yet.