[Support] binhex - qBittorrentVPN


Recommended Posts

1 minute ago, wgstarks said:

This is your issue. It may be that the server is down. Can you try another?

I saw that line. I don't think I can without deleting the port forward and reconfiguring the whole thing. I'd hate to do that if it's just not gonna work anyway. I was hoping someone would know if something had changed with the way we have to config for Mullvad or whatever. I'm not too well versed in this stuff, so I hate to monkey around in there and break it more without some guidance. ;)

Link to comment
On 9/25/2022 at 9:11 AM, CiscoCoreX said:

After upgrading to unraid 6.11 i notice for the first time I run into some problems with my qbittorrent (4.4.5-1-01). The VPN is disable.
For the first i couldn't login to the webgui. Then I try to stop the container from the unraid. But it fails big time.
This is the error i found:

 

Sep 25 08:44:56 Tower root: Error response from daemon: cannot stop container: binhex-qbittorrentvpn: tried to kill container, but did not receive an exit event
Sep 25 08:44:56 Tower root: Error response from daemon: error while removing network: network br0 id f564b69135e76d78b145214998f5739d7ec44224c468282466b2c9f4702a8b3b has active endpoints


I also was trying to KILL it, but it didn't help.
 

image.png

And this also prevent me for stopping the Array.
Found this info:
 

Sep 25 08:49:20 Tower root: umount: /mnt/cache: target is busy.
Sep 25 08:49:20 Tower emhttpd: shcmd (471): exit status: 32
Sep 25 08:49:20 Tower emhttpd: Retry unmounting disk share(s)...
Sep 25 08:49:25 Tower emhttpd: Unmounting disks...
Sep 25 08:49:25 Tower emhttpd: shcmd (472): umount /mnt/cache
Sep 25 08:49:25 Tower root: umount: /mnt/cache: target is busy.
Sep 25 08:49:25 Tower emhttpd: shcmd (472): exit status: 32
Sep 25 08:49:25 Tower emhttpd: Retry unmounting disk share(s)...
Sep 25 08:49:30 Tower emhttpd: Unmounting disks...
Sep 25 08:49:30 Tower emhttpd: shcmd (473): umount /mnt/cache
Sep 25 08:49:30 Tower root: umount: /mnt/cache: target is busy.
Sep 25 08:49:30 Tower emhttpd: shcmd (473): exit status: 32
Sep 25 08:49:30 Tower emhttpd: Retry unmounting disk share(s)...


I ended up to reboot my unraid server. :(

 

On 9/25/2022 at 8:57 PM, CiscoCoreX said:

It happens again, i was downloading with qbittorret and after 100GB downloading, my qbittorent stop responding, all the other containers are working. But my unraid gui also stopped, can't login.

Hi all.

 

I'm having this issue also. Is there a solution for this?

Link to comment
9 hours ago, Elmojo said:
[crit] 'us-atl-105.mullvad.net' cannot be resolved, possible DNS issues, exiting...

also change your dns, i see you are using the older name servers which includes the flaky PIA name servers (209.222.x.x) which maybe causing the intermittent lookup failure, the default list of NAME_SERVERS should now be set as:-

84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

 

Link to comment
8 hours ago, Elmojo said:

I saw that line. I don't think I can without deleting the port forward and reconfiguring the whole thing. I'd hate to do that if it's just not gonna work anyway. I was hoping someone would know if something had changed with the way we have to config for Mullvad or whatever. I'm not too well versed in this stuff, so I hate to monkey around in there and break it more without some guidance. ;)

I’ve never used Mullvad, only PIA, but I know with PIA I can just edit the ovpn file and change the server specified there.

 

Hopefully following @binhex’s suggestion for modifying the dns settings will correct your issue. If not, post back.

Link to comment
1 hour ago, binhex said:

also change your dns, i see you are using the older name servers which includes the flaky PIA name servers (209.222.x.x) which maybe causing the intermittent lookup failure, the default list of NAME_SERVERS should now be set as:-

84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

 

Ok, I changed to those you listed. Where should I have gotten the new list from, out of curiosity?

 

1 hour ago, wgstarks said:

I’ve never used Mullvad, only PIA, but I know with PIA I can just edit the ovpn file and change the server specified there.

 

Hopefully following @binhex’s suggestion for modifying the dns settings will correct your issue. If not, post back.

Nope, updated the NS list, re-enabled VPN... broken. No access. :(

Link to comment
27 minutes ago, Elmojo said:

No access

I think the next step would be connecting to a different server. I’m not a Mullvad user but the safest process to do this would be to download a new ovpn file from Mullvad for a different port forwarding server. Replace the current ovpn file in the appdata folder with the new one. Restart the docker.

 

You may need to contact Mullvad customer service to get a new ovpn file unless you know the proper download site for them.

 

Perhaps @binhex might have other suggestions.

  • Upvote 1
Link to comment
1 hour ago, Elmojo said:

Ok, I changed to those you listed. Where should I have gotten the new list from, out of curiosity?

either by re-creating the the container from scratch, this will pickup all changes from the template (obviously not ideal), or viewing the github readme linked in the first post of this thread.

  • Like 1
Link to comment
1 minute ago, Elmojo said:

Creating and uploading new ovpn certs seemed to fix it.

No idea why. Anyway, thanks!!

If you check the log you may see you’re connecting to a new server. I know PIA occasionally has servers go down and I have to switch.

  • Like 1
Link to comment
1 minute ago, binhex said:

simple, the cert and/or openvpn config file is out of date, your vpn provider has changed something and the old config/cert file is no longer valid, it happens a lot.

That's good to learn. I didn't know that was a thing. It's the first time this has happened to me in over a year. I'll be on the lookout for it in the future. Thanks for the help!

Link to comment
On 9/22/2022 at 10:24 PM, sph031772 said:

My docker had been running good for months. I haven't changed anything in the docker settings since I initially set it up, but I did move my appdata folder to a new SATA SSD cache protected by RAID 1 from a stand alone NVME.   I noticed after I moved it the qbittorent Web UI login took longer to prompt, a few seconds.   Now it just simply stopped working a few weeks later.  When I disable VPN it works though.   CA backups has been backing up QBIT and I also noticed that the folder permission state owner nobody (not sure if that changed at one point).   Im using Nordvpn as my VPN, I tried replacing the sever file with a new one, but no luck.

 

All of my ARR dockers use a separate bridge network I created called dockerrnet 172.18.0.0/16 

I tried switching to br0 and changing the LAN Network settings, nothing has worked.

 

I see static routes but I'm not sure what the gateways are.

 

Route: 172.17.0.0/16

Geteway: docker01

Route: 172.18.0.0/16

Gateway: br-31fc6dcb88df1

 

I get the following error when I start the Docker with VPN enabled.

 

472 DEBG 'start-script' stdout output:
TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
TLS Error: TLS handshake failed

DEBG 'start-script' stdout output:
SIGHUP[soft,tls-error] received, process restarting

 

I'm running Tag 4.4.5-1-01.

 

Any help would be much appreciated.

 

image.png.75bd6499c59e57096e9a1ed2157cbaea.png

supervisord.log_1.txt 84.37 kB · 0 downloads

Turns out this was nordVPN causing the problem for me! - Download a new openvpn file from your preferred server (UDP) and replace your current one if you haven't tried it, fixed this failed/handshake error!

Edited by kazul
Link to comment

 

@binhex I think there may be a problem with version 4.4.5-2-01.

 

I have been using this docker container for over a year with no issues. I updated the container last night  and  I couldn't upload or download anything after the update. The connection status icon at the bottom was showing there was a problem. I tried changing servers with my vpn multiple times but that didn't help. This morning it still wasn't working. I rolled back to 4.4.5-1-01 and everything went back to working normally.

 

  • Like 1
Link to comment

Also having the same issue since updating last night. I see the following in the logs:

2022-11-05 10:02:29,104 DEBG 'start-script' stderr output:
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

2022-11-05 10:02:29,107 DEBG 'start-script' stderr output:
/usr/sbin/wg-quick: line 338: echo: write error: Broken pipe

 

Edited by jfs9112
clarification
  • Like 1
Link to comment

@binhex

 

The latest docker version is giving me these error(s) and I can not access the UI

 

Downgrading to 4.4.5-1-01 resolves the error(s)

[info] Script started to assign incoming port


2022-11-05 10:26:53,200 DEBG 'start-script' stdout output:

[info] Port forwarding is enabled

[info] Checking endpoint 'CENSORED.privacy.network' is port forward enabled...


2022-11-05 10:26:53,204 DEBG 'start-script' stdout output:

[warn] PIA VPN info API currently down, skipping endpoint port forward check


2022-11-05 10:26:53,205 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,209 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,213 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,243 DEBG 'start-script' stdout output:

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

[info] 12 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:04,273 DEBG 'start-script' stdout output:

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

[info] 11 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:14,302 DEBG 'start-script' stdout output:

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

[info] 10 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:23,200 DEBG 'start-script' stdout output:

[info] Sending 'down' command to WireGuard due to dns failure...


2022-11-05 10:27:23,201 DEBG 'start-script' stdout output:

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


2022-11-05 10:27:23,207 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,210 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0


2022-11-05 10:27:23,275 DEBG 'start-script' stderr output:

[#] '/root/wireguarddown.sh'


2022-11-05 10:27:23,278 DEBG 'start-script' stderr output:

/root/getvpnport.sh: line 1: kill: (1299) - No such process


2022-11-05 10:27:23,278 DEBG 'start-script' stdout output:

[info] WireGuard interface 'down'


2022-11-05 10:27:23,281 DEBG 'start-script' stdout output:

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


2022-11-05 10:27:23,287 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,291 DEBG 'start-script' stderr output:

[#] ip link add wg0 type wireguard


2022-11-05 10:27:23,292 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,294 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.25.200.63 dev wg0


2022-11-05 10:27:23,298 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0


2022-11-05 10:27:23,299 DEBG 'start-script' stderr output:

sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory


2022-11-05 10:27:23,300 DEBG 'start-script' stderr output:

/usr/sbin/wg-quick: line 338: echo: write error: Broken pipe


2022-11-05 10:27:23,300 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'


2022-11-05 10:27:23,303 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:27:24,307 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:27:24,311 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E

 

Im using the latest unraid OS (6.11.1) and PIA WG if thats relevant

Edited by ISwearItIsNotMe
Clarity & proper formatting & Didnt realize 6.11.2 got released)
  • Like 1
Link to comment
50 minutes ago, exactopposite said:

 

@binhex I think there may be a problem with version 4.4.5-2-01.

 

I have been using this docker container for over a year with no issues. I updated the container last night  and  I couldn't upload or download anything after the update. The connection status icon at the bottom was showing there was a problem. I tried changing servers with my vpn multiple times but that didn't help. This morning it still wasn't working. I rolled back to 4.4.5-1-01 and everything went back to working normally.

 

Agreed. A rollback fixed the problem for me as well.

 

thanks for the hard work Binhex, we appreciate it.

  • Like 1
Link to comment

I just rolled back to 4.4.5-1-01, what is going on here? If Qbittorrent runs for more than 5-10mins, its using up all my RAM and CPU? I updated to Unraid 6.11.1 (just did 6.11.2 now) today too, is it trying to download my files to RAM now???

 

image.thumb.png.35ddafcc6f8f3f1bf06c49a257c2231a.png

 

image.png.3beabcfad191a2eeb2f9c5f00fe2c69f.png

Edited by Linguafoeda
Link to comment
9 hours ago, ISwearItIsNotMe said:

@binhex

 

The latest docker version is giving me these error(s) and I can not access the UI

 

Downgrading to 4.4.5-1-01 resolves the error(s)

[info] Script started to assign incoming port


2022-11-05 10:26:53,200 DEBG 'start-script' stdout output:

[info] Port forwarding is enabled

[info] Checking endpoint 'CENSORED.privacy.network' is port forward enabled...


2022-11-05 10:26:53,204 DEBG 'start-script' stdout output:

[warn] PIA VPN info API currently down, skipping endpoint port forward check


2022-11-05 10:26:53,205 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,209 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,213 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:26:54,243 DEBG 'start-script' stdout output:

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

[info] 12 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:04,273 DEBG 'start-script' stdout output:

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

[info] 11 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:14,302 DEBG 'start-script' stdout output:

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

[info] 10 retries left

[info] Retrying in 10 secs...


2022-11-05 10:27:23,200 DEBG 'start-script' stdout output:

[info] Sending 'down' command to WireGuard due to dns failure...


2022-11-05 10:27:23,201 DEBG 'start-script' stdout output:

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


2022-11-05 10:27:23,207 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,210 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0


2022-11-05 10:27:23,275 DEBG 'start-script' stderr output:

[#] '/root/wireguarddown.sh'


2022-11-05 10:27:23,278 DEBG 'start-script' stderr output:

/root/getvpnport.sh: line 1: kill: (1299) - No such process


2022-11-05 10:27:23,278 DEBG 'start-script' stdout output:

[info] WireGuard interface 'down'


2022-11-05 10:27:23,281 DEBG 'start-script' stdout output:

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


2022-11-05 10:27:23,287 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,291 DEBG 'start-script' stderr output:

[#] ip link add wg0 type wireguard


2022-11-05 10:27:23,292 DEBG 'start-script' stderr output:

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


2022-11-05 10:27:23,294 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.25.200.63 dev wg0


2022-11-05 10:27:23,298 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0


2022-11-05 10:27:23,299 DEBG 'start-script' stderr output:

sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory


2022-11-05 10:27:23,300 DEBG 'start-script' stderr output:

/usr/sbin/wg-quick: line 338: echo: write error: Broken pipe


2022-11-05 10:27:23,300 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'


2022-11-05 10:27:23,303 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:27:24,307 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E


2022-11-05 10:27:24,311 DEBG 'start-script' stderr output:

egrep: warning: egrep is obsolescent; using grep -E

 

Im using the latest unraid OS and PIA WG if thats relevant

@binhex similar problem here using mullvad and 4.4.5-2-01. resolve by using 4.4.5-1-01 instead.

  • Like 1
Link to comment
6 hours ago, Linguafoeda said:

I just rolled back to 4.4.5-1-01, what is going on here? If Qbittorrent runs for more than 5-10mins, its using up all my RAM and CPU? I updated to Unraid 6.11.1 (just did 6.11.2 now) today too, is it trying to download my files to RAM now???

 

 

image.png.3beabcfad191a2eeb2f9c5f00fe2c69f.png

 

What are you using to get those graphs for the CPU and RAM usage of the container?

Link to comment
 
Same issue here and downgrading to 4.4.5-1-01 got me working again. 
 
Hi.
Got same error as ISwearItIsNotMe using WG.
 
Downgraded back to 4.4.5-1-01 , works now
 
@binhex similar problem here using mullvad and 4.4.5-2-01. resolve by using 4.4.5-1-01 instead.
arghh you guys got me out of my weekend slumber! :-).

ok it looks like arch linux in their wisdom ripped out crypto support which wireguard relies on, here is a post about it and the suggested fix, which ive now tested and confirmed working:-
 
https://unix.stackexchange.com/questions/723616/how-to-fix-missing-libcrypto-so-1-1
 
fix is now in, please pull down the image at your next convenience, now where's my coffee cup?

  • Thanks 2
  • Upvote 1
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.