[Support] binhex - DelugeVPN


8529 posts in this topic Last Reply

Recommended Posts

On 11/7/2020 at 8:03 PM, helpermonkey said:

i have - i've used CA Montreal and Netherlands and keep getting that message.

 

Currently trying CA Montreal and this is what the top of that file looks like:


client
dev tun
proto udp
remote ca-montreal.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>

here's the recent log:


2020-11-07 23:02:03,600 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 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-07 23:02:03,601 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 WARNING: file 'credentials.conf' is group or others accessible
2020-11-07 23:02:03 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-07 23:02:03 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10

2020-11-07 23:02:03,601 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-11-07 23:02:03,601 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----


2020-11-07 23:02:03,601 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 TCP/UDP: Preserving recently used remote address: [AF_INET]199.36.223.162:1198
2020-11-07 23:02:03 UDP link local: (not bound)
2020-11-07 23:02:03 UDP link remote: [AF_INET]199.36.223.162:1198

2020-11-07 23:02:03,727 DEBG 'start-script' stdout output:
2020-11-07 23:02:03 [montreal411] Peer Connection Initiated with [AF_INET]199.36.223.162:1198

2020-11-07 23:02:04,729 WARN received SIGTERM indicating exit request
2020-11-07 23:02:04,729 DEBG killing watchdog-script (pid 173) with signal SIGTERM
2020-11-07 23:02:04,729 INFO waiting for start-script, watchdog-script to die
2020-11-07 23:02:04,746 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23342285760160 for <Subprocess at 23342286252352 with name watchdog-script in state STOPPING> (stdout)>
2020-11-07 23:02:04,746 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23342285988768 for <Subprocess at 23342286252352 with name watchdog-script in state STOPPING> (stderr)>
2020-11-07 23:02:04,746 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-11-07 23:02:04,747 DEBG received SIGCHLD indicating a child quit
2020-11-07 23:02:04,747 DEBG killing start-script (pid 172) with signal SIGTERM
2020-11-07 23:02:04,896 DEBG 'start-script' stdout output:
2020-11-07 23:02:04 AUTH: Received control message: AUTH_FAILED

is it possible that it's having a problem b/c I have 2 factor enabled on PIA? I can't imagine that's it b/c that's been in place for a long long time but that's the only thing i can think of ... shrug.

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.

Edited by DontWorryScro
typo fix
Link to post
  • Replies 8.5k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

ok thats fine, so you are using privoxy in this case and NOT network binding multiple containers.   so good news, at long last i am able to replicate one of the issues here, so if i set sona

Posted Images

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 post
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

Link to post
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 post

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 post
10 hours ago, karldonteljames said:

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:

thats a deprecation warning, its not an error, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Link to post
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 post
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 post
2 minutes ago, helpermonkey said:

Here's my log file 🙂 i've removed my userid and password.

supervisord.log 1.85 MB · 0 downloads

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

Link to post
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 post
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 post
Just now, binhex said:

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

yeah - its my Pxxxxxxx but my password is over 99 characters. I'll shorten that up right now and give that a try. I'll be back momentarily.

Link to post
Just now, helpermonkey said:

that was it! the password was too long. Odd that it has worked for years but anywho - all good now.

excellent, thats two people who have had that issue, going to add that to the faq q16 🙂

Link to post

I am having an issue. I am running deluge 1.3.15 for windows on my local client and binhex-delugevpn container on unraid. I am trying to figure out a way to create torrents to and direct them to my container. How are people accomplishing this if 1.3.15 and 2.0 versions aren't compatible for remote setup?

Link to post
7 minutes ago, DontWorryScro said:

When I try to update from binhex/arch-delugevpn:2.0.3-2-01 to binhex/arch-delugevpn:latest I get error spam re: No such container.

 

Why is dis?

I believe “latest” isn’t a valid tag. Try just deleting the colon and everything after it in the repository field.

Link to post
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 post

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.