[Support] binhex - qBittorrentVPN


Recommended Posts

Hello,

 

I am unable to access the webui although everything else works fine as far as I can tell. I was in vuetorrent, unticked altwebui to go back to the original ui, was in the RSS section for a moment, and when i ticked the altwebui box to go back to vuetorrent, it crashed and I have been unable to get the UI to work since. confirmed the config (attached) is set to "false" for altwebui.  I have updated to latest, which didnt change anything. I went back down to 4.3.9-2-01 which is where I was originally.

When trying to access the webui, it tries for a couple minutes before erroring out on an html version of the ui https://imgur.com/mxhG0nY [/img].

I saw one post with someone who mentioned something similar, they were successful toggling wireguard on then going back to openvpn in the container settings, but that didnt work either.

Thanks for the help!
 

 

Command execution.txt supervisord.log qBittorrent.conf

 

 

Edited by rexorexor
  • Like 1
Link to comment
15 hours ago, rexorexor said:

Hello,

 

I am unable to access the webui although everything else works fine as far as I can tell. I was in vuetorrent, unticked altwebui to go back to the original ui, was in the RSS section for a moment, and when i ticked the altwebui box to go back to vuetorrent, it crashed and I have been unable to get the UI to work since. confirmed the config (attached) is set to "false" for altwebui.  I have updated to latest, which didnt change anything. I went back down to 4.3.9-2-01 which is where I was originally.

When trying to access the webui, it tries for a couple minutes before erroring out on an html version of the ui https://imgur.com/mxhG0nY [/img].

I saw one post with someone who mentioned something similar, they were successful toggling wireguard on then going back to openvpn in the container settings, but that didnt work either.

Thanks for the help!
 

 

Command execution.txt 1.36 kB · 0 downloads supervisord.log 105 kB · 0 downloads qBittorrent.conf 4.24 kB · 0 downloads

 

 

im experiencing this too

  • Like 1
Link to comment

Hello!
after I had a hardwere issue, all of my docker apps dissapeard, 

I reinstalled them from `previous apps`, and it looks like I'm having permission issues on `binhex-qbittorrentvpn` app. 

It has read permissions but it cannot write.

From logs:

 

File error alert. Torrent... error: Permission denied


When it tries to download anything, it immidietly errors out.

 

How can I fix this?

 

Edit: attached an image of the config of the container.

 

I've read that for others the solution was to delete everything and reinstall.

I'd really like to avoid that as I have over a 1000 torrents with different categories etc.

 

Edit2: If I reset a torrent that was already existing before the hardware failure, the qbit is able to actually download it. Only newly added torrents are erroring out

 

image.png

Edited by VRA
adding new information
Link to comment

I have fixed the issue by running the `Tools -> New Permissions`!

Running it broke sonnar and radarr but those I can resetup without any problem, so I'm happy with the result.

Edited by VRA
Link to comment

If you have the "Fix Common Problems" plugin installed it adds an extra tool called "Docker Safe New Perms" that excludes the appdata directory and any other directories you specify and is generally recommended.  

  • Like 1
Link to comment

First thanks for this nice container and very good documentation binhex :)

 

I've checked some youtube videos and guides but cannot find any solution for this error.

Quote

Unable to successfully download PIA json payload from URL

 

I tried to change the location and checked internet access from the container.

 

Everythings seems to be fine.

 

Do you have any clue what I am missing?

Link to comment

Since the last update I havnt been able to reach the webui. When looking at the logs I see this in red:

 

VERIFY ERROR: depth=1, error=certificate has expired: C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, [email protected], serial=10148936457887096835
2024-04-09 03:49:08 Sent fatal SSL alert: certificate expired
2024-04-09 03:49:08 OpenSSL: error:0A000086:SSL routines::certificate verify failed:
2024-04-09 03:49:08 TLS_ERROR: BIO read tls_read_plaintext error
2024-04-09 03:49:08 TLS Error: TLS object -> incoming plaintext read error
2024-04-09 03:49:08 TLS Error: TLS handshake failed

 

My AirVPN is still active and I tried to download another certificate but no joy. Im a noob at this and managed to install this a couple of years back through spaceinvader I think so now Im totaly out of my depth trying to reinstall it O.o

 

Any suggestions? Any way to roll back to previous version?

Link to comment
1 hour ago, binhex said:

This is the issue, you need to talk to AirVPN about this if there is no newer certificate.

Thank you for confirming that and pointing me in the right direction! I messed around and tried the wireguard option from AirVPN (must be "new", havnt seen it before) and eventually I got it to work again. However not to port 8787 as before but to 8080 (that I used for sabnzbdvpn). Hopefully I will work out that later...

 

Thanks! 

Link to comment
On 4/8/2024 at 1:31 PM, VRA said:

Hello!
after I had a hardwere issue, all of my docker apps dissapeard, 

I reinstalled them from `previous apps`, and it looks like I'm having permission issues on `binhex-qbittorrentvpn` app. 

It has read permissions but it cannot write.

From logs:

 

File error alert. Torrent... error: Permission denied


When it tries to download anything, it immidietly errors out.

 

How can I fix this?

 

Edit: attached an image of the config of the container.

 

I've read that for others the solution was to delete everything and reinstall.

I'd really like to avoid that as I have over a 1000 torrents with different categories etc.

 

Edit2: If I reset a torrent that was already existing before the hardware failure, the qbit is able to actually download it. Only newly added torrents are erroring out

 

image.png

 

The issue happened again after a restart of the server.

I fixed it again, this time using `Docker Safe New Permissions`.


However, after a few hours it returned one more time. And now running the Docker Safe New Permissions is not helping :(
If anyone has any ideas on what I could do to fix it I would be grateful for any help.


EDIT:
The problem seems to be with the config location of qbittorrent. 
The `Fix Common Problems` plugin told me to change the appdata location to `cache`. This is what broke qbit.
I moved it back to array for now, and it started to work again.
However, if its better to have the appdata on cache, it would be nice to figoure it out and solve this issue somehow.

Edited by VRA
Link to comment
On 4/9/2024 at 8:21 PM, VRA said:

I moved it back to array for now, and it started to work again.
However, if its better to have the appdata on cache, it would be nice to figoure it out and solve this issue somehow.

left click the container and click on the 'show more settings....'  and it will reveal the path for /config, i would assume its pointing at your array, if you want it to use your cache drive then stop the container, move the files to the cache drive and then change the host path to point at the cache drive location where you moved the files to.

Link to comment

Hi,

 

For some time everything was working but my Mullvad subscription ended. I bought Windscribe, downloaded the configuration file, and simply replaced it with the wg0.conf from Windscribe. 

 

1. For a few minutes after starting I can't access the webgui. After several minutes I can.

2. There's no internet connection.

 

I'm attaching the logs.

 

Can you help me please?

 

Spoiler

2024-04-11 19:15:53,983 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

 

2024-04-11 19:15:53,996 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

 

2024-04-11 19:15:54,007 DEBG 'start-script' stderr output:

[#] ip link add wg0 type wireguard

 

2024-04-11 19:15:54,010 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

 

2024-04-11 19:15:54,012 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.67.135.53/32 dev wg0

 

2024-04-11 19:15:54,022 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

 

2024-04-11 19:15:54,025 DEBG 'start-script' stderr output:

[#] resolvconf -a wg0 -m 0 -x

 

2024-04-11 19:15:54,033 DEBG 'start-script' stderr output:

could not detect a useable init system

 

2024-04-11 19:15:54,073 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

 

2024-04-11 19:15:54,074 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

 

2024-04-11 19:15:54,077 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

 

2024-04-11 19:15:54,080 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

 

2024-04-11 19:15:54,086 DEBG 'start-script' stderr output:

[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

 

2024-04-11 19:15:54,088 DEBG 'start-script' stderr output:

[#] iptables-restore -n

 

2024-04-11 19:15:54,092 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

 

2024-04-11 19:18:37,499 DEBG 'watchdog-script' stdout output:

[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

 

2024-04-11 19:19:35,626 DEBG 'start-script' stdout output:

[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

 

2024-04-11 19:19:35,630 DEBG 'start-script' stdout output:

[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

 

2024-04-11 19:19:45,660 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

 

2024-04-11 19:19:55,713 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

 

2024-04-11 19:20:05,754 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

 

2024-04-11 19:20:15,783 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-04-11 19:20:15,787 DEBG 'start-script' stdout output:

# Generated by resolvconf

nameserver 10.64.0.1

 

2024-04-11 19:20:15,788 DEBG 'start-script' stdout output:

[info] Show contents of hosts file

 

2024-04-11 19:20:15,793 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.19.0.2      5376661c1279

 

2024-04-11 19:20:15,814 DEBG 'start-script' stdout output:

[info] WireGuard interface 'up'

 

2024-04-11 19:20:15,866 DEBG 'start-script' stdout output:

[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

 

Edited by Gobblerpl
clarification of point 1
Link to comment

Hello,
Am I correct that the current version of QBittorentVPN still uses "XZ Utils 5.6.1" ?
If i'm wrong, sorry, where can I find the latest "safe" one or could you orient me to the post I missed ?
If yes, is there a plan to downgrade to a different version of XZ Utils ?
https://tukaani.org/xz-backdoor/
Thanks a lot
 

Container ID: d238565ad9e2
xz (XZ Utils) 5.6.1

Container ID: d238565ad9e2
By: binhex/arch-qbittorrentvpn


 

Link to comment
On 3/15/2024 at 11:03 PM, wgstarks said:

That file should have been populated when you enabled privoxy with default settings. Most are commented but I know the listen port is enabled.

it was permissions, it wasnt allowed to create the files so i changed them and BOOM we are cooking on gas!

Link to comment

Anyone have any ideas?

 

The Web UI just won't load. I've disabled the VPN so that strikes that out.

 

2024-04-15 04:58:27.853379 [info] Host is running unRAID
2024-04-15 04:58:27.885629 [info] System information Linux 222c668176a2 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
2024-04-15 04:58:27.922436 [info] PUID defined as '99'
2024-04-15 04:58:28.008334 [info] PGID defined as '100'
2024-04-15 04:58:28.125813 [info] UMASK defined as '000'
2024-04-15 04:58:28.169173 [info] Permissions already set for '/config'
2024-04-15 04:58:28.209140 [info] Deleting files in /tmp (non recursive)...
2024-04-15 04:58:28.258098 [info] VPN_ENABLED defined as 'no'
2024-04-15 04:58:28.282725 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2024-04-15 04:58:28.321015 [info] WEBUI_PORT defined as '8282'
2024-04-15 04:58:28.358829 [info] Starting Supervisor...
2024-04-15 04:58:28,769 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-04-15 04:58:28,770 INFO Set uid to user 0 succeeded
2024-04-15 04:58:28,775 INFO supervisord started with pid 7
2024-04-15 04:58:29,777 INFO spawned: 'start-script' with pid 62
2024-04-15 04:58:29,779 INFO spawned: 'watchdog-script' with pid 63
2024-04-15 04:58:29,780 INFO reaped unknown pid 8 (exit status 0)
2024-04-15 04:58:29,800 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2024-04-15 04:58:29,800 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-04-15 04:58:29,800 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-04-15 04:58:29,800 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22364966405840 for <Subprocess at 22364969660432 with name start-script in state RUNNING> (stdout)>
2024-04-15 04:58:29,801 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22364966397200 for <Subprocess at 22364969660432 with name start-script in state RUNNING> (stderr)>
2024-04-15 04:58:29,801 INFO exited: start-script (exit status 0; expected)
2024-04-15 04:58:29,801 DEBG received SIGCHLD indicating a child quit
2024-04-15 04:58:29,819 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2024-04-15 04:58:29,820 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2024-04-15 04:58:29,879 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2024-04-15 04:58:29,885 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8282...

2024-04-15 04:58:30,330 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8282

 

image.thumb.png.44feee4c01f4838b11af7d47dd0ff669.png

Link to comment
On 4/11/2024 at 7:22 PM, Gobblerpl said:

Hi,

 

For some time everything was working but my Mullvad subscription ended. I bought Windscribe, downloaded the configuration file, and simply replaced it with the wg0.conf from Windscribe. 

 

1. For a few minutes after starting I can't access the webgui. After several minutes I can.

2. There's no internet connection.

 

I'm attaching the logs.

 

Can you help me please?

 

  Reveal hidden contents

2024-04-11 19:15:53,983 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

 

2024-04-11 19:15:53,996 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

 

2024-04-11 19:15:54,007 DEBG 'start-script' stderr output:

[#] ip link add wg0 type wireguard

 

2024-04-11 19:15:54,010 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

 

2024-04-11 19:15:54,012 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.67.135.53/32 dev wg0

 

2024-04-11 19:15:54,022 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

 

2024-04-11 19:15:54,025 DEBG 'start-script' stderr output:

[#] resolvconf -a wg0 -m 0 -x

 

2024-04-11 19:15:54,033 DEBG 'start-script' stderr output:

could not detect a useable init system

 

2024-04-11 19:15:54,073 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

 

2024-04-11 19:15:54,074 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

 

2024-04-11 19:15:54,077 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

 

2024-04-11 19:15:54,080 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

 

2024-04-11 19:15:54,086 DEBG 'start-script' stderr output:

[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

 

2024-04-11 19:15:54,088 DEBG 'start-script' stderr output:

[#] iptables-restore -n

 

2024-04-11 19:15:54,092 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

 

2024-04-11 19:18:37,499 DEBG 'watchdog-script' stdout output:

[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

 

2024-04-11 19:19:35,626 DEBG 'start-script' stdout output:

[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

 

2024-04-11 19:19:35,630 DEBG 'start-script' stdout output:

[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

 

2024-04-11 19:19:45,660 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

 

2024-04-11 19:19:55,713 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

 

2024-04-11 19:20:05,754 DEBG 'start-script' stdout output:

[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

 

2024-04-11 19:20:15,783 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-04-11 19:20:15,787 DEBG 'start-script' stdout output:

# Generated by resolvconf

nameserver 10.64.0.1

 

2024-04-11 19:20:15,788 DEBG 'start-script' stdout output:

[info] Show contents of hosts file

 

2024-04-11 19:20:15,793 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.19.0.2      5376661c1279

 

2024-04-11 19:20:15,814 DEBG 'start-script' stdout output:

[info] WireGuard interface 'up'

 

2024-04-11 19:20:15,866 DEBG 'start-script' stdout output:

[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

 

Reinstall worked

Link to comment
On 4/9/2024 at 12:12 PM, Adam_ said:

Thank you for confirming that and pointing me in the right direction! I messed around and tried the wireguard option from AirVPN (must be "new", havnt seen it before) and eventually I got it to work again. However not to port 8787 as before but to 8080 (that I used for sabnzbdvpn). Hopefully I will work out that later...

 

Thanks! 

Thanks, this worked for me as well!

  1. Go to AirVPN's website > client area > Generate new config
  2. Choose advanced
  3. Choose Linux > Wireguard UDP 1637 lightweight and efficient UDP connection
  4. Scroll down and choose your country (tip: Switerland)
  5. Scroll all the way down and generate and config file
  6. Place the config file in your appdata/wireguard folder (for my instance: /mnt/user/appdata/binhex-qbittorrentvpn/wireguard)
  7. Go to the docker settings and change container variable "VPN CLIENT" from openvpn to wireguard
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.