Jump to content

[Support] binhex - qBittorrentVPN

binhex

By binhex
in Docker Containers

Recommended Posts

Recommended

Posted by binhex,

Need further help?, please >click< here and follow the instructions.

Further help

Recommended by binhex

0 reactions

Go to this post
Recommended

Posted by binhex,

This also looks like a neat and fast solution, but PLEASE for the love of god change the password from adminadmin after doing this:- https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1330952

qBittorrent password workaround

Recommended by binhex

0 reactions

Go to this post
Recommended

Posted by binhex,

Looks like a PIA issue with the CRL inline in the ovpn files being malformed, see here:- https://github.com/binhex/arch-qbittorrentvpn/issues/233#issuecomment-2088192316

PIA OpenVPN CRL issue

Recommended by binhex

0 reactions

Go to this post
  • Replies 3.9k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

nraygun
nraygun

FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.   Add this line under [Preferences]

ThEdOtOr
ThEdOtOr

Create a necessary folder in   \\yourservername\appdata\binhex-qbittorrentvpn\qBittorrent    Create a folder called ssl     Open up terminal and type,  

cloudyb
cloudyb

For me radarr and sonarr picked up my changed password no problem. The steps I took were: -Edited the binhex/arch-qbittorrentvpn container: Changed the Repository field to binhex/arch-qbittorre

Posted Images

wgstarks Mentor

wgstarks

Posted
Posted
7 minutes ago, Zarroc said:

and it brought it back as the updated docker thats hot garbage currently. wonderful

You can install any version. Go to the dockerhub link in the first post and copy the tag number for the version you want. In the docker configuration add a colon and the tag number after the binhex/arch-qbittorrentvpn in the repository field.

Link to comment
Mlatx Apprentice

Mlatx

Posted
Posted
2 hours ago, wgstarks said:

This sounds like a bug that has already been reported in the qbit forum where the details section is expanded to fill the entire window. There is a spot you can grab on the bar at the top of that section and drag down to reveal the list of torrents. I fixed mine by switching to an alternate webUI. This had the advantage of also letting me turn off dark mode.

 

 

Yup this is it. Thank you for responding. I can drag it down to see the content. I'll check out the other UI's.

Link to comment
captainkegs Noob

captainkegs

Posted
Posted

I'm unable to access Qbit Web GUI because the page times out.

I'm running qbit by binhex as a docker container on my Unraid 6.12.10.

 
According to the log the VPN and Qbit are running just fine, however, I cannot access the Web GUI for qbit once it has started. I get a timeout and the page won't load. I usually access hosts on my LAN via another subnet but I've included both my LAN and Subnet IP ranges in the LAN_NETWORK section of the container. I also tried accessing the GUI directly from my LAN but it also times out. I am forwarding port 8080 to 8083 but I've confirmed the container is properly forwarding to that port and I have no conflicting ports. I have attached logs for reference. Any guidance would be much appreciated.

supervisord.log commandexecution.txt

Link to comment
lightsout Rookie

lightsout

Posted
Posted

I am running qbitorrentvpn with airvpn and wireguard. All works great. I also have a wireguard vpn on my asus router that I can turn on to access my home lan remotely.

 

When I do this I can access all my other arr stack dockers remotely. (through nzb360 or web browser, such as sab, radarr, sonarr, etc.)

But I cannot access qbit remotely, I believe this is related to the vpn in this docker. My home lan is simple, 192.168.1.0/24 everything on that same network, no vlans or docker networks.

I have entered the home lan address (192.168.1.0/24) in the config for this docker. Is there something I need to do in my wireguard config file inside the docker container so that I can access qbit like all my other arrs from outside the network.

Hopefully the way I have explained it makes sense.

Link to comment
wgstarks Mentor

wgstarks

Posted
Posted
3 minutes ago, lightsout said:

Hopefully the way I have explained it makes sense.

When you use WireGuard is your IP address in the 192.168.1.0/24 range? I suspect it’s not and this is the problem. Any address outside that range won’t be able to access the webUI. You’ll need to add the network used by WireGuard to the docker configuration.

Link to comment
crumbling-tug-of-war7809 Noob

crumbling-tug-of-war7809

Posted
Posted (edited)

Can anyone help me get this container working again? My server was down for a couple weeks while I waited for Intel to send a replacement CPU. Everything worked PERFECTLY two weeks ago before I booted the server down. I just got it back up today and binhex-qbittorrentvpn won't work. It's acting like it can't connect to the VPN but nothing has changed. I even generated a new wireguard key just to make sure that wasn't the issue. Nothing seems to fix it. I see the following output in the console:

 

2024-10-04 22:08:35,276 DEBG 'start-script' stdout output:
--------------------

2024-10-04 22:08:35,278 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2024-10-04 22:08:35,282 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2024-10-04 22:08:35,291 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-10-04 22:08:35,297 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2024-10-04 22:08:35,299 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2024-10-04 22:08:35,300 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.65.70.20/32 dev wg0

2024-10-04 22:08:35,307 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2024-10-04 22:08:35,310 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2024-10-04 22:08:35,320 DEBG 'start-script' stderr output:
could not detect a useable init system

2024-10-04 22:08:35,355 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2024-10-04 22:08:35,356 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2024-10-04 22:08:35,358 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2024-10-04 22:08:35,359 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2024-10-04 22:08:35,363 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2024-10-04 22:08:35,364 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-10-04 22:08:35,367 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2024-10-04 22:08:36,484 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-10-04 22:08:46,517 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

2024-10-04 22:08:56,537 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

2024-10-04 22:09:06,558 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

2024-10-04 22:09:16,579 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
[info] Show name servers defined for container

2024-10-04 22:09:16,580 DEBG 'start-script' stdout output:
# Generated by resolvconf
nameserver 10.64.0.1

2024-10-04 22:09:16,580 DEBG 'start-script' stdout output:
[info] Show contents of hosts file

2024-10-04 22:09:16,581 DEBG 'start-script' stdout output:
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.2      5af765d222d2

2024-10-04 22:09:16,582 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2024-10-04 22:09:16,583 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2024-10-04 22:12:16,647 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-10-04 22:12:16,654 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.65.70.20 different, marking for reconfigure

2024-10-04 22:12:16,659 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2024-10-04 22:12:16,659 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2024-10-04 22:12:16,675 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2024-10-04 22:12:16,678 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2024-10-04 22:12:16,797 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2024-10-04 22:12:46,603 DEBG 'start-script' stdout output:
[info] Sending 'down' command to WireGuard due to dns failure...

2024-10-04 22:12:46,604 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2024-10-04 22:12:46,612 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-10-04 22:12:46,620 DEBG 'start-script' stderr output:
[#] ip -4 rule delete table 51820

2024-10-04 22:12:46,626 DEBG 'start-script' stderr output:
[#] ip -4 rule delete table main suppress_prefixlength 0

2024-10-04 22:12:46,633 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2024-10-04 22:12:46,718 DEBG 'start-script' stderr output:
[#] resolvconf -d wg0 -f

2024-10-04 22:12:46,724 DEBG 'start-script' stderr output:
could not detect a useable init system

2024-10-04 22:12:46,755 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-10-04 22:12:46,758 DEBG 'start-script' stderr output:
[#] '/root/wireguarddown.sh'

2024-10-04 22:12:46,762 DEBG 'start-script' stdout output:
[info] WireGuard interface 'down'

2024-10-04 22:12:46,764 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2024-10-04 22:12:46,769 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2024-10-04 22:12:46,776 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2024-10-04 22:12:46,782 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2024-10-04 22:12:46,784 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2024-10-04 22:12:46,785 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.65.70.20/32 dev wg0

2024-10-04 22:12:46,792 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2024-10-04 22:12:46,795 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2024-10-04 22:12:46,801 DEBG 'start-script' stderr output:
could not detect a useable init system

2024-10-04 22:12:46,835 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2024-10-04 22:12:46,836 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2024-10-04 22:12:46,838 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2024-10-04 22:12:46,839 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2024-10-04 22:12:46,843 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2024-10-04 22:12:46,844 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2024-10-04 22:12:46,847 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2024-10-04 22:12:47,959 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-10-04 22:12:57,980 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

2024-10-04 22:13:08,001 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

2024-10-04 22:13:18,022 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

2024-10-04 22:13:28,043 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'...
[info] Show name servers defined for container

2024-10-04 22:13:28,043 DEBG 'start-script' stdout output:
# Generated by resolvconf
nameserver 10.64.0.1

2024-10-04 22:13:28,044 DEBG 'start-script' stdout output:
[info] Show contents of hosts file

2024-10-04 22:13:28,044 DEBG 'start-script' stdout output:
127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.2      5af765d222d2

2024-10-04 22:13:28,046 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2024-10-04 22:13:28,047 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

 

Comand Execution.txt

supervisord.log

Edited by crumbling-tug-of-war7809
adding log files
Link to comment
lightsout Rookie

lightsout

Posted
Posted
On 10/4/2024 at 6:43 PM, wgstarks said:

When you use WireGuard is your IP address in the 192.168.1.0/24 range? I suspect it’s not and this is the problem. Any address outside that range won’t be able to access the webUI. You’ll need to add the network used by WireGuard to the docker configuration.

No it's intentionally not. It's 192.168.0.0/24

 

I added that to the wg config and qbit wouldn't load. Any help on how to do that.

 

Also how would I know what ip range to add for my phone on Mobile data.

Link to comment
wgstarks Mentor

wgstarks

Posted
Posted
10 minutes ago, lightsout said:

No it's intentionally not. It's 192.168.0.0/24

 

I added that to the wg config and qbit wouldn't load. Any help on how to do that.

 

Also how would I know what ip range to add for my phone on Mobile data.

Add any networks you want to be able to access from to the LAN_NETWORK field. Comma separated. I would recommend not exposing your Unraid server to the internet. Use OpenVPN or Tailscale to access the webUI on your local network.

Link to comment

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.

×
Go to topic listing
×
×
  • Create New...