I recently noticed that no torrents were appearing at all in the Web UI (all categories had a count of 0) and the bottom bar that normally shows upload and download speeds etc. was blank other than a few icons like up and down arrows.

 

 

I'm on unRAID 6.11.5. Recently I ran "Docker Safe New Perms" to fix some issue in another docker, if that's relevant.

 

supervisord.log

Hi, I've recently had to reinstall my binhex-qbittorentvpn due to update issues following swapping out a dead USB, I am hitting an issue where I cannot access the webUI. I have tried the steps I used perviously and I cannot seem to get this to work again, can anyone shed any light on this that would help me fix it please?

 

LOGS:

Spoiler

text  error  warn  system  array  login  

2023-06-28 23:23:53,767 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 SIGTERM[soft,auth-failure] received, process exiting

2023-06-28 23:23:53,769 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-06-28 23:23:53,775 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.
2023-06-28 23:23:53 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2023-06-28 23:23:53,776 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 WARNING: file 'credentials.conf' is group or others accessible
2023-06-28 23:23:53 OpenVPN 2.6.5 [git:makepkg/cbc9e0ce412e7b42+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 13 2023
2023-06-28 23:23:53 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10
2023-06-28 23:23:53 DCO version: N/A

2023-06-28 23:23:53,776 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2023-06-28 23:23:53 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-06-28 23:23:53,776 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 TCP/UDP: Preserving recently used remote address: [AF_INET]178.239.164.193:1194

2023-06-28 23:23:53,776 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 Socket Buffers: R=[212992->212992] S=[212992->212992]
2023-06-28 23:23:53 UDPv4 link local: (not bound)
2023-06-28 23:23:53 UDPv4 link remote: [AF_INET]178.239.164.193:1194

2023-06-28 23:23:53,791 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 TLS: Initial packet from [AF_INET]178.239.164.193:1194, sid=c29300ea f131558a

2023-06-28 23:23:53,823 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2023-06-28 23:23:53,823 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8

2023-06-28 23:23:53,823 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 VERIFY KU OK
2023-06-28 23:23:53 Validating certificate extended key usage
2023-06-28 23:23:53 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-06-28 23:23:53 VERIFY EKU OK
2023-06-28 23:23:53 VERIFY X509NAME OK: CN=uk899.nordvpn.com
2023-06-28 23:23:53 VERIFY OK: depth=0, CN=uk899.nordvpn.com

2023-06-28 23:23:53,838 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2023-06-28 23:23:53 [uk899.nordvpn.com] Peer Connection Initiated with [AF_INET]178.239.164.193:1194

2023-06-28 23:23:53,838 DEBG 'start-script' stdout output:
2023-06-28 23:23:53 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2023-06-28 23:23:53 TLS: tls_multi_process: initial untrusted session promoted to trusted

2023-06-28 23:23:54,941 DEBG 'start-script' stdout output:
2023-06-28 23:23:54 SENT CONTROL [uk899.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2023-06-28 23:24:00,061 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 SENT CONTROL [uk899.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2023-06-28 23:24:00,076 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 AUTH: Received control message: AUTH_FAILED

2023-06-28 23:24:00,076 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 SIGTERM[soft,auth-failure] received, process exiting

2023-06-28 23:24:00,078 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-06-28 23:24:00,084 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.
2023-06-28 23:24:00 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2023-06-28 23:24:00,084 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 WARNING: file 'credentials.conf' is group or others accessible
2023-06-28 23:24:00 OpenVPN 2.6.5 [git:makepkg/cbc9e0ce412e7b42+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 13 2023
2023-06-28 23:24:00 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10
2023-06-28 23:24:00 DCO version: N/A

2023-06-28 23:24:00,084 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2023-06-28 23:24:00 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-06-28 23:24:00,085 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 TCP/UDP: Preserving recently used remote address: [AF_INET]104.17.107.63:1194

2023-06-28 23:24:00,085 DEBG 'start-script' stdout output:
2023-06-28 23:24:00 Socket Buffers: R=[212992->212992] S=[212992->212992]
2023-06-28 23:24:00 UDPv4 link local: (not bound)
2023-06-28 23:24:00 UDPv4 link remote: [AF_INET]104.17.107.63:1194

 

Screenshots:

 

 

 

Edited June 28, 20233 yr by ArxKnight

10 hours ago, urbanracer34 said:

Hello,

 

I was wondering how I can modify the port the Qbittorrent instance uses for connecting to other peers. I am listed as unconnectable.

 

I'm currently using port 15276.  I port forwarded on my router but the connection is refused. 

 

Thanks!

 

  GIBSON_UpdateContainer2.pdf 143.41 kB · 3 downloads

 

 

I fixed this by manually assigning my ports on my docker. I hope that's it

Edited June 29, 20233 yr by urbanracer34

On 6/26/2023 at 3:48 PM, urbanracer34 said:

 

@eske Thanks for the advice. I am a horrible coder so I really can't use scripts in my environment. 

 

Would just adding the original torrents from rutorrent's session folder, and not the "libtorrent_resume or "rutorrent" ones, to an new instance of an torrent client suffice? 

 

EDIT1: I have all 641 current torrent files ready to go to a new client.

If the files are all saved in the same download directory and without renaming, you could take all of the torrent files from the session directory and add them into qbittorrent pointing to the same download directory.  You could also right click any torrent or groups of torrents in rutorrent and press "get torrent". This will create and download a .zip file of all the torrents that you have selected, with all the .torrent files. I could not go this route since I had a lot of unique directories for many of the torrents.

Edited June 29, 20233 yr by eske

18 hours ago, thatsthefrickenlightning said:

 

 

 

Did any of you get this container working with ProtonVPN? I created a .conf file with no fancy stuff like the VPN accelerator or extra filtering and chose a server with P2P support, and enabled NAT-PMP. The tunnel will come up and the web UI is accessible, but I am not connectable yet.

 

After some more reading, I suspect port forwarding via NAT-PMP is not supported on this container at the moment. @binhexcan you comment on this? Many thanks.

I changed my docker network to use a dedicated port on my server and now I can't get to the webgui of qbittorrentvpn.

 

Here's what I did: https://forums.unraid.net/topic/137048-guide-how-to-solve-macvlan-and-ipvlan-issues-with-containers-on-a-custom-network/

 

The container now has an IP on the host's network. I can ping it, but it doesnt bring up the gui nor can the other arr's access it. If I put it back to bridge, it works fine.

When on bridge, it got an ip of 172.17.0.2. When on the br1 bridge, it gets an IP of 192.168.0.10.

 

Hi all,

 

Have a little problem after a failed parity disk replacement.

Some of my docker containers were still running, and I have 4 binhex-qbitvpn containers.

Some of the torrents inside the containers were fully downloaded, and now not anymore cause of a partly failed rebuild.

Nothing problementary at all, so I want to download them again to 100%.

They are still in the clients, but some of the torrents continue after automatically being reset to 0.0 percent due to missing files.

 

But now comes the problem, some of the torrents are in the 0.0 percent state with as status Errored.
The log files said, no space left on device.

But, there is still over 6 TB left on the array, before there wasn't, now there is.

 

I've already tried to recheck those, but they recheck and say, even with 0.0% and space left, still Errored and I get also continuous get errors in my log files that say no space left.

 

What can I do, other that removing them and add them again, as I don't have the torrent files on my pc (maybe on the server/docker folder somewhere), to get them started again to download the full torrent again, as they should after getting them at 0 percent?

 

Thanks in advance, and thanks for reading this whole "tale".

-Rikdegraaff

14 hours ago, eske said:

If the files are all saved in the same download directory and without renaming, you could take all of the torrent files from the session directory and add them into qbittorrent pointing to the same download directory.  

This is exactly what I did. All checked OK but I'm not getting the speeds I usually got with rutorrent. 

Docker UI not loading with VPN enabled all of a sudden.  Been using this for a while and now it stopped.  I can still use it without VPN.  My VPN credentials are working and I've tried several ovpn config files both TCP and UDP.  VPN provider is NORD.

supervisord_20230629_debug.log

I am seeing the same issue as mdr6273, Also using NORD and I have verified that the user and the password in the credentials.conf are correct. Running on 6.11.5

I thinking the issue revolves around

2023-06-29 22:04:12 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

 

...

2023-06-29 22:04:12,020 DEBG 'start-script' stdout output:
2023-06-29 22:04:12 AUTH: Received control message: AUTH_FAILED

Edited June 30, 20233 yr by Matthew_K

12 hours ago, nraygun said:

I changed my docker network to use a dedicated port on my server and now I can't get to the webgui of qbittorrentvpn.

 

Here's what I did: https://forums.unraid.net/topic/137048-guide-how-to-solve-macvlan-and-ipvlan-issues-with-containers-on-a-custom-network/

 

The container now has an IP on the host's network. I can ping it, but it doesnt bring up the gui nor can the other arr's access it. If I put it back to bridge, it works fine.

When on bridge, it got an ip of 172.17.0.2. When on the br1 bridge, it gets an IP of 192.168.0.10.

 

I got it! But it's weird.

I had to change the webgui port to 8585 in the container settings and in the app itself. unRaid's port mapping still shows 8080, but it's actually 8585. I also found that some of the arr's cant resolve hostnames even though they are on the same custom network. So I put static IPs for everything.

6 hours ago, mdr6273 said:

Docker UI not loading with VPN enabled all of a sudden.  Been using this for a while and now it stopped.  I can still use it without VPN.  My VPN credentials are working and I've tried several ovpn config files both TCP and UDP.  VPN provider is NORD.

supervisord_20230629_debug.log 354.42 kB · 1 download

Switching over to the NORD Service credentials fixed this for me.

 

Apparently this email went out:

 

Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead.

 

You can find your service credentials by following these steps:

Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/

Click on the NordVPN tab on the left panel which is under the Services tab.

Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually:

Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder.

Copy your service credentials by using the buttons on the right.

Hello, I I have an error where the docker container won't fully start. It keeps repeatedly trying to connect to OpenVPN servers. I looked in the logs and I keep seeing this error:
 

6:35,430 DEBG 'start-script' stdout output:
2023-06-30 14:46:35 AUTH: Received control message: AUTH_FAILED

 

Any help would be great thanks!

 

Edit: Issue fixed

Edited June 30, 20233 yr by corfoto4

On 6/29/2023 at 11:24 AM, thatsthefrickenlightning said:

 

After some more reading, I suspect port forwarding via NAT-PMP is not supported on this container at the moment. @binhexcan you comment on this? Many thanks.

 

Sorry to harp on about this. Further tinkering has revealed to me that NAT-PMP changes up the forwarded port on each connection. The Proton VPN client for Windows will tell you the port, as will the Wireguard client for Windows. I cannot however find the forwarded port in the log files for this container. So how do I know which port to manually enter in the WebUI settings?

 

Aside from this, would it be possible to have the container automatically change the listening port based on what Proton's NAT-PMP system reports as the currently forwarded port? Otherwise we'll all be manually updating that port every time there's a reconnection, which in my case would be daily, as it goes down for an AppData backup.

 

Hope I'm on the right track with this.

1 hour ago, thatsthefrickenlightning said:

would it be possible to have the container automatically change the listening port based on what Proton's NAT-PMP system reports as the currently forwarded port?

yes, but its a fair chunk of work to add in support, i will have a think about it, dont expect anything soon (within the next week).

7 minutes ago, binhex said:

yes, but its a fair chunk of work to add in support, i will have a think about it, dont expect anything soon (within the next week).

Any and all work is appreciated. I believe I donated to you in the past but I'll have to do so again given how much I use your software.

 

In the meantime, can you clue me in as to how to discover the NAT-PMP forwarded port for manual entry?

 

E: I suspect with the excellent Mullvad sunsetting port forwarding support, this question will be asked more than once.

Edited June 30, 20233 yr by thatsthefrickenlightning

1 hour ago, thatsthefrickenlightning said:

Any and all work is appreciated. I believe I donated to you in the past but I'll have to do so again given how much I use your software.

 

In the meantime, can you clue me in as to how to discover the NAT-PMP forwarded port for manual entry?

 

E: I suspect with the excellent Mullvad sunsetting port forwarding support, this question will be asked more than once.

I do appreciate any and all donations, thank you :-), sadly my time is limited so i have to squeeze things in when i can. 

As for manually getting it working you can try the following:-

 

step 1. install natpmp by getting to the 'console' of the container then typing `pacman -S libnatpmp` confirm install, then issue the command `natpmpc` to ensure its installed.
 

step 2. follow the section 'how to use port forwarding/manual configuration' from this webpage:- https://protonvpn.com/support/port-forwarding-manual-setup/
 

Hello again.

 

i´ve setup my qbittorrent docker, with shared vpn to sabnzbd and prowlarr.. The problem is that when i try to locate the sabnzbd. download client it can´t find any other that qbittorrent..

i´ve tried with localhost, and with my ip-address.. But no luck.

Anyone ideas??

 

Regards

10 hours ago, Megalodon170 said:

Switching over to the NORD Service credentials fixed this for me.

 

Apparently this email went out:

 

Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead.

 

You can find your service credentials by following these steps:

Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/

Click on the NordVPN tab on the left panel which is under the Services tab.

Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually:

Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder.

Copy your service credentials by using the buttons on the right.

Worked like a charm, thank you!!

Can someone help explain what's going on here?

My container on a dedicated bridge on eth1 shows these mappings. Note 8080.

 

 

6881 and 8118 look fine to me and make sense.

 

In the config, there is no 8080. It shows this:

Shouldn't the port mappings show 8081 or 8585? Why is 8080 shown in port mapping? Where is it getting 8081 from?

 

1 hour ago, nraygun said:

Can someone help explain what's going on here?

Just a guess but perhaps a typo when you set the port? You don’t show what you have set for the WEBUI_PORT variable but if you want it to be 8080 then Host Port 3 would be 8080:8080.

1 hour ago, nraygun said:

My container on a dedicated bridge on eth1

IIRC network type bridge is recommended.

22 hours ago, binhex said:

I do appreciate any and all donations, thank you :-), sadly my time is limited so i have to squeeze things in when i can. 

As for manually getting it working you can try the following:-

 

step 1. install natpmp by getting to the 'console' of the container then typing `pacman -S libnatpmp` confirm install, then issue the command `natpmpc` to ensure its installed.
 

step 2. follow the section 'how to use port forwarding/manual configuration' from this webpage:- https://protonvpn.com/support/port-forwarding-manual-setup/
 

 

This is what I get when I enter 'natpmpc' after installing it in the container's console. QB is working fine at this point, just not connectable.

 

initnatpmp() returned (SUCCESS)
using gateway: 172.17.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)
readnatpmpresponseorretry() failed: the gateway does not support nat-pmp
errno-111 'Connection refused'

 

But we may not need to get into that all the way. There's another container (Gluetun) that just added support for Proton VPN port forwarding (which I suspect just means it supports NAT-PMP port forwarding). A few thoughts on this:

• Seeing as Gluetun works with an MIT license, could this situation be as simple as just copying Gluetun's work with some changes to fit your container?
• Or, as a stop-gap fix, I can point the QBVPN container to Gluetun for its network access. I'm no expert, but I've always felt reassured by your iptables approach to prevent leaks. Does Gluetun sound like it has similar reliability? They say the following about this feature:

Quote

Built in firewall kill switch to allow traffic only with needed the VPN servers and LAN devices

 

I'm no big fish but I do like my privacy.

 

Many thanks.

Edited July 1, 20233 yr by thatsthefrickenlightning

19 hours ago, wgstarks said:

Just a guess but perhaps a typo when you set the port? You don’t show what you have set for the WEBUI_PORT variable but if you want it to be 8080 then Host Port 3 would be 8080:8080.

Here's my WebGUI value. I get this same behavior with DelugeVPN.

It seems like it's stuck on having things route through privoxy for the webgui port until I change it to something else in the app.

And I noticed I can change the container port by going to "bridge" mode, saving, then going back to "br1". Then I have to change the gui port in qbittorrent. For example, the container port is now 8585 instead of 8081 and it still works.

 

Maybe there's a problem when switching network types?

 

Edited July 1, 20233 yr by nraygun

9 hours ago, thatsthefrickenlightning said:

This is what I get when I enter 'natpmpc' after installing it in the container's console. QB is working fine at this point, just not connectable.

 

initnatpmp() returned (SUCCESS)
using gateway: 172.17.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)
readnatpmpresponseorretry() failed: the gateway does not support nat-pmp
errno-111 'Connection refused'

are you connecting to a protonvpn endpoint that supports port forwarding?, note the section in the webpage i linked to describing this exact error.

 

9 hours ago, thatsthefrickenlightning said:

Seeing as Gluetun works with an MIT license, could this situation be as simple as just copying Gluetun's work with some changes to fit your container?

that would be a nasty cludge that i wouldnt be happy to entertain, sorry, you would be better off simply using deluge (no vpn) and routing it through gluetun in the way its supposed to be used.

 

9 hours ago, thatsthefrickenlightning said:

I've always felt reassured by your iptables approach to prevent leaks. Does Gluetun sound like it has similar reliability? They say the following about this feature:

i honestly dont know how gluetun works in this regards, but the word 'killswitch' suggests to me that gluetun is reactive (kills connection when vpn goes down) as opposed to proactive (my images - protection is always on irrespective of state of vpn).