Skip to content
Viscosity does not recognize the connection as tls-client
Got a problem with Viscosity or need help? Ask here!
Starting a week ago, whenever I'm trying to connect to my OpenVPN I get the following error (using Viscosity 1.0.8):
----
Options error: Parameter pkcs12_file can only be specified in TLS-mode, i.e. where --tls-server or --tls-client is also specified.
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Make sure Viscosity is not running under a File Vault protected location (put Viscosity in the Applications folder).
- Make sure the configuration is valid. Check the connection settings for the connection using Viscosity and make sure all settings are correct.
----
It seems that Viscosity is unable to determine that the connection needs the tls-client switch. In fact if I add manually this switch in the additional options, the connection will work, but Viscosity will remove the switch after disconnection, I believe because it is considered a "managed" switch.
My configuration file is as follows (from Library/Application Support/Viscosity/OpenVPN/2/config.conf):
---
#-- Config Auto Generated By Viscosity --#
#viscosity startonopen true
#viscosity dhcp true
#viscosity dnssupport true
#viscosity name xyz
remote x.y.z 443
pull
proto tcp-client
ping 10
pkcs12 pkcs.p12
ping-restart 3600
tun-mtu 1400
dev tun
route a.b.c.d 255.255.255.0 default default
route e.f.g.h 255.255.255.0 default default
route i.j.k.l 255.255.255.0 default default
route m.n.o.p 255.255.255.0 default default
cipher AES-128-CBC
ns-cert-type server
-----
What is wrong here?
David
----
Options error: Parameter pkcs12_file can only be specified in TLS-mode, i.e. where --tls-server or --tls-client is also specified.
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Make sure Viscosity is not running under a File Vault protected location (put Viscosity in the Applications folder).
- Make sure the configuration is valid. Check the connection settings for the connection using Viscosity and make sure all settings are correct.
----
It seems that Viscosity is unable to determine that the connection needs the tls-client switch. In fact if I add manually this switch in the additional options, the connection will work, but Viscosity will remove the switch after disconnection, I believe because it is considered a "managed" switch.
My configuration file is as follows (from Library/Application Support/Viscosity/OpenVPN/2/config.conf):
---
#-- Config Auto Generated By Viscosity --#
#viscosity startonopen true
#viscosity dhcp true
#viscosity dnssupport true
#viscosity name xyz
remote x.y.z 443
pull
proto tcp-client
ping 10
pkcs12 pkcs.p12
ping-restart 3600
tun-mtu 1400
dev tun
route a.b.c.d 255.255.255.0 default default
route e.f.g.h 255.255.255.0 default default
route i.j.k.l 255.255.255.0 default default
route m.n.o.p 255.255.255.0 default default
cipher AES-128-CBC
ns-cert-type server
-----
What is wrong here?
David
- Posts: 2
- Joined: Sat Jan 09, 2010 4:50 am
I'm getting this too.
It seems to be an issue wherein you can't select psk12 as the key method. For previously imported connections, things may work until you look at the key setting page, after which things keep getting set as static key. You can see the bug visually as the psk12 text is missing from the drop down, and there is only one space to set a key, like the static key page, while the pks12 page usually has two spaces.
I seem to remember there was a similar bug in 1.0.7 where if you selected static key, you couldn't go back and select psk12, but this could be solved by creating a new connection.
Suffice to say this bug ruined the last few hours for me as it made it impossible to connect to my VPN. The only way to solve it I could find was to revert back to 1.0.7.
I couldn't find past versions on the Viscosity site, but managed to find a copy at:
It seems to be an issue wherein you can't select psk12 as the key method. For previously imported connections, things may work until you look at the key setting page, after which things keep getting set as static key. You can see the bug visually as the psk12 text is missing from the drop down, and there is only one space to set a key, like the static key page, while the pks12 page usually has two spaces.
I seem to remember there was a similar bug in 1.0.7 where if you selected static key, you couldn't go back and select psk12, but this could be solved by creating a new connection.
Suffice to say this bug ruined the last few hours for me as it made it impossible to connect to my VPN. The only way to solve it I could find was to revert back to 1.0.7.
I couldn't find past versions on the Viscosity site, but managed to find a copy at:
Hi Guys,
How do you get on with the latest beta release? Hopefully this issue has been fixed up.
You can download the latest beta version from:
http://www.viscosityvpn.com/forum/viewt ... p=134#p134
Regards,
James
How do you get on with the latest beta release? Hopefully this issue has been fixed up.
You can download the latest beta version from:
http://www.viscosityvpn.com/forum/viewt ... p=134#p134
Regards,
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
- Posts: 2
- Joined: Sat Jan 09, 2010 4:50 am
Seems to be working here too, thanks for the quick update!
5 posts
Page 1 of 1