Page 1 of 1

.ru server problems

Posted: Sun May 10, 2015 12:21 am
by parib
Hi,

I use and love your service since a lot of months, but since about one to two weeks I have problems with the .ru-Server.
I can connect to the iceland, .fr-server ... but not to the .ru-server. I can ping it, but I can not connect.
I used it the last 6 month with my router. But since about a week I can not connect.
I tried windows with your soft with the same result: No connection to the .ru-server.

Are there problems at the moment? Do you need additional infos?

(I contacted support via E-Mail but did not get any answer the last 2 - 3 days)

Log from my router:
May 7 17:47:30 dnsmasq[13815]: read /etc/hosts - 5 addresses
May 7 17:47:30 dnsmasq[13815]: using nameserver 79.134.235.131#53
May 7 17:47:30 dnsmasq[13815]: using nameserver 79.134.235.132#53
May 7 17:47:30 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:47:36 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:47:42 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:47:48 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:47:54 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:48:09 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:48:15 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:48:21 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused
May 7 17:48:30 openvpn[13808]: TCP: connect to [AF_INET]91.214.70.206:443
failed, will try again in 5 seconds: Connection refused

Thanks,

parib

Re: .ru server problems

Posted: Sun May 10, 2015 12:56 pm
by Fermi
Parib,

You're connecting to Russia using TCP. I've tested it and I'm also unable to connect using TCP:

Sun May 10 08:46:21 2015 Attempting to establish TCP connection with [AF_INET]91.214.70.206:443 [nonblock]
Sun May 10 08:46:22 2015 TCP: connect to [AF_INET]91.214.70.206:443 failed, will try again in 5 seconds: Connection refused


Using UDP succeeds:

Sun May 10 08:39:34 2015 TLS: Initial packet from [AF_INET]91.214.70.206:443, sid=1bdfec2a a87f6634
Sun May 10 08:39:34 2015 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun May 10 08:39:34 2015 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
...
Sun May 10 08:39:37 2015 /usr/sbin/ip route add 128.0.0.0/1 via 10.33.0.1
Sun May 10 08:39:37 2015 Initialization Sequence Completed


Connecting to other nodes using TCP succeeds. So for now I advise you to use UDP for the Russian node until TCP is accepted again.

Regards,

/Fermi

Re: .ru server problems

Posted: Sun May 10, 2015 1:05 pm
by parib
Hi Fermi,

thank you for your fast answer. But with UDP my performance drops by 80 % to 20 % of the TCP speed, because I chain VPNs from different providers and this is my 2nd part of the chain. So this is not really an option. For the time being fixed, I use another country.

Once again: Thank you for your fast answer.

Re: .ru server problems

Posted: Sun May 10, 2015 5:01 pm
by parityboy
@parib

Considering the anonymity provided by Cryptostorm, it should be the first part of your VPN chain. :D

Re: .ru server problems

Posted: Tue May 12, 2015 6:51 am
by marzametal
LOL... seen a lot of gob-flapping recently about chaining VPNs... and CS not being the first cab off of the rank. You're just asking for trouble.

Re: .ru server problems

Posted: Sat May 23, 2015 10:38 am
by parib
... two weeks later: The same problem.
Is there any reason, why TCP-connections do not work at the .ru server?
And: I wrote a mail about 2 weeks ago at support@ with no answer.

Laika is doing fine, she may in fact have taught us something wonderful

Posted: Sat May 23, 2015 4:29 pm
by cryptostorm_team
I'm not at liberty to share details yet, but given the frustrating delays you've had it seems fair to at least say something.


The problem you're seeing isn't... conventional. Nor is it unique to our Leningrad offramp. I know the others are working some long hours to get a published explanation ready.


But the good stuff is the solution we might have in hand for this. If that holds up under fast track testing, it's a game changer.

And I'm really sorry but we can't say more than that right now. When the embargo lifts any day now, it's easy to see why we had to wait - all good, nothing but.

Meanwhile clean pcap session captures of these... incidents are really helpful. And I'm sorry to sound like a politician ducking questions here. It's not that at all. But more is less wrt details beyond that. For a few more days at least.


Thanks for being patient, from all us here - it's likely to be more than worth it when the dust settles.

~ cryptostorm_team

Re: .ru server problems

Posted: Tue Jun 02, 2015 6:33 am
by marzametal
Any chance of an update at what's going on behind the scenes...