Skip to content
macOS 10.15 + 1.7.17b4 — connection stuck in connecting mode
Got a problem with Viscosity or need help? Ask here!
Hello. After updating to the beta of new Mac OS version, Viscosity stopped connecting. So I updated Viscosity to the last version 1.7.17b4 (from version 1.6.7). Here are the logs (no error or warning messages):
Here are the connection settings (The two most important tabs, as I understand it):
Code: Select all
And it's all in the loop. 2019-07-12 23:22:21: Viscosity Mac 1.7.17b4 (1495)
2019-07-12 23:22:21: Viscosity OpenVPN Engine Started
2019-07-12 23:22:21: Running on macOS 10.15.0
2019-07-12 23:22:21: ---------
2019-07-12 23:22:21: State changed to Connecting
2019-07-12 23:22:21: Checking reachability status of connection...
2019-07-12 23:22:21: Connection is reachable. Starting connection attempt.
2019-07-12 23:22:22: OpenVPN 2.4.7 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Jul 8 2019
2019-07-12 23:22:22: library versions: OpenSSL 1.0.2s 28 May 2019, LZO 2.10
2019-07-12 23:22:23: PKCS#11: Adding PKCS#11 provider '/Library/Aktiv Co/Rutoken ECP/lib/librtpkcs11ecp.dylib'
2019-07-12 23:22:23: State changed to Disconnected
2019-07-12 23:22:23: Delaying connection reconnect attempt by 5 seconds
Here are the connection settings (The two most important tabs, as I understand it):
Hi kefiijrw,
It appears the PKCS#11 driver you're using ("/Library/Aktiv Co/Rutoken ECP/lib/librtpkcs11ecp.dylib") is crashing and killing the OpenVPN process. This likely means the driver is not compatible with macOS 10.15 (or a macOS 10.15 beta bug could be crashing the driver). You'll have to get in touch with the manufacture of the driver for more information.
Cheers,
James
It appears the PKCS#11 driver you're using ("/Library/Aktiv Co/Rutoken ECP/lib/librtpkcs11ecp.dylib") is crashing and killing the OpenVPN process. This likely means the driver is not compatible with macOS 10.15 (or a macOS 10.15 beta bug could be crashing the driver). You'll have to get in touch with the manufacture of the driver for more information.
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
2 posts
Page 1 of 1