Viscosity 1.7.3 won't connect in Mac Sierra

Got a problem with Viscosity or need help? Ask here!

Prisca22

Posts: 5
Joined: Tue Jul 18, 2017 12:09 am

Post by Prisca22 » Tue Jul 18, 2017 12:14 am
Hi,
Since I updated to Mac Sierra, Viscosity won't connect. It keeps seeking for a connection but it doesn't go through. I can't make a copy of the log because it keeps updating constantly. Any ideas?
Thanks for any help.

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Tue Jul 18, 2017 2:59 pm
Hi Prisca22,

The log is rapidly filling with errors you may like to try disconnecting your connection from Viscosity's main menu so the connection attempt is aborted, and then view the log:
http://www.sparklabs.com/support/kb/art ... envpn-log/

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

Prisca22

Posts: 5
Joined: Tue Jul 18, 2017 12:09 am

Post by Prisca22 » Wed Jul 19, 2017 8:02 pm
Thank you for your suggestion. I didn't know how to do that. I have no idea how to interpret the result. Can you help? Here is the log:

2017-07-19 11:56:58: State changed to Connexion en cours
2017-07-19 11:56:58: Vérification du statut d'accessibilité de la connexion ...
2017-07-19 11:56:58: La connexion est accessible. Tentative de démarrage de la connexion.
2017-07-19 11:56:59: OpenVPN 2.4.3 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Jun 21 2017
2017-07-19 11:56:59: library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.09
2017-07-19 11:56:59: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
2017-07-19 11:56:59: TCP/UDP: Preserving recently used remote address: [AF_INET]94.242.209.90:1194
2017-07-19 11:56:59: Attempting to establish TCP connection with [AF_INET]94.242.209.90:1194 [nonblock]
2017-07-19 11:57:00: TCP connection established with [AF_INET]94.242.209.90:1194
2017-07-19 11:57:00: TCP_CLIENT link local: (not bound)
2017-07-19 11:57:00: TCP_CLIENT link remote: [AF_INET]94.242.209.90:1194
2017-07-19 11:57:00: State changed to Authentification en cours
2017-07-19 11:57:00: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2017-07-19 11:57:00: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1544', remote='link-mtu 1604'
2017-07-19 11:57:00: WARNING: 'cipher' is used inconsistently, local='cipher BF-CBC', remote='cipher AES-256-CBC'
2017-07-19 11:57:00: WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth SHA512'
2017-07-19 11:57:00: WARNING: 'keysize' is used inconsistently, local='keysize 128', remote='keysize 256'
2017-07-19 11:57:00: [server] Peer Connection Initiated with [AF_INET]94.242.209.90:1194
2017-07-19 11:57:02: WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
2017-07-19 11:57:02: WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
2017-07-19 11:57:02: WARNING: cipher with small block size in use, reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
2017-07-19 11:57:02: Opening utun (connect(AF_SYS_CONTROL)): Resource busy
2017-07-19 11:57:02: Opened utun device utun1
2017-07-19 11:57:02: do_ifconfig, tt->did_ifconfig_ipv6_setup=0
2017-07-19 11:57:02: /sbin/ifconfig utun1 delete
2017-07-19 11:57:02: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2017-07-19 11:57:02: /sbin/ifconfig utun1

Prisca22

Posts: 5
Joined: Tue Jul 18, 2017 12:09 am

Post by Prisca22 » Thu Jul 20, 2017 4:06 am
Could somebody help, please? :mrgreen:

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Thu Jul 20, 2017 1:12 pm
Hi Prisca22,

There appear to be a significant number of incompatibilities between the VPN client configuration and the server's configuration that'll prevent your connection from working:
Code: Select all
2017-07-19 11:57:00: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2017-07-19 11:57:00: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1544', remote='link-mtu 1604'
2017-07-19 11:57:00: WARNING: 'cipher' is used inconsistently, local='cipher BF-CBC', remote='cipher AES-256-CBC'
2017-07-19 11:57:00: WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth SHA512'
2017-07-19 11:57:00: WARNING: 'keysize' is used inconsistently, local='keysize 128', remote='keysize 256'
2017-07-19 11:57:00: [server] Peer Connection Initiated with [AF_INET]94.242.209.90:1194
You'll need to get in touch with your VPN Provider and seek an updated configuration file to import into Viscosity that is correctly configured for the server you're connecting to. Please see:
http://www.sparklabs.com/support/kb/art ... ovider-is/

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

Prisca22

Posts: 5
Joined: Tue Jul 18, 2017 12:09 am

Post by Prisca22 » Sat Jul 22, 2017 9:14 pm
Thank you. I will do that.

Prisca22

Posts: 5
Joined: Tue Jul 18, 2017 12:09 am

Post by Prisca22 » Sun Jul 23, 2017 4:09 am
Hi, I imported a new connection from my seedbox provider and it's working now. Thanks for your help. :mrgreen:
7 posts Page 1 of 1