Skip to content
The scripts were the problem. Once I had a clean install of 1.3 and removed the scripts, everything worked fine.
The up script was to get the DNS resolver in Tunnelbick to work. Down script undid what the up script built. Not needed with Viscosity, clearly
After upgrade 1.3 Mac hangs after confirming reachability.
Got a problem with Viscosity or need help? Ask here!
- Posts: 14
- Joined: Sun May 22, 2011 9:41 pm
James wrote:Hi Matt,
It seems like you are using a custom OpenVPN up script (up.sh) - do you know what it does? Are you able to post its contents (minus any sensitive addresses)?
Cheers,
James
The scripts were the problem. Once I had a clean install of 1.3 and removed the scripts, everything worked fine.
The up script was to get the DNS resolver in Tunnelbick to work. Down script undid what the up script built. Not needed with Viscosity, clearly
Glad to hear it's now working again!
It would have been working under Viscosity 1.2.3 as Viscosity's DNS support scripts would have been overriding the ones left over from Tunnelblick. However as 1.3 no longer uses up/down scripts (and instead manages DNS settings internally) they would have become active again (and hence the error).
I'm sure a few others will run into the same problem, so thanks for posting the solution!
Cheers,
James
It would have been working under Viscosity 1.2.3 as Viscosity's DNS support scripts would have been overriding the ones left over from Tunnelblick. However as 1.3 no longer uses up/down scripts (and instead manages DNS settings internally) they would have become active again (and hence the error).
I'm sure a few others will run into the same problem, so thanks for posting the solution!
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hi Everyone,
[Update] We now have a beta version available that hopefully works around this issue. Please give it a try and let us know if it solves the problem for you or not.
For everyone experiencing getting stuck at the "Connection is reachable. Starting connection attempt." log message, would you please be able to test the following build? We're completely stuck on this one as we're unable to replicate it - so we need your help!. If this build works please let us know. If it doesn't please send us a copy of the OpenVPN log from the Details window ([email protected] - or feel free to post it here if you are comfortable doing so). You'll find there is a lot of extra debug output in the log which should help us determine what is going on.
Thanks,
James
[Update] We now have a beta version available that hopefully works around this issue. Please give it a try and let us know if it solves the problem for you or not.
For everyone experiencing getting stuck at the "Connection is reachable. Starting connection attempt." log message, would you please be able to test the following build? We're completely stuck on this one as we're unable to replicate it - so we need your help!. If this build works please let us know. If it doesn't please send us a copy of the OpenVPN log from the Details window ([email protected] - or feel free to post it here if you are comfortable doing so). You'll find there is a lot of extra debug output in the log which should help us determine what is going on.
Thanks,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
After downloading 1.3.1b4 - immediately got VPN up and running. Disconnected to try second VPN. Nothing works now. Cannot get first VPN back, but also cannot get second.
Tried to upload screenshot of console (all messages) but got message: Could not upload attachment to ./files/816_217445c89d897a5baf9a12f6596658ad. Will have to email.
Tried to upload screenshot of console (all messages) but got message: Could not upload attachment to ./files/816_217445c89d897a5baf9a12f6596658ad. Will have to email.
Another update after the 1.3.1 beta - I cannot kill Viscosity. Quit does not work. And since it is not a running application in Force Quit, that won't work. I am not actually connected to my server, but Viscosity thinks I am. It won't disconnect and it won't die. Help!