8 hours ago, dukiethecorgi said:

PIA announces that the legacy servers will shut down at the end of October

 

Now that the next gen server support is in the latest, I guess it's time for me to update

RIP binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

Just now, tjb_altf4 said:

RIP binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

lol, served you well has it? 🙂

Binhex, I was a guinea pig running the :test version, have the changes for nextgen now made it into the standard code?  I don't recall seeing a call out saying it's good to change back...but I could be blind.

1 minute ago, kslaguardia said:

Binhex, I was a guinea pig running the :test version, have the changes for nextgen now made it into the standard code?  I don't recall seeing a call out saying it's good to change back...but I could be blind.

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=897581

 

15 minutes ago, binhex said:

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=897581

 

And I'm blind, thanks for confirming that binhex lol!  Thank you for your hard work getting all of us PIA users through this challenging time!

Apparently, I don't know how to force an update...can someone tell me the command for that?

Edited October 1, 20205 yr by Merijeek

1 hour ago, Merijeek said:

Apparently, I don't know how to force an update...can someone tell me the command for that?

Set “Advance view” in the top right corner of the docker page and you should see “force update” below the version info for the docker.

9 minutes ago, wgstarks said:

Set “Advance view” in the top right corner of the docker page and you should see “force update” below the version info for the docker.

Thanks. Looks like I'd already updated (at one point I did a remove/add) so I guess I'm on the newest. 

 

Now I'm getting this in a loop:

 

2020-10-01 10:07:20,844 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 154.21.20.59

2020-10-01 10:07:20,929 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200


2020-10-01 10:07:21,047 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'us-seattle.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-10-01 10:07:21,048 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[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

2020-10-01 10:07:21,085 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=ac9125af77316821ac9536c06a53908e9116eee011f230a55bf8f377c79b470c...

2020-10-01 10:07:24,294 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...

2020-10-01 10:07:41,509 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 11 retries left
[info] Retrying in 10 secs...

 

Thanks for the most recent update Binhex. I just updated to the latest release and I am happy to have port forwarding back from PIA's CA Toronto next-gen server! It was a rough few weeks there without it.

18 hours ago, Merijeek said:

Thanks. Looks like I'd already updated (at one point I did a remove/add) so I guess I'm on the newest. 

 

you aren't, that is the still the old image, click on force update as instructed.

I have a 1 gig fiber connection

I live in the USA

I used to run the old arch-qbittorrentvpn using PIA and selecting France as the PIA endpoint and i would easily get 100megabits per second or more which is fine for me before the "next gen" crap

 

I am trying Deluge now since it seems to have a lot more pulls than qbittorrent but i am only getting like 6-8 megabits per second and thats after trying to download a few Linux ISOs all at the same time to see my maximum using Mexico, France, 

 

Bahamas seem to get around 12 megabits per second for me

 

Deluge seems to connect fine when i am looking at the logs so thats not the problem

 

What is a recommended VPN to use since i think PIA is not any good any more

 

Thanks in advance and for all the hardwork Binhex

Edited October 2, 20205 yr by Cytomax

1 hour ago, Cytomax said:

I have a 1 gig fiber connection

I live in the USA

I used to run the old arch-qbittorrentvpn using PIA and selecting France as the PIA endpoint and i would easily get 100megabits per second or more which is fine for me before the "next gen" crap

 

I am trying Deluge now since it seems to have a lot more pulls than qbittorrent but i am only getting like 6-8 megabits per second and thats after trying to download a few Linux ISOs all at the same time to see my maximum using Mexico, France, 

 

Bahamas seem to get around 12 megabits per second for me

 

Deluge seems to connect fine when i am looking at the logs so thats not the problem

 

What is a recommended VPN to use since i think PIA is not any good any more

 

Thanks in advance and for all the hardwork Binhex

Just to confirm, are your speeds in megabits or megabytes. I just download an Ubuntu torrent at between 10-12 megabytes per second which is about 80-100 megabits per second. This is on a one gigabit connection using PIA connected to Canada. Deluge displays speeds in bytes (KiB/s-MiB/s) not bits. If 6-12 MiB/s is what your seeing displayed in the webUI that sounds right.

Edited October 2, 20205 yr by TrueImpulse

I switched from binhex-delugevpn to binhex-qbittorrentvpn and have been getting much better download speeds.  I went from 10 - 15 MBps to 30 - 40 MBps.

3 hours ago, binhex said:

you aren't, that is the still the old image, click on force update as instructed.

OK, well, in that case I did follow the force instructions. I'm showing: 1.3.15_18_ge050905b2-1-04. 

 

I run the force update and I see: 

 

 

...ending with:

 

 

...and then just the same loop:

 

020-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'ca-montreal.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-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com

2020-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[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

2020-10-02 09:44:07,870 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=490c17333dbc8f1811cf0120ce36b8f421d35b0a84a9159ee97a5f84ae137acf...

2020-10-02 09:44:07,974 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...

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

2020-10-02 09:44:29,245 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 10 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:00,444 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 9 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:10,551 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 8 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:40,666 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 7 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:50,775 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0

 

@Merijeek - edit your docker container and change your tag to latest instead of the 1.x branch.  Your on a pre 2.0 client

2 hours ago, Merijeek said:

OK, well, in that case I did follow the force instructions. I'm showing: 1.3.15_18_ge050905b2-1-04. 

 

I run the force update and I see: 

 

 

...ending with:

 

 

...and then just the same loop:

 

020-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'ca-montreal.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-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com

2020-10-02 09:44:07,841 DEBG 'start-script' stdout output:
[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

2020-10-02 09:44:07,870 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=490c17333dbc8f1811cf0120ce36b8f421d35b0a84a9159ee97a5f84ae137acf...

2020-10-02 09:44:07,974 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...

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

2020-10-02 09:44:29,245 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 10 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:00,444 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 9 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:10,551 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 8 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:40,666 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0
[info] 7 retries left
[info] Retrying in 10 secs...

2020-10-02 09:46:50,775 DEBG 'start-script' stdout output:
[warn] Response code 000 from curl != 2xx
[warn] Exit code 7 from curl != 0

 

By looking at your log you are showing the List of PIA Endpoints associated with the OLD open vpn config

Here is the new link for the "NEXTGEN" config

https://www.privateinternetaccess.com/openvpn/openvpn-nextgen.zip

I literally realized this 12 hours ago after bashing my head for a few hours on why qbittorrent wasnt working

 

nextgen has a lot more end points

Edited October 2, 20205 yr by Cytomax

2 hours ago, Merijeek said:

OK, well, in that case I did follow the force instructions. I'm showing: 1.3.15_18_ge050905b2-1-04. 

It looks to me as if you have set a tag for this docker in the repository field. Is it set to "latest". If it's set to 1.3.15_18_ge050905b2-1-04 then it won't install the latest update. You'll need to change the version to latest and install the current version on Deluge v2.

2 hours ago, sigfreund said:

I switched from binhex-delugevpn to binhex-qbittorrentvpn and have been getting much better download speeds.  I went from 10 - 15 MBps to 30 - 40 MBps.

i used to use qbittorrent all the time but i stopped torrenting for like a month and then when i came back it didnt work when i tried after the nextgen switch so i went to deluge, i realized i was using the old openvpnconfig and i am going to retry qbittorrent with the new nextgen opnenvpn config

https://www.privateinternetaccess.com/openvpn/openvpn-nextgen.zip

 

the biggest thing i miss about qbittorrent is total traffic summary as well as total download and total upload.. i cant find a way to enable it on deluge

 

 

4 hours ago, TrueImpulse said:

Just to confirm, are your speeds in megabits or megabytes. I just download an Ubuntu torrent at between 10-12 megabytes per second which is about 80-100 megabits per second. This is on a one gigabit connection using PIA connected to Canada. Deluge displays speeds in bytes (KiB/s-MiB/s) not bits. If 6-12 MiB/s is what your seeing displayed in the webUI that sounds right.

pretty sure its megaBytes per second... which isnt terrible if im downloading 1 torrent with that but if i download multiple Linux ISO i cant pass a total of 8ish which is pretty bad.. im going to try qbittorrent and see if there is any difference

OK, I have been reading through all the new posts regarding the nextgen setups.  I updated my docker which was successful.  I can connect successfully using legacy ovpn files from PIA.

 

Deluge: 2.0.4.dev38
PIA ovpn files: legacy
Port Forward: no
Errors: none; connects fine and everything resumes

 

I downloaded the nextgen files via the instructions form Q19 in the VPN Docket FAQ.  I removed the old ovpn and cert files and replaced them with the nextgen files.  I also changed the STRICT_PORT_FORWARD variable to 'yes' since it was set to 'no' while using the legacy files.

 

When I try to start my docker I get the following error in the log:
2020-10-02 10:11:11,741 DEBG 'start-script' stdout output:
Fri Oct 2 10:11:11 2020 AUTH: Received control message: AUTH_FAILED

 

I saw Q16 in the VPN Docker FAQ which states my VPN_USER and/or VPN_PASS are not correct.  I regenerated my username and password from the PIA account site and updated them in the docker settings, but I am still receiving the error.  I even failed back to legacy ovpn files, setting STRICT_PORT_FORWARD to 'no', and everything works fine.  So I am thinking my user ID and password are good/valid since they work with the legacy files just fine.  A couple of questions to those with PIA and have it working with nextgen files:

 

1. Did you download the NextGen zip from the link labeled 'OpenVPN Configuration Files (Recommended Default)'?  The step in Q19 doesn't specify which set of files to use, but I was assuming the top link.

 

2. Are you using the 'PPTP/L2TP/SOCKS Username and Password' from PIA?  I wasn't sure if I should be using a different username and password for VPN_USER and VPN_PASS for the NextGen setup.  This is what works with my legacy ovpn files.

 

3. Are there any other settings you need to change outside of what is stated in Q19 from the VPN Docket FAQ?  I am assuming no or else it would be called out in those steps to switch over to NextGen.

I also tested setting STRICT_PORT_FORWARD variable to 'yes' with legacy files, and another test with nextgen files and the setting it to 'no'.  Both were still failures and I assumed neither of these were the ideal setup so I am not working on troubleshooting those failures.

 

I am attaching my logs for legacy files port forwarding set to 'no', and nextgen files port forwarding set to 'yes' just if anyone wants to look at anything not stated here in my working and not working logs.

LegacyPortFwdNo.txtNextgenPortFwdYes.txt

 

So I am not sure if I need something in my PIA account flagged so I can use the NextGen servers or something else with my PIA account not setup correctly.  I know I am grasping at straws but I am not sure what is going on here.  I can open a ticket with PIA but I wanted to make sure what I am doing is correct before having them check my account on their side.

 

Any help from anyone would be....well....helpful.
Thanks.

2 minutes ago, Burizado said:

OK, I have been reading through all the new posts regarding the nextgen setups.  I updated my docker which was successful.  I can connect successfully using legacy ovpn files from PIA.

 

Deluge: 2.0.4.dev38
PIA ovpn files: legacy
Port Forward: no
Errors: none; connects fine and everything resumes

 

I downloaded the nextgen files via the instructions form Q19 in the VPN Docket FAQ.  I removed the old ovpn and cert files and replaced them with the nextgen files.  I also changed the STRICT_PORT_FORWARD variable to 'yes' since it was set to 'no' while using the legacy files.

 

When I try to start my docker I get the following error in the log:
2020-10-02 10:11:11,741 DEBG 'start-script' stdout output:
Fri Oct 2 10:11:11 2020 AUTH: Received control message: AUTH_FAILED

 

I saw Q16 in the VPN Docker FAQ which states my VPN_USER and/or VPN_PASS are not correct.  I regenerated my username and password from the PIA account site and updated them in the docker settings, but I am still receiving the error.  I even failed back to legacy ovpn files, setting STRICT_PORT_FORWARD to 'no', and everything works fine.  So I am thinking my user ID and password are good/valid since they work with the legacy files just fine.  A couple of questions to those with PIA and have it working with nextgen files:

 

1. Did you download the NextGen zip from the link labeled 'OpenVPN Configuration Files (Recommended Default)'?  The step in Q19 doesn't specify which set of files to use, but I was assuming the top link.

 

2. Are you using the 'PPTP/L2TP/SOCKS Username and Password' from PIA?  I wasn't sure if I should be using a different username and password for VPN_USER and VPN_PASS for the NextGen setup.  This is what works with my legacy ovpn files.

 

3. Are there any other settings you need to change outside of what is stated in Q19 from the VPN Docket FAQ?  I am assuming no or else it would be called out in those steps to switch over to NextGen.

I also tested setting STRICT_PORT_FORWARD variable to 'yes' with legacy files, and another test with nextgen files and the setting it to 'no'.  Both were still failures and I assumed neither of these were the ideal setup so I am not working on troubleshooting those failures.

 

I am attaching my logs for legacy files port forwarding set to 'no', and nextgen files port forwarding set to 'yes' just if anyone wants to look at anything not stated here in my working and not working logs.

LegacyPortFwdNo.txt 103.8 kB · 0 downloads NextgenPortFwdYes.txt 139.39 kB · 0 downloads

 

So I am not sure if I need something in my PIA account flagged so I can use the NextGen servers or something else with my PIA account not setup correctly.  I know I am grasping at straws but I am not sure what is going on here.  I can open a ticket with PIA but I wanted to make sure what I am doing is correct before having them check my account on their side.

 

Any help from anyone would be....well....helpful.
Thanks.

which ovpn file did you pick (what location)? is it one of the approved locations that it mentions in the log when starting deluge

36 minutes ago, wgstarks said:

It looks to me as if you have set a tag for this docker in the repository field. Is it set to "latest". If it's set to 1.3.15_18_ge050905b2-1-04 then it won't install the latest update. You'll need to change the version to latest and install the current version on Deluge v2.

Well, hell, I didn't even know that was as thing. I have no idea how I had a specified version when I didn't even know that was something that could be done. 

 

Thanks for the help, that did it and I'm up and running now. 

 

 

3 minutes ago, Cytomax said:

which ovpn file did you pick (what location)? is it one of the approved locations that it mentions in the log when starting deluge

Yes.  I am using CA Toronto.  It is one of the locations mentioned in the my legacy log.  It doesn't get that far in the nextgen log, but I am assuming it works based on a previous post someone stating it works with nextgen.

 

Thanks for the follow-up question.  I forgot to mention what location I am testing.

Hello!

 

I'm struggling with the final 5% of setting up YaRSS2 with my binhex-DelugeVPN docker container. 

 

I've followed the steps detailed here:   

 

I've been able to successfully set up the client deluge (getting passed all the Python version fun that is posted about everywhere), and the connection to the Server/Container deluge. 

 

Then I get a bit confused about what I should be seeing. My understanding is that  I'll *never* see YaRSS2 config in the Docker container WebUI. However, when I'm on the non-server "thin" client, and I set up an RSS, with the connection manager pointed to the Docker container server, it just downloads to the client machine... which isn't what I want.

 

This sorta seems obvious when I look at the Download config of the client Deluge installation - it's pointed at the local machine. But my confusion is around how these steps were to set up RSS for the server. Am I missing something? Is it impossible to have RSS driven downloads in the Docker container? or have I just missed the last few steps of config?

 

One step that I wasn't quite sure if I achieved, was that installing YaRSS2 on the windows client is supposed to *also* install it on the server somehow? (See quote below)

 

Quote

When running the Deluge daemon, deluged and Deluge client on a separate computers, the plugin must be installed on both machines. Installing a plugin egg through the GTK client will copy the egg to both the local plugins directory, as well as the remote daemon's. However if the Python versions on the local machine and remote server do not match, you will have to copy the egg to the remote server manually.

- https://dev.deluge-torrent.org/wiki/Plugins/YaRSS2#RunningaserverseedboxwithaDelugedaemon

 

I'll keep investigating on my own, but if someone has any guidance or tips, I'd greatly appreciate it!

 

Thanks!

What’s the best way to test other Binhexvpn downloaders without un-installing this one? If I install qbtorrent (for example) can I set it with adjusted ports and sonarr/Radarr will still be able to connect? Maybe it would be better to uninstall this docker first since I can always re-install from previous apps in CA?