SparkLabs Forum.

Community Help.


Connection Import Failed message for .visz 1.7.4

Clients that have upgraded to 1.7.4 on Windows are getting a Connection Import Failed dialogue when attempting to double-click a software-generated .visz configuration package that we distribute for our VPN service.

Have there been any changes to the format of the .visz package that would be causing this problem?

Manually extracting the archive and point Viscosity to the config.conf file seems to work.

The generated import file looks like this:

Code: Select all

#viscosity dnssupport true
#viscosity name rps-5 VPN
#viscosity startonopen false
#viscosity dhcp true
remote openvpn-pool.removed 1194 udp
remote openvpn-pool.removed 443 tcp-client
server-poll-timeout 5
reneg-sec 0
pull
auth-user-pass
tls-client
ns-cert-type server
persist-key
ca ca.crt
dev tun
persist-tun
cert cert.crt
comp-lzo adaptive
nobind
key key.key
route-delay 2
resolv-retry infinite


After the import, if I export it from 1.7.4 it looks like this:

Code: Select all

#-- Config Auto Generated By Viscosity --#

#viscosity name rps-5 VPN
#viscosity startonopen false
#viscosity dhcp true
#viscosity dns automatic
remote openvpn-pool.removed 1194 udp
remote openvpn-pool.removed 443 tcp-client
pull
auth-user-pass
tls-client
ns-cert-type server
persist-key
ca ca.crt
dev tun
persist-tun
cert cert.crt
nobind
key key.key
server-poll-timeout 5
reneg-sec 0
comp-lzo adaptive
route-delay 2
resolv-retry infinite
dev-node {B23CB912-4156-4008-9C00-928470BA094F}
Hi rps,

There have been no changes for a while to importing. Does the import fail list any extra information? Are you able to replicate the problem by exporting the connection and reimporting it? If these visz files are hand made, are you able to replace the certificates with dummy information and email us one that does not work and we can take a look.

Regards,
Eric
2 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy