How come "latest stable" is giving me 2.0.4dev38? One of my trackers have banned it as they don't allow dev-versions.

3 hours ago, Kishin said:

Hello, does anyone has a script to move files between disks ?

I would like to download to my cache then move them to the array where i can continue to seed / hardlink for plex.

 

Thanks.

In my setup I rely on the nightly mover to move my downloads from the cache to the array.  This occurs every day at 04:00.

 

4 hours ago, Kishin said:

Hello, does anyone has a script to move files between disks ?

I would like to download to my cache then move them to the array where i can continue to seed / hardlink for plex.

I download to a cache-only share, then allow deluge to move the files to another share, automatically, on download completion.  No extra script needed.

 

Check out deluge 'Preferences' -> 'Downloads', "Move completed to:"

7 hours ago, binhex said:

Q22:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

excellent - thanks!
so in my config file i see:

cipher aes-128-cbc

but none of the other ones ... so do i just add
 

cipher aes-256-gcm

ncp-disable

or do i also remove "cipher aes-128-cbc"

14 minutes ago, helpermonkey said:

or do i also remove "cipher aes-128-cbc"

remove that line, you can only have one cipher line and that one is not correct.

[FIXED]

When I try to connect to Deluge from Sonnar, I receive the following error:  "Unknown exception: The operation has timed out.: 'http://10.69.55.110:8112/json'

 

I can login to deluge fine using the IP address (10.69.55.110:8112).   However the json file does not seem to exist.   This has been working for a while and I've used bin hex projects for a majority of my Unraid media server.    I'm unsure if this is something I've broken, but I've not made a change on my system in months.    

 

Turning off the VPN component of this container does allow other containers to connect, but that doesn't provide me what I need for reasons.

 

Any suggestions or advice?
[FIXED]
------

After a lot of goole foo, found another thread on reddit that described this issue and it was a firewall issue on a Synology nas.  Seemed my Mikrotik router considered looking up Json an invalid connection.  I excluded my local lan subnet and all is well now.  Not sure why this is... but I'll leave this here incase someone else runs across it. 

Edited November 6, 20205 yr by djgizmo

2 hours ago, binhex said:

remove that line, you can only have one cipher line and that one is not correct.

thank you for your help.  this helped me as well.

 

For reference for anyone else.  Deluge VPN would not start for me.  This is due to a recent PIA change on their end. 

 

Go to: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Look at question 19 and 22 and make the changes.

 

I can't seem to get around this error...

2020-11-06 12:26:17,597 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privacy.network' is port forward enabled...

2020-11-06 12:26:17,604 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2020-11-06 12:26:18,184 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2020-11-06 12:26:18,309 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'ca-toronto.privacy.network' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
[info] Please consider switching to one of the endpoints shown below

2020-11-06 12:26:18,311 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2020-11-06 12:26:18,312 DEBG 'start-script' stdout output:
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-11-06 12:26:18,346 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=a619b6295e9df7efdf53872765677526286e6f49586fb964d0d6989b4f2ebd6c...

2020-11-06 12:26:18,420 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 12 retries left
[info] Retrying in 10 secs...

I have been through the faq and have done the following:

Updated the container, downloaded the next gen files from PIA, changed my password to alphanumeric only, and tried multiple sites (Montreal, Toronto, Berlin, Frankfurt, Romania, France).

 

The only change that seems to help is to set STRICT_PORT_FORWARD to no. Is that a potential risk to do that or is it more for performance?

 

Could curl exit code 7 be related to name servers? Mine are set to:

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

 

I appreciate any advice, I'm nearing my wit's end.

4 hours ago, binhex said:

remove that line, you can only have one cipher line and that one is not correct.

Thanks - so i gave that a twirl and i'm still getting some errors ... here is the log file on pastebin

 

here is the .ovpn file minus the cert and the X509 portion....

client
dev tun
proto udp
remote ca-toronto.privacy.network 1198
resolv-retry infinite
nobind
persist-key
cipher aes-256-gcm
ncp-disable
auth sha1
tls-client
remote-cert-tls server

auth-user-pass credentials.conf
compress
verb 1
<crl-verify>

 

6 minutes ago, helpermonkey said:

Thanks - so i gave that a twirl and i'm still getting some errors ... here is the log file on pastebin

 

here is the .ovpn file minus the cert and the X509 portion....

client
dev tun
proto udp
remote ca-toronto.privacy.network 1198
resolv-retry infinite
nobind
persist-key
cipher aes-256-gcm
ncp-disable
auth sha1
tls-client
remote-cert-tls server

auth-user-pass credentials.conf
compress
verb 1
<crl-verify>

 

You're using the username/password generated for SOCKS connections.  Use the username and password you sign into the PIA website with. The generated u/p used to work before they switched to nextgen, now you have to use your actual u/p

1 hour ago, chesh said:

You're using the username/password generated for SOCKS connections.  Use the username and password you sign into the PIA website with. The generated u/p used to work before they switched to nextgen, now you have to use your actual u/p

so how would i do that? in my credentials.conf file - the first line is my userid for PIA and the second line is my password that i login to the website with.

16 minutes ago, helpermonkey said:

so how would i do that? in my credentials.conf file - the first line is my userid for PIA and the second line is my password that i login to the website with.

Change them in your container settings.

2 minutes ago, wgstarks said:

Change them in your container settings.

they are also in my container settings.... i just double checked and had no problem signing into the PIA website from my browser and all of my other clients are logging in without a problem.

2 hours ago, Malaki said:

appreciate any advice, I'm nearing my wit's end

Are you sure your running the latest version of the container? What do you have set for repository?

Does binhex/arch-delugevpn:2.0.3-2-01 support all this next gen, updated servers stuff?  My current experience would suggest no.  But maybe I'm just misconfigured somewhere.  Ive been through the FAQ up and down, though.

4 minutes ago, DontWorryScro said:

Does binhex/arch-delugevpn:2.0.3-2-01 support all this next gen, updated servers stuff?  My current experience would suggest no.  But maybe I'm just misconfigured somewhere.  Ive been through the FAQ up and down, though.

No. You will have to install one of the most recent 2.0.4 builds. Might as well just install the latest build.

55 minutes ago, wgstarks said:

No. You will have to install one of the most recent 2.0.4 builds. Might as well just install the latest build.

ok can anyone chime in on a specific 2.0.4 build that plays nice with the most amount of private trackers without getting you banned/blocked/timedout?

Give me your favorite tag!  TIA

 

Edit: tho i guess the real issue is they're all dev versions.  No stable version.  So I'm up a creek.

Edited November 7, 20205 yr by DontWorryScro

1 hour ago, DontWorryScro said:

Edit: tho i guess the real issue is they're all dev versions.  No stable version.  So I'm up a creek.

Edited 11 minutes ago by DontWorryScro

Binhex-qbittorrentvpn has worked great for me. The switch was fairly painless if you want to go that route. You will need to re-add all your torrents so you need to be sure you have the torrent files (and maybe backup copies 🤞).

 

Edit: you’re welcome to pm me if you need details.

Edited November 7, 20205 yr by wgstarks

2 hours ago, wgstarks said:

Are you sure your running the latest version of the container? What do you have set for repository?

I'm running 2.0.4.dev38_g23a48dd01-2-15. I'm using latest for the repo.

9 minutes ago, Malaki said:

I'm running 2.0.4.dev38_g23a48dd01-2-15. I'm using latest for the repo.

You could try the recommended NS's and see what happens-

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

 

Edited November 7, 20205 yr by wgstarks

21 minutes ago, wgstarks said:

Binhex-qbittorrentvpn has worked great for me. The switch was fairly painless if you want to go that route. You will need to re-add all your torrents so you need to be sure you have the torrent files (and maybe backup copies 🤞).

 

Edit: you’re welcome to pm me if you need details.

thank you for this.  i may need to go that route.  i dread the thought of having to recheck my 2100+ torrents all living in different folders with various labels.  but if thats what i gotta do....

1 minute ago, wgstarks said:

You could try the recommended NS's and see what happens-

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

 

Nevermind. I see that's what you already have set.

1 hour ago, DontWorryScro said:

ok can anyone chime in on a specific 2.0.4 build that plays nice with the most amount of private trackers without getting you banned/blocked/timedout?

Give me your favorite tag!  TIA

 

Edit: tho i guess the real issue is they're all dev versions.  No stable version.  So I'm up a creek.

Most trackers I'm on have a banned list that you cannot use, and an approved list that is supported/preferred, leaving a grey area for certain clients and/or versions of those clients.

I would do some research on your tracker's forums etc to see if there is a grey area that allows use of these version of deluge.

 

31 minutes ago, wgstarks said:

Nevermind. I see that's what you already have set.

I did double-check those. I tried the binhex/qbittorrent container just for fun. I set it up using the same info - VPN settings, name servers, etc. - it connected right up. Switching back to deluge, I got an auth failed message so I double-checked the password. It's now back to the same error...

warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0

 

I'm assuming that binhex is using the same openvpn client on both so I'll keep working with the deluge container. I'm sure it's a user error somewhere, I might just just from scratch with it. At least qbittorent works, so that might become my go-to system.

 

Thanks wgstarks, it was one of your other comments about qbittorrent that prompted me to try that.

9 hours ago, helpermonkey said:

they are also in my container settings.... i just double checked and had no problem signing into the PIA website from my browser and all of my other clients are logging in without a problem.

I had the same issue with Toronto. Switched to Vancouver. It’s working fine now for me.