Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ
∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞
Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! Ξ
Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ

troubles connecting

cryptofree: full-bore cryptostorm protection... for free! Capped to 1 megabit down / 500kb up, it's a great way to use cryptostorm in a pinch. Play nice & be safe, ok?

Topic Author
eskimo
Posts: 5
Joined: Tue Mar 21, 2017 8:22 pm

troubles connecting

Postby eskimo » Tue Mar 21, 2017 8:28 pm

Hello,
I've been using CryptoFree for 2 months with narwhal on win 10.
I've been experiencing issues since 2 days, couldn't connect.
I tried to update to v3 today and I still got the same issue.

A "Logging into darknet" stage, I get blocked. Those are 2 last lines (if it could help).

Tue Mar 21 16:25:55 2017 us=309020 UDPv4 link local: [undef]
Tue Mar 21 16:25:55 2017 us=309020 UDPv4 link remote: [AF_INET]195.154.33.73:443

then it stops - connection took longer than 2 min - try to reconnect etc.
What can I do to solve this problem ? I can bring up more information if needed.

Thanks in advance


Topic Author
eskimo
Posts: 5
Joined: Tue Mar 21, 2017 8:22 pm

Re: troubles connecting

Postby eskimo » Wed Mar 22, 2017 9:34 pm

Some more informations
Problem seems to be there :

Code: Select all

TLS Error: TLS key negotiation failed to occur within 17 seconds (check your network connectivity)
 TLS Error: TLS handshake failed
TCP/UDP: Closing socket
SIGUSR1[soft,tls-error] received, process restarting


I tried to open TCP/UDP 1194, didn't improve things.
Any idea ?

User avatar

parityboy
Site Admin
Posts: 1096
Joined: Wed Feb 05, 2014 3:47 am

Re: troubles connecting

Postby parityboy » Sat Mar 25, 2017 5:57 pm

@OP

Can you try connecting to a specific node (one that is more local to you than what the global balancer might give you) and see if you get the same thing?


Topic Author
eskimo
Posts: 5
Joined: Tue Mar 21, 2017 8:22 pm

Re: troubles connecting

Postby eskimo » Sat Mar 25, 2017 7:26 pm

I'm using CryptoFree, so I don't have any token to try.
This is all CryptoFree logs

Code: Select all

Sat Mar 25 15:08:00 2017 us=492101 LZO compression initialized
Sat Mar 25 15:08:00 2017 us=492101 Control Channel MTU parms [ L:1606 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Sat Mar 25 15:08:00 2017 us=493096 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Mar 25 15:08:00 2017 us=495098 Data Channel MTU parms [ L:1606 D:1450 EF:106 EB:143 ET:0 EL:3 AF:3/1 ]
Sat Mar 25 15:08:00 2017 us=495098 Fragmentation MTU parms [ L:1606 D:1400 EF:105 EB:143 ET:1 EL:3 AF:3/1 ]
Sat Mar 25 15:08:00 2017 us=495098 Local Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client'
Sat Mar 25 15:08:00 2017 us=495098 Expected Remote Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server'
Sat Mar 25 15:08:00 2017 us=495098 Local Options hash (VER=V4): 'ff724a72'
Sat Mar 25 15:08:00 2017 us=496104 Expected Remote Options hash (VER=V4): '545e2783'
Sat Mar 25 15:08:00 2017 us=496104 UDPv4 link local: [undef]
Sat Mar 25 15:08:00 2017 us=496104 UDPv4 link remote: [AF_INET]195.154.33.73:443
Sat Mar 25 15:08:17 2017 us=762532 TLS Error: TLS key negotiation failed to occur within 17 seconds (check your network connectivity)
Sat Mar 25 15:08:17 2017 us=762532 TLS Error: TLS handshake failed
Sat Mar 25 15:08:17 2017 us=762532 TCP/UDP: Closing socket
Sat Mar 25 15:08:17 2017 us=762532 SIGUSR1[soft,tls-error] received, process restarting
Sat Mar 25 15:08:17 2017 us=762532 Restart pause, 2 second(s)
Sat Mar 25 15:08:19 2017 us=763078 LZO compression initialized
Sat Mar 25 15:08:19 2017 us=763078 Control Channel MTU parms [ L:1606 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Sat Mar 25 15:08:19 2017 us=763078 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Mar 25 15:08:19 2017 us=764109 Data Channel MTU parms [ L:1606 D:1450 EF:106 EB:143 ET:0 EL:3 AF:3/1 ]
Sat Mar 25 15:08:19 2017 us=764109 Fragmentation MTU parms [ L:1606 D:1400 EF:105 EB:143 ET:1 EL:3 AF:3/1 ]
Sat Mar 25 15:08:19 2017 us=764109 Local Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client'
Sat Mar 25 15:08:19 2017 us=764109 Expected Remote Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server'
Sat Mar 25 15:08:19 2017 us=764109 Local Options hash (VER=V4): 'ff724a72'
Sat Mar 25 15:08:19 2017 us=764109 Expected Remote Options hash (VER=V4): '545e2783'
Sat Mar 25 15:08:19 2017 us=764109 UDPv4 link local: [undef]
Sat Mar 25 15:08:19 2017 us=764109 UDPv4 link remote: [AF_INET]195.154.33.73:443
Sat Mar 25 15:08:36 2017 us=437074 TLS Error: TLS key negotiation failed to occur within 17 seconds (check your network connectivity)
Sat Mar 25 15:08:36 2017 us=437074 TLS Error: TLS handshake failed
Sat Mar 25 15:08:36 2017 us=437074 TCP/UDP: Closing socket
Sat Mar 25 15:08:36 2017 us=437074 SIGUSR1[soft,tls-error] received, process restarting
Sat Mar 25 15:08:36 2017 us=437074 Restart pause, 2 second(s)


And this is me trying to connect to standard - France with the free token (obviously wouldn't work but got some more code to show) :

Code: Select all

Sat Mar 25 15:22:55 2017 us=660735 LZO compression initialized
Sat Mar 25 15:22:55 2017 us=660735 Control Channel MTU parms [ L:1606 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Sat Mar 25 15:22:55 2017 us=660735 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Mar 25 15:22:55 2017 us=691987 Data Channel MTU parms [ L:1606 D:1450 EF:106 EB:143 ET:0 EL:3 AF:3/1 ]
Sat Mar 25 15:22:55 2017 us=691987 Fragmentation MTU parms [ L:1606 D:1400 EF:105 EB:143 ET:1 EL:3 AF:3/1 ]
Sat Mar 25 15:22:55 2017 us=691987 Local Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client'
Sat Mar 25 15:22:55 2017 us=691987 Expected Remote Options String: 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server'
Sat Mar 25 15:22:55 2017 us=691987 Local Options hash (VER=V4): 'ff724a72'
Sat Mar 25 15:22:55 2017 us=691987 Expected Remote Options hash (VER=V4): '545e2783'
Sat Mar 25 15:22:55 2017 us=691987 UDPv4 link local: [undef]
Sat Mar 25 15:22:55 2017 us=691987 UDPv4 link remote: [AF_INET]212.83.163.209:1194
Sat Mar 25 15:22:55 2017 us=738867 TLS: Initial packet from [AF_INET]212.83.163.209:1194, sid=e9a02d05 7b4b9044
Sat Mar 25 15:22:55 2017 us=738867 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Mar 25 15:22:55 2017 us=770122 VERIFY OK: depth=1, C=CA, ST=QC, L=Montreal, O=Katana Holdings Limite /  cryptostorm_darknet, OU=Tech Ops, CN=cryptostorm_is, emailAddress=certadmin@cryptostorm.is
Sat Mar 25 15:22:55 2017 us=770122 VERIFY OK: nsCertType=SERVER
Sat Mar 25 15:22:55 2017 us=770122 VERIFY OK: depth=0, C=CA, ST=QC, L=Montreal, O=Katana Holdings Limite /  cryptostorm_darknet, OU=Tech Ops, CN=server, emailAddress=certadmin@cryptostorm.is
Sat Mar 25 15:22:56 2017 us=35762 NOTE: --mute triggered...
Sat Mar 25 15:22:56 2017 us=35762 5 variation(s) on previous 3 message(s) suppressed by --mute
Sat Mar 25 15:22:56 2017 us=35762 [server] Peer Connection Initiated with [AF_INET]212.83.163.209:1194
Sat Mar 25 15:22:58 2017 us=223425 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Sat Mar 25 15:22:58 2017 us=223425 AUTH: Received control message: AUTH_FAILED
Sat Mar 25 15:22:58 2017 us=223425 SIGTERM received, sending exit notification to peer


Thanks for helping

User avatar

Fermi
Site Admin
Posts: 218
Joined: Tue Jun 17, 2014 11:42 am

Re: troubles connecting

Postby Fermi » Sat Mar 25, 2017 10:08 pm

Code: Select all

Sat Mar 25 15:08:00 2017 us=496104 UDPv4 link remote: [AF_INET]195.154.33.73:443
Sat Mar 25 15:08:17 2017 us=762532 TLS Error: TLS key negotiation failed to occur within 17 seconds (check your network connectivity)
Sat Mar 25 15:08:17 2017 us=762532 TLS Error: TLS handshake failed


That node is down at the moment, this explains the error you are getting.
There's a second Cryptofree node, so after an

Code: Select all

ipconfig /flushdns
, there's a possibility the widget will connect to the working one.

We will look into this issue.

/fermi


Topic Author
eskimo
Posts: 5
Joined: Tue Mar 21, 2017 8:22 pm

Re: troubles connecting

Postby eskimo » Sat Mar 25, 2017 11:44 pm

I tried to flush several (>10) times, same node coming over and over.
Ready to bring more information if requested.
Thanks again


Topic Author
eskimo
Posts: 5
Joined: Tue Mar 21, 2017 8:22 pm

Re: troubles connecting

Postby eskimo » Tue Mar 28, 2017 10:15 pm

Today it worked - this node seems to be fixed.
Thanks you for your work.


Return to “cryptofree: no-cost cryptostorm network access”

Who is online

Users browsing this forum: No registered users and 1 guest

cron

Login