6 hours ago, binhex said:

ProtonVPN support is now in!, the image (just built - please pull down) will now automatically assign and set an incoming port for you in the application, support for both wireguard and openvpn is included, for instructions see Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Thanks a lot @binhex

Not much but I've bought you a few beers 

after update, can't get to web-gui?

 

after update, can't get to web-gui?

 

That screenshot shows nothing is wrong.

Sent from my 22021211RG using Tapatalk

On 6/28/2023 at 11:01 PM, sonofdbn said:

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 95.06 kB · 1 download

 

I should add that I'm using PIA and I think my qbittorrentvpn setup is very straightforward. So far still unable to get it going properly. (It's been working fine for ages.)

On 7/6/2023 at 3:56 PM, binhex said:

ProtonVPN support is now in!, the image (just built - please pull down) will now automatically assign and set an incoming port for you in the application, support for both wireguard and openvpn is included, for instructions see Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Binhex, that's absolutely great, thank you so much! I haven't had a chance to tinker with it more and the job just got a whole lot easier. I'll buy you some more beers in a bit.

 
Binhex, that's absolutely great, thank you so much! I haven't had a chance to tinker with it more and the job just got a whole lot easier. I'll buy you some more beers in a bit.

It was as I suspected fiddly and to prevent me coding blind I signed up for 1 month of proton VPN, I'm quite pleased with the result, it certainly worked well for me.

Sent from my 22021211RG using Tapatalk

2 minutes ago, binhex said:

It was as I suspected fiddly and to prevent me coding blind I signed up for 1 month of proton VPN, I'm quite pleased with the result, it certainly worked well for me.

Sent from my 22021211RG using Tapatalk
 

 

I wish you'd said something! I would have gladly provided you with configuration files for Proton VPN. Anyway, glad it's to your satisfaction, then I'm sure it will be to mine as well.

23 hours ago, sonofdbn said:

 

I should add that I'm using PIA and I think my qbittorrentvpn setup is very straightforward. So far still unable to get it going properly. (It's been working fine for ages.)

 

OK, my (big) mistake. I had set the version to 4.3.9-2-01; I think this was a while back as a workaround for some problem I had. Switched to latest version, and all OK now.

On 7/6/2023 at 3:56 PM, binhex said:

ProtonVPN support is now in!, the image (just built - please pull down) will now automatically assign and set an incoming port for you in the application, support for both wireguard and openvpn is included, for instructions see Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Thanks for the documentation. I successfully added ProtonVPN to the list of VPN Providers and enabled it. One thing that had me confused was appending '+pmp' to my VPN username in the container parameters. I'm on Wireguard so the wg0.conf file contains all the VPN login info needed, right? I wouldn't even know what to put there. My Proton username? The private key from the conf file? I ended up just entering +pmp and nothing else in that field and the system works.

 

Another snag I ran into is that the logs say my chosen server doesn't support port forwarding, but it did have the arrows icon. I generated another config file with a different server and it's now working, so that was probably a gaffe on Proton's end.

 

Thanks again!

 

EDIT: weird, after an initial connection and everything working fine, the tunnel seems to die and it says NAT-PMP is not supported. But before that, a port is established just fine, Privoxy works and the trackers report me as connectable. It starts with not being able to resolve google.com and then..

 

2023-07-09 DEBG •watchdog-script' stdout output:
Having issues resolving name
Retrying in 5 secs...
9 retries left
22:09:49, 141 DEBG •start-script' stderr output:
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
errno=11 'Resource temporarily unavailable '

 

I can upload a full supervisord.log if you want.

Edited July 9, 20233 yr by thatsthefrickenlightning

I went on Vacation 7th and came back on the 9th... noticed the container was dead when I got home. Checked the logs, and the vpn isn't validating. No biggie, I use NordVPN so I went to their site and grabbed a new openvpn profile. Still not working...hmmm okay try this 3 or so more times to no success. I left it for the night and trying to troubleshoot some more.

anyone else having these issues specifically with Nord VPN? I'm getting an AUTH_FAILED message:

 

2023-07-10 12:25:58,565 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-07-10 12:25:58,620 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 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-07-10 12:25:58 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2023-07-10 12:25:58,621 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 WARNING: file 'credentials.conf' is group or others accessible
2023-07-10 12:25:58 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-07-10 12:25:58 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10

2023-07-10 12:25:58,621 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 DCO version: N/A

2023-07-10 12:25:58,621 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2023-07-10 12:25:58 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-07-10 12:25:58,622 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 TCP/UDP: Preserving recently used remote address: [AF_INET]154.47.17.25:1194

2023-07-10 12:25:58,622 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 Socket Buffers: R=[212992->212992] S=[212992->212992]
2023-07-10 12:25:58 UDPv4 link local: (not bound)
2023-07-10 12:25:58 UDPv4 link remote: [AF_INET]154.47.17.25:1194

2023-07-10 12:25:58,699 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 TLS: Initial packet from [AF_INET]154.47.17.25:1194, sid=7e8fc475 43b39994

2023-07-10 12:25:58,857 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2023-07-10 12:25:58,857 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8

2023-07-10 12:25:58,858 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 VERIFY KU OK
2023-07-10 12:25:58 Validating certificate extended key usage
2023-07-10 12:25:58 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-07-10 12:25:58 VERIFY EKU OK
2023-07-10 12:25:58 VERIFY X509NAME OK: CN=ca1701.nordvpn.com
2023-07-10 12:25:58 VERIFY OK: depth=0, CN=ca1701.nordvpn.com

2023-07-10 12:25:58,935 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2023-07-10 12:25:58 [ca1701.nordvpn.com] Peer Connection Initiated with [AF_INET]154.47.17.25:1194

2023-07-10 12:25:58,935 DEBG 'start-script' stdout output:
2023-07-10 12:25:58 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2023-07-10 12:25:58 TLS: tls_multi_process: initial untrusted session promoted to trusted

2023-07-10 12:25:59,947 DEBG 'start-script' stdout output:
2023-07-10 12:25:59 SENT CONTROL [ca1701.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2023-07-10 12:26:04,040 DEBG 'start-script' stdout output:
2023-07-10 12:26:04 SENT CONTROL [ca1701.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2023-07-10 12:26:04,116 DEBG 'start-script' stdout output:
2023-07-10 12:26:04 AUTH: Received control message: AUTH_FAILED

2023-07-10 12:26:04,116 DEBG 'start-script' stdout output:
2023-07-10 12:26:04 SIGTERM[soft,auth-failure] received, process exiting

I assume this is on Nords end? but surely it's not just me having this issue then?

I've reset my password as well just in case, something much shorter than the original (but working) 30 char pass. I should note I can access the profiles via the Nord App no problem.

15 minutes ago, Rockstar said:

2023-07-10 12:25:58 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305).

This is likely your problem. You just need to get an up-to-date certificate.

44 minutes ago, wgstarks said:

This is likely your problem. You just need to get an up-to-date certificate.

What cert is this pulling from? the OpenVPN profile?

1 hour ago, Rockstar said:

[ca1701.nordvpn.com]:

 

1 hour ago, Rockstar said:

AUTH: Received control message: AUTH_FAILED

nordvpn user with auth failed, this is well known, nordvpn changed their authentication mechanism you need to get the new credentials.

 

edit - follow this guys post:- https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1278020

 

1 hour ago, binhex said:

 

nordvpn user with auth failed, this is well known, nordvpn changed their authentication mechanism you need to get the new credentials.

 

edit - follow this guys post:- https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1278020

 

Excellent this worked! Thank you very much for the quick link. Back up and running again!

Anybody using binhex/arch-qbittorrentvpn:libtorrentv1 with binhex/arch-radarr?

 

I've been using binhex/arch-qbittorrentvpn:4.3.9-2-01 because of earlier issues with binhex/arch-radarr

 

On 7/9/2023 at 9:58 PM, thatsthefrickenlightning said:

 

Thanks for the documentation. I successfully added ProtonVPN to the list of VPN Providers and enabled it. One thing that had me confused was appending '+pmp' to my VPN username in the container parameters. I'm on Wireguard so the wg0.conf file contains all the VPN login info needed, right? I wouldn't even know what to put there. My Proton username? The private key from the conf file? I ended up just entering +pmp and nothing else in that field and the system works.

 

Another snag I ran into is that the logs say my chosen server doesn't support port forwarding, but it did have the arrows icon. I generated another config file with a different server and it's now working, so that was probably a gaffe on Proton's end.

 

Thanks again!

 

EDIT: weird, after an initial connection and everything working fine, the tunnel seems to die and it says NAT-PMP is not supported. But before that, a port is established just fine, Privoxy works and the trackers report me as connectable. It starts with not being able to resolve google.com and then..

 

2023-07-09 DEBG •watchdog-script' stdout output:
Having issues resolving name
Retrying in 5 secs...
9 retries left
22:09:49, 141 DEBG •start-script' stderr output:
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
errno=11 'Resource temporarily unavailable '

 

I can upload a full supervisord.log if you want.

Working fine for now. Guess the unavailable service errors are just that: Proton's server being overloaded.

6 minutes ago, thatsthefrickenlightning said:

EDIT: weird, after an initial connection and everything working fine, the tunnel seems to die and it says NAT-PMP is not supported. But before that, a port is established just fine, Privoxy works and the trackers report me as connectable. It starts with not being able to resolve google.com and then..

if you get dns failure then the vpn tunnel is down (dns blocked on lan), once the tunnel is down natpmp will also fail as it requires a working vpn tunnel to get assigned an incoming port. so the question is, why is the tunnel going down, well there are a number of possibilities, as you mentioned it could be protonvpn getting overloaded, try and choose an endpoint with low utilisation (noticed protonvpn show this in their endpoint selection webpage).

 

one other thing to mention is that i have code in place to recover from a vpn connectivity failure, so you should see an attempt to re-establish the vpn tunnel and subsequent natpmp calls to get a new incoming port, have you tried simply leaving the container running to see if it recovers?.

On 4/29/2022 at 11:13 PM, Skikibobski said:

Everytime I restart my container all my active downloads reset to 0% and my completed downloads give "Missing files" message.

I've confirmed the files are present in the host location, but the container location is empty.
Force recheck doesn't help.

 

I have temp downloads folder enabled, so my finished downloads/default save location goes to /data/Downloads/Complete and my incomplete downloads goes to /data/Downloads/Incomplete.

 

I'm still new to Unraid so I might be missing something.

I did just add a cache drive, and the mover moved my appdata folder to it, unsure if that might be related though.
Any help appreciated!

Hi!
I just started up this docker after not having a VPN for ages. I've read that Qbittorrent changed path after an update. I've tried to change it back to the path I've had before, but everything I've tried it just start the download on the default path on the cache drive. Is there something I'm doing wrong?

1 hour ago, ostron2 said:

Hi!
I just started up this docker after not having a VPN for ages. I've read that Qbittorrent changed path after an update. I've tried to change it back to the path I've had before, but everything I've tried it just start the download on the default path on the cache drive. Is there something I'm doing wrong?

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

 

Try the solution in Q2.

2 hours ago, wgstarks said:

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

 

Try the solution in Q2.

Thank you for your reply. There is no tiny file icon to the right what I can see. Is this the fix for saving default path?

1 hour ago, ostron2 said:

Thank you for your reply. There is no tiny file icon to the right what I can see. Is this the fix for saving default path?

I’m not sure what you mean by a file icon. It’s just a text field where you type in the save path.

 

 

Just now, wgstarks said:

I’m not sure what you mean by a file icon. It’s just a text field where you type in the save path.

 

 

Type in PART of the path for your watched folder, for instance if you want your monitored folder to be /data/qbittorrent/watched, then enter in /data then click on the tiny file icon to the right of the 'Override Save Location' field, then click on 'Save' at the bottom of the window.

Am I just misunderstanding the instructions maybe?

I see. Pretty sure there isn’t a file icon. Try just clicking save after entering each segment of the path until you have entered  the full path.

18 hours ago, wgstarks said:

I see. Pretty sure there isn’t a file icon. Try just clicking save after entering each segment of the path until you have entered  the full path.

Just realized I'm dumb. I changed download path but not the temp path. When I changed that everything worked. Sorry, but thank you for taking your time

1 hour ago, ostron2 said:

Just realized I'm dumb. I changed download path but not the temp path. When I changed that everything worked. Sorry, but thank you for taking your time

Happens to me all the time.😂