[Support] binhex - SABnzbdVPN


Recommended Posts

I've found the fix for the issue.... PIA have not updated their stack of ovpn config files. You need to go into their config file generator ( https://www.privateinternetaccess.com/pages/ovpn-config-generator ) and generate the .ovpn file for your particular server. I did this and replaced it with the existing .ovpn file and its working as it should... no need to make any changes to the file. 

 

EDIT

 

Just FYI... I chose nextgen servers and openvpn Version 2.4 or newer... and windows platform (by accident but it worked)... Switzerland server

Edited by tazire
Link to comment
1 hour ago, tazire said:

I've found the fix for the issue.... PIA have not updated their stack of ovpn config files. You need to go into their config file generator ( https://www.privateinternetaccess.com/pages/ovpn-config-generator ) and generate the .ovpn file for your particular server. I did this and replaced it with the existing .ovpn file and its working as it should... no need to make any changes to the file. 

 

EDIT

 

Just FYI... I chose nextgen servers and openvpn Version 2.4 or newer... and windows platform (by accident but it worked)... Switzerland server

I don't think so I'm afraid - at least, not for all servers.  The nextgen 2.4+ ovpn file from the config file generator for the Bahamas server is essentially the same as the zip file version, and doesn't work without adding in npc-disable.

Link to comment
12 minutes ago, David2376 said:

All servers are working for me.....You have to use your PIA username and password in the container. For some reason PPTP/L2TP/SOCKS username and password are not being accepted. 

I always have used that username and pw. Most recent update seems to have revealed that I was wrong. back to the same issue as before. facepalm!

Link to comment
On 11/2/2020 at 5:34 PM, DoItMyselfToo said:

Using the "openvpn-strong-nextgen" files from PIA and only adding the line "data-ciphers-fallback aes-256-gcm" to the OVPN file in use worked instantly.  In other words, copy ctyke's shown above.

This was the answer right here. Had to download the "Strong" Nextgen files and insert that line. Instantly started working. 

Link to comment
On 11/3/2020 at 3:43 PM, tazire said:

I've found the fix for the issue.... PIA have not updated their stack of ovpn config files. You need to go into their config file generator ( https://www.privateinternetaccess.com/pages/ovpn-config-generator ) and generate the .ovpn file for your particular server. I did this and replaced it with the existing .ovpn file and its working as it should... no need to make any changes to the file. 

 

EDIT

 

Just FYI... I chose nextgen servers and openvpn Version 2.4 or newer... and windows platform (by accident but it worked)... Switzerland server

 

FYI I started having problems (again) with the Toronto server, and my logs would repeatedly end with "Peer connection Initiated" and then it would go through the connect dance again. I used the config generator above (selected Linux and Nextgen), dropped it in the openvpn directory and the container was able to connect.

 

This docker has been a bastion of reliability until the last week... hopefully gets itself sorted.

Link to comment
3 hours ago, binhex said:

thanks for the detailed explanation of your issue \s, before i whip out my crystal ball can you tell me what 'issues' you are having?

Im sorry my intent was just to make a light comment. I expected for me not to be the only one and I know its frustrating when you think you are alone with issues so my comment was meant to let others know not alone. My issues have been mentioned already by others so I am just patiently waiting to see how solutions keep coming and I will keep trying, im positive as always a solution will come that will work.

Link to comment
35 minutes ago, NeoSys said:

I expected for me not to be the only one and I know its frustrating when you think you are alone with issues so my comment was meant to let others know not alone.

i think you are alone with your issue, thats why i need to know what it is, until that time i cannot help.

35 minutes ago, NeoSys said:

My issues have been mentioned already by others

and that issue is? i have looked at your profile and you have made no other posts in this thread.

Link to comment

@NeoSys - You aren't being clear, but just to try and clarify what I think is going on here if your 'issue' is with PIA.

 

1. PIA's support for OpenVPN V2.5 is very spotty and varies from server to server. 

2. I also think this is changing as they upgrade servers, so a server that worked yesterday might not today, or vice-versa.

3. As far as I can tell, best advice right now, no matter what cipher you are using, is to make sure you have the 'ncp-disable' line in your ovpn file. It might work without on some servers but it's a dynamic situation.

4. Also make sure you are using your PIA login username and password which start with p--------, not the SOCKS one.

 

Edited by Lignumaqua
Link to comment

I've been struggling with this too. I downloaded the strong files and dropped them in (Toronto). Before editing the opvn file, I restarted just to test and it worked!

 

My problem now is that Sonarr isn't going through the proxy. I tested this by opening the console and typing curl ifconfig.io and get my IP from my ISP. Doing the same with SAB's docker I get an IP in Toronto. If I change my browser to use the proxy it works. Any idea why?

 

Thanks

Link to comment
11 hours ago, jcato said:

I tested this by opening the console and typing curl ifconfig.io and get my IP from my ISP.

completely expected, a proxy server works at an application layer NOT an os layer, so unless you get curl to use the proxy then it will go out through your isp's connection.

Link to comment
On 11/5/2020 at 10:46 AM, Lignumaqua said:

@NeoSys - You aren't being clear, but just to try and clarify what I think is going on here if your 'issue' is with PIA.

 

1. PIA's support for OpenVPN V2.5 is very spotty and varies from server to server. 

2. I also think this is changing as they upgrade servers, so a server that worked yesterday might not today, or vice-versa.

3. As far as I can tell, best advice right now, no matter what cipher you are using, is to make sure you have the 'ncp-disable' line in your ovpn file. It might work without on some servers but it's a dynamic situation.

4. Also make sure you are using your PIA login username and password which start with p--------, not the SOCKS one.

 

Thanks I have tried all the options here. I just did exactly above right now. The problem that I am having is after the container starts I click on "Status and interface options"  and I get "Public IPv4 address Connection failed!" and "Nameserver / DNS Lookup Connection failed!" if I keep clicking on refresh eventually I will get the PIA IP address and the DNS but a few minutes later I will get the same error messages. If I try to download something the file will take for eve to fetch and than it will just sit there and either download after a while or abort. Now an aborted file I will retry and sometimes it will actually download correctly.

 

I am using 4096 Files and using US New York

On 11/5/2020 at 9:10 AM, binhex said:

i think you are alone with your issue, thats why i need to know what it is, until that time i cannot help.

and that issue is? i have looked at your profile and you have made no other posts in this thread.

Again I did not mean to bother. The biggest issue for me to post here is I am like really new so sometimes I do not know how to answer questions so the way I fix things is by waiting for others to keep asking and I try what they are told how to fixes and up to now I always find a fix lol.

 

But please if you can look at my issue above and if you need more info please ask away and I will do my best not to look like an idiot finding what you need for me to help me fix this.

 

I love this container and never had an issue I use all your containers as recommended by spaceinvader and I am so glad I have done that. So please do not take anything I have said or asked as some king of insult or dig, I am so thankful for people like you and can only but praise your amazing work.

 

 

Thank you both!

 

VIc

Link to comment

Good evening all.  I'm also a user that has enjoyed the stability of this container for a long time.  Starting this week, I started to have problem.

I removed the files from the SABVPN OpenVPN folder

Downloaded the Openvpn-nextgen Files this evening and added CA Toronto and the PM and CRT File

 

I followed A22 here

It corrected my issue.

 

Thank you very very much.

 

 

Link to comment
On 11/4/2020 at 2:45 AM, David2376 said:

All servers are working for me.....You have to use your PIA username and password in the container. For some reason PPTP/L2TP/SOCKS username and password are not being accepted. 

I had been struggling with this issue all day. Weird part is NZBGETVPN works with PPTP/L2TP/SOCKS Username and Password, but delugevpn you have to use your actually login. Everything was working normally until my power outage and my dockers restarted.

Link to comment

Are people just experiencing problems with PIA and not AirVPN too?

 

Since the update last week I have not been able to access the GUI, but found the container was showing as orphaned?

 

Reinstalled new version, but could not establish a VPN connection + Sonar and Radar can't see index sites either.

 

I have ended up having to restore my app data to a previous version, so assume now running older version of SabnzbVPN. But it's working.

Edited by clevoir
Missing ?
Link to comment

Hi all,

 

I'm also unable to get connected to PIA servers anymore.

I keep getting this warning:

2020-11-07 16:21:21,750 DEBG 'start-script' stdout output:
2020-11-07 16:21:21 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

38212338_Screenshot2020-11-07at16_37_26.png.19cf317ca50655f6eccf50c5c94c28f3.png

 

I tried several OVPN config files from PIA, with different ciphers and none is working now.

 

Attached log and redacted PIA info and IPs.

 

Best.

supervisord_redacted.log

Link to comment

Hi Binhex, I updated my docker yesterday (6th Nov 2020) for BINHEX_SABNZBDVPN and now it is not working anymore. When I disable the vpn it works fine but when I enable the VPN it doesn't work at all. Would you be able to advise what might have happened for this to have stopped working all of a sudden please?

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.