[Support] binhex - qBittorrentVPN

[binhex]

59 minutes ago, Elmojo said:

Speaking of, given the bug you noted above, and 'downgrade' update, do I need to do that, or am I okay to stay as I am, since it appears to be working?

wireguard is unaffected by CRL (specific to openvpn)

[Elmojo]

1 hour ago, binhex said:

wireguard is unaffected by CRL (specific to openvpn)

Oh, sorry. I misunderstood.  You said earlier "Please pull latest image at your convenience and switch back to openvpn."

That implied WG in my mind, since it was the only alternative to OpenVPN, my mistake. 

Thanks for the awesome container and 1st class support!

[binhex]

2 minutes ago, Elmojo said:

switch back to openvpn

yes sorry i wasn't clear enough, i meant switch back to openvpn IF you were forced to switch to Wireguard and you WANT to move back (for whatever reason - multi remote endpoint support being the main one).

[ck1]

On 5/3/2024 at 2:40 PM, Fribb said:

yeah, this isn't any different to what I did. Wireguard and the VPN work fine, the curled IP from ifconfig.co/ip is different to the one I get in just my regular browser. However, the WebUI of Qbit is not accessible for whatever reason 

 

the only errors in the linked log file are Standard error outputs from the Start Script which don't look like errors to me.

Hey, did you check that the LAN_NETWORK env is correct?

I just had the same issue where the UI worked in OpenVPN but not wireguard. Correctly setting that variable to the cidr of my lan fixed it 😀

[Fribb]

5 hours ago, ck1 said:

Hey, did you check that the LAN_NETWORK env is correct?

I just had the same issue where the UI worked in OpenVPN but not wireguard. Correctly setting that variable to the cidr of my lan fixed it 😀

 

Thank you, that was it. I don't know why that was set to '192.168.1.0/24'. set that to my correct LAN network and now it works.

[Doublemyst]

Hi there, I have an issue with the binhex-qbittorentvpn docker. Basically, if you have to change all the ports, as they might be already occupied, or any other reason, the WebUI won't start. The only way to get the WebUI to work, is to delete the image (just changing the ports back to original values won't work) and leave all the port values at the original state.

 

Are there some hidden ports, which aren't visible in the docker edit view, which have also to be changed?

[rgreen83]

On 5/6/2024 at 9:27 AM, Doublemyst said:

Hi there, I have an issue with the binhex-qbittorentvpn docker. Basically, if you have to change all the ports, as they might be already occupied, or any other reason, the WebUI won't start. The only way to get the WebUI to work, is to delete the image (just changing the ports back to original values won't work) and leave all the port values at the original state.

 

Are there some hidden ports, which aren't visible in the docker edit view, which have also to be changed?

if your port 8080 is occupied, as mine is by unifi controller, then just change the 8080 variable to an unused port

[wgstarks]

On 5/6/2024 at 10:27 AM, Doublemyst said:

Are there some hidden ports, which aren't visible in the docker edit view, which have also to be changed?

If you have changed the website portion the past you will probably need to be in advanced view mode to see the mapping for the port.

[jortan]

On 9/18/2023 at 11:10 PM, Masterwishx said:

 

Is it working now? 

Tryed some dark themes but have same error. 

Tryed you location same error. 

Also tryed mount /theme to location.. 

 

I'm not using the binhex template for qBittorrent, but just worked out how to get Dark mode working and though I would share.  Should work for this container as well:

 

Theme from:
https://github.com/Carve/qbittorrent-webui-cjratliff.com

 

cd /mnt/user/appdata/binhex-qbittorrentvpn
git clone https://github.com/Carve/qbittorrent-webui-cjratliff.com

 

This creates the theme located at

/mnt/user/appdata/binhex-qbittorrent/qbittorrent-webui-cjratliff.com

 

The path for this inside the container is:

/config/qbittorrent-webui-cjratliff.com

 

qBittorrent Tools, Options | Web UI:

 

Restart qBittorrent container and SHIFT+F5 in your browser to force a complete refresh.

 

Edited May 16 by jortan

[Masterwishx]

34 minutes ago, jortan said:

I'm not using the binhex template for qBittorrent, but just worked out how to get Dark mode working and though I would share.  Should work for this container as well:

 

 

Thanks will check it ,using dark reader at now

[Zimeic]

I have observed weird behaviour since roughly a week ago:

A few minutes after midnight, download and upload speed decrease dramatically to no more than ~60kbps (regular speed is ~10mbps symmetrical). The actual point in time can vary a few minutes, but its always between 00:00 and 00:15. A container restart temporarily fixes this until next midnight.

 

Supervisord log shows nothing interesting as far as i can tell, but i discovered, that according to the logs, i had the same public ip adress before and after restarting the container. However, executing curl https://ifconfig.io in the containers console shows a different ip adress. Aren't these adresses supposed to be same and could this indicate an ip leak of some kind? Neither adresses are my home ip, but still...

docker.txt supervisord.txt

[Mitorar]

I tried this container and it does not seem like it will run well on a ubuntu platform. Some things were missing and i could not get it work.

I could get the privoxyvpn to work tho (maybe because it's avaible through drockstarter?)

 

But would it not be a good idea to make this work under ubuntu/debian too? It's a much larger platform than archlinux and from my point of view it would be good practise to have this work with all major platforms. 

[SelfSD]

On 5/2/2024 at 5:18 PM, betaman said:

I just took a look at the supervisorord.log. Getting this warning:

 

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

 

I'm currently stuck on this issue as well. I've only tried 4 different endpoints so far, rebooting my server, pulling different versions of the container, reinstalling the container and reading up and down the forum and FAQ with no luck.

 

Deleting the OpenVPN folder when on Wireguard didn't help on my end and switching temporarily to OpenVPN also didn't help.

 

I don't actively watch the container so I can't say how long it's been dead either. Last time I interacted with it was 5 days ago.

 

Update: It started working again, so maybe the issue was on PIA's side.

Edited May 22 by SelfSD

[DrBazUK]

On 5/5/2024 at 4:05 AM, Fribb said:

 

Thank you, that was it. I don't know why that was set to '192.168.1.0/24'. set that to my correct LAN network and now it works.

This solved it for me too... Have now completed my migration from original media management (SpaceInvaderOne) to TRASH guides/Ibracorp atomic links...

[malu]

On 5/5/2024 at 12:02 AM, ck1 said:

Hey, did you check that the LAN_NETWORK env is correct?

I just had the same issue where the UI worked in OpenVPN but not wireguard. Correctly setting that variable to the cidr of my lan fixed it 😀

Hi, also using wireguard, set the correct cidr (was set to wrong one before and still worked), didnt fix it for some reason, update didnt fix it either

Edited May 21 by malu

[flinerock]

As of may 7th Radarr and Sonarr no longer imports to Qbittorrent. When i test both they pass but when they both try to download to qbitorrent it says its unavailable. any fix for this. im guessing something changed in This container since both radarr and sonarr have the same issue with qbittorrent. this all was working fine for a long time. Any one have any fixes for this or anymore info. downloading manually sucks lol 

[KevinE]

Setting Up myanonamouse.net seedbox for use with qbt  over VPN

 

I need to execute this command with the session id created with my vpn ip:

sudo curl -c /path/docker/persists/mam.cookies -b 'mam_id=IP_session_cookie' https://t.myanonamouse.net/json/dynamicSeedbox.php

 

What do I enter for the path to mam.cookies?

 

 

[nhatlinh]

On 10/23/2020 at 7:47 AM, _rogue said:

Hey binhex, I think I am having a similar issue to dnLL. I am using PIA and I have switched to the new network already as part of my troubleshooting.

 

For the longest time I always had all my dockers on one independent VLAN so qbittorrentvpn has IP 10.15.1.57 and my unRAID host would be on another VLAN with IP 10.15.0.30. Since a few days ago I can no longer access qbittorrent from my other containers on the 10.15.1.0 VLAN (sonarr, radarr, reverse proxy). I can access it from my other subnets without issue. Like dnLL if I turn off the VPN I can access qbittorrent without issue from the 10.15.1.0 VLAN. 

 

Looking at pfsense I am getting an entry like this (10.15.1.50 is my reverse proxy):

Google-fu tells me that TCP:SA is related to asymmetric routing but trying to configure the floating rules does nothing to help. This kinda makes sense because my reverse proxy would be accessing qbittorrent over the "switch" within unraid/docker but for some reason qbittorrent is sending its reply to the default gateway. Does not explain why this issue only started since the 4.3.0 update but even if I downgrade it does not work again. I even tried a whole new container and still not working.

 

I'm stumped. Is this the same/similar issue as dnLL?

 

I have the same exact issue. I change qbittorrent to another VLAN subnet, and Sonarr can access it from the original VLAN but not from the same subnet. Not sure if maintainer can help with that but thanks to your comment at least i can make another non isolating VLAN network just for qbittorrent. Crude but an decent work around.  

[Low-Volt]

Having an issue where the Docker Container starts with no problem, I can access the WebGUI and all my *arr Containers can as well, then sometime later (usually within an hour or two) the WebGUI becomes unreachable and requests time out. The Container remains running, however nothing can access it and the log watchdog doesn't flag any errors.

 

Not using VPN as I'm using another container to manage that specifically (more info below).

 

Cache is about 60% full so its not a storage problem. Other containers using the same network container (--network=container:GluetunVPN) aren't having any issues, including a linuxserver qBitTorrent container which was serving as my backup.

 

Only started this week as far as I know.

 

Thanks for the help.

Command execution.txt supervisord.log

Edited Tuesday at 10:04 AM by Low-Volt
Typo Fix

[DaveG]

Afternoon,

Ive installed binhex-qbittorrentvpn and for the life of me the password will not work 'adminadmin'.

Ive uninstalled and reinstalled. Edited the config file with early posts on this topic. That didnt work. Deleted the config file and reinstalled the docker image and it still wont let me in.

Ive attached Log File and Docker Run file for you too look at.

Any help would be appreciated.

Thanks

Dave

docker run.txt Log File.txt

Edited Tuesday at 07:42 PM by DaveG
Spelling

[DaveG]

Great news! I have manage to work out what the password is..

 

For those who have this problem...

 

Delete your supervisord.log ( location on my system is /mnt/user/appdata/binhex-qbittorrentvpn)

Restart qBittoreent

Open up the the fresh instance of supervisord.log and you'll see the temporary password (Towards the bottom)

Enter this with admin as you username and voila!

Go into Tools -> Options -> WebUi and change to suit you need.

 

 

[betaman]

I got a new modem yesterday from my cable company. Router config didn't change. I'm using wireguard with PIA in the docker config. Having DNS issues and not sure what I need to configure to get it working again?  This is what I see in the supervisord.log:

 

2024-05-29 08:58:41,096 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

2024-05-29 08:58:41,107 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://ifconfig.co/port/55162' failed json download, marking as failed

2024-05-29 09:00:06,291 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:01:31,490 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:02:56,690 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:04:21,872 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:05:47,042 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:07:12,241 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-05-29 09:08:37,447 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

 

I also can't find /tmp/dnsfailure log file.

 

EDIT: Idiot alert...never thought to restart the containers after the modem change. Doh..all fixed.

Edited Thursday at 01:21 PM by betaman

[btother]

Ever since the latest update in early May, I keep getting this error when downloading a torrent.  I have plenty of free space (445 GB) and thus have no idea what the cause or fix for this issue is.

 

Please help!

 

[malu]

On 5/23/2024 at 12:32 AM, KevinE said:

Setting Up myanonamouse.net seedbox for use with qbt  over VPN

 

I need to execute this command with the session id created with my vpn ip:

sudo curl -c /path/docker/persists/mam.cookies -b 'mam_id=IP_session_cookie' https://t.myanonamouse.net/json/dynamicSeedbox.php

 

What do I enter for the path to mam.cookies?

 

 

did that as well, its just the UNIX path to a file that contains the session cookie that you can get from preferences>security on the site

[ptr78]

On 5/3/2024 at 12:03 PM, binhex said:

Hi guys, i don't want to be snowed under with support due to the PIA CRL issue so i have taken the executive decision of downgrading openssl to 3.2.0 (ignores the issue), this will get openvpn up and running again whilst we await to see if PIA will actually do anything to address the problem.

 

Does this cause a security issue or are CRLs handled as they should (AirVPN) with this openssl version?