[Support] binhex - DelugeVPN


Recommended Posts

I'm having issues accessing the GUI to my container. I've completed switching over to the new NextGen for PIA, and have compelted Q22 in the FAQ. Attached is a quick grab from the logs. Not sure where to go from here.logs.txt

 

Edited to move the logs.txt to the end of the message.

Edited by AceDaPig
Link to comment
2 minutes ago, AceDaPig said:

I'm having issues accessing the GUI to my container. I've completed switching over to the new NextGen for PIA, and have compelted Q22 in the FAQ. Attached is a quick grab from the logs. Not sure where to go from here.logs.txt

 

Edited to move the logs.txt to the end of the message.

from your log:-

2020-11-09 11:26:20 AUTH: Received control message: AUTH_FAILED

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

  • Like 1
Link to comment
1 hour ago, DontWorryScro said:

i dont know if this is helpful but i had a similar issue.  I had been using the download link for the next gen servers in the FAQ and the auth errors were persisting.  But then I made sure I was actually logged in to the PIA site and only then did I download from their openvpn - next gen link on the site and it connected no problem.  Not sure if logging in updates a link for you or gives you a more current cert or what.  Could also be total coincidence or something else.  All this to say can't hurt to double check that as another step in troubleshooting.

that was a great suggestion! (sadly it didn't work) but i appreciate the help and definitely know that they can' sometimes repackage things for those that are logged in versus those that arent. Strange.

 

FWIW in case anyone else reads this - here is the error message:

2020-11-09 13:55:13,017 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2020-11-09 13:55:13,022 DEBG 'start-script' stdout output:
2020-11-09 13:55:13 DEPRECATED OPTION: ncp-disable. Disabling cipher negotiation is a deprecated debug feature that will be removed in OpenVPN 2.6

2020-11-09 13:55:13,022 DEBG 'start-script' stdout output:
2020-11-09 13:55:13 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-256-gcm' to --data-ciphers or change --cipher 'aes-256-gcm' to --data-ciphers-fallback 'aes-256-gcm' to silence this warning.
2020-11-09 13:55:13 WARNING: file 'credentials.conf' is group or others accessible
2020-11-09 13:55:13 OpenVPN 2.5.0 [git:makepkg/a73072d8f780e888+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 27 2020
2020-11-09 13:55:13 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10

2020-11-09 13:55:13,022 DEBG 'start-script' stdout output:
2020-11-09 13:55:13 NOTE: the current --script-security setting may allow this conf

 

Link to comment

Im seeing an issue where i cannot connect to deluge, i'm getting connection refused. When I take a look a the logs i can see the following every couple of minutes:

 

DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-256-gcm' to --data-ciphers or change --cipher 'aes-256-gcm' to --data-ciphers-fallback 'aes-256-gcm' to silence this warning.

The top of my config is setup as below:

client
dev tun
proto udp
remote sweden.privacy.network 1198
remote denmark.privacy.network 1198
remote man.privacy.network 1198
remote nl-amsterdam.privacy.network 1198
remote no.privacy.network 1198
remote brussels.privacy.network 1198
remote lu.privacy.network 1198
remote malta.privacy.network 1198
remote monaco.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>

Any advice is appreciated.

Link to comment
On 11/8/2020 at 10:42 PM, tjb_altf4 said:

This issue is still happening, logs show this on repeat (wireguard connection)


2020-11-09 10:59:03,623 DEBG 'watchdog-script' stdout output:
0

2020-11-09 11:00:38,903 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '41561'

2020-11-09 11:15:39,838 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '41561'

2020-11-09 11:29:30,654 DEBG 'watchdog-script' stdout output:
0

2020-11-09 11:29:34,772 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

I can connect to UI and STRICT_PORT_FORWARD is enabled, so there is an established vpn connection (based on previous experience), but nothing actually connects.

Restart the container and everything starts to connect again.

 

Other than that its working quite well.

for what it's worth, i'm getting this too in my logs, the container is operating normally right now (seeding and downloading fine) but I have had this issue in the past where I've had to restart the container. Previously, it ran for 11 days without issue. 

2020-11-10 05:58:24,937 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:13:30,983 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:19:26,115 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:19:26,991 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:19:27,904 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:28:31,377 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:43:31,851 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:50:33,809 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:50:34,691 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:50:35,286 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:58:32,265 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'

Not sure if this is an early indicator of failure, or what. 

Edited by eat_eat_the_doreets
getting rid of doublespacing in code block
Link to comment
12 minutes ago, eat_eat_the_doreets said:

2020-11-10 06:50:34,691 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:50:35,286 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:58:32,265 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'

Not sure if this is an early indicator of failure, or what. 

it isnt, i just need to fix up the web scrape for portchcker.co, its falling back to the second website so this is a not an issue right now.

Link to comment
Just now, binhex said:

from your log:-


2020-11-10 11:05:28,840 DEBG 'start-script' stdout output:
2020-11-10 11:05:28 AUTH: Received control message: AUTH_FAILED

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

yup - i did that already - i entered in the password and userid i use to login to the website. I've checked it in the container settings and i've checked it the credentials file that's created in the openvpn directory and it matches my credentials. I've been setup like that for years. Strange isn't it?

Link to comment
3 minutes ago, helpermonkey said:

yup - i did that already - i entered in the password and userid i use to login to the website. I've checked it in the container settings and i've checked it the credentials file that's created in the openvpn directory and it matches my credentials. I've been setup like that for years. Strange isn't it?

ok so your credential username is def in the format Pxxxxxx right? NOT the generated L2TP/Proxy creds? is the length of your password over 99 characters?

 

edit - keep in mind PIA HAVE changed things so you can no longer use the generated credentials, you MUST use the website login credentials for vpn connectivity.

Edited by binhex
Link to comment
6 minutes ago, strike said:

Why not? I'm using 2.0.4dev38 thin client on windows, works fine

Sorry if it wasn't clear on my post. From what I've read and experienced you cannot use deluge for windows v1.3.15 to remote connect to deluge 2.x which is what the delugevpn container runs. Hopefully I am wrong in this and I am just change a config somewhere

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.