superstyle wrote:just upgraded to the lastest one. did some speedtest getting almost full speed
Can you post your findings in the Cryptotorm Speedtest Thread? Many thanks.

superstyle wrote:just upgraded to the lastest one. did some speedtest getting almost full speed
themanwithavan wrote:Well I take it back. Seems to last a bit longer but now instead of a dialogue box about unable to connect the client now hangs on attempting to reset to crypto dns. The log says after 20 or 40 minutes that it's resetting due to time out. But that isn't the case at all. This is so frustrating. Cryptostorm is so unstable.
toupie wrote:not very technology literate and new to the world of vpn.
using win xp sp3
currently using sexynarwhal2_22 - no major issues apart from occasional crashing while running with standard node (but rare).
installed beta version of 24 may 2016
(after having uninstalled sexynarwhal2_22 and deleting cs and tap-windows folders in program files and rebooting)
on installing getting error installing tap-windows, but installation complete.
on running the widget v3, getting it's getting longer than 60 seconds, trying again, at the 3rd automatic try getting this message:
Can't load fwpuclnt.dll
Options error: Failed to enable --block-outside-dns. Maybe WFP is not supported on your system?
after installing tap-windows-9.21.2.exe manually, no longer getting the above error message on re-installing widget v3, but still not being able to connect.
installed beta version of 25 may 2016
(after having uninstalled widget v3 of 24 may 2016 and deleting cs and tap-windows folders in program files and rebooting)
no error message during installation
still cannot connect and getting it's getting longer than 60 seconds, trying again, and no error message after the 5th try (but still no connection).
going back to sexynarwhal2_22 for the time being, until a new widget v3 version is available.
thank you.
marzametal wrote:The scenario in the above post happened to me as well...
It turns out that the widget defaults to a specific exit node after install/update, and unless the end user picks it up by checking connection logs, he/she will throw a fit because s**t doesn't work.
For me, it was one of the US nodes, off the top of my head, cannot remember which one.
df wrote:@JJ
It looks like dnscrypt is running correctly. I guess try doing the same thing the widget would do (from cmd):
nslookup windows-balancer.cstorm.pw 127.0.0.1
That'll lookup the first windows balancer against dnscrypt.
But as Khariz said, you could just disable dnscrypt since you're not facing any adversaries that are capable of causing problems via DNS.
bricus wrote:Hi,
I was on a previous v3 build, and since several updates happened within the widget, I’m not able to use a v3 build any more – well, I just have the v3.0.0.66 to test.
It stops at the “Logging into the darknet” step, no log is visible, just a black square.
Is there a way to get the log elsewhere?
Widget v2.22 is working.
Thanks in advance for any help.
Khariz wrote:I'm keeping the 2.4 widget. It works great for me on Windows 10. I just keep answering no when it asks me to "upgrade" to 2.3
Return to “cryptostorm in-depth: announcements, how it works, what it is”
Users browsing this forum: Bing [Bot] and 9 guests