after I change to new version, The Tunnelblink can't work

73 views
Skip to first unread message

Qiaomei

unread,
Nov 1, 2014, 2:17:36 PM11/1/14
to tunnelbli...@googlegroups.com
Hope somebody can help me to solve it.. Thanks in advance.

The entire log message is 

2014-11-01 14:13:52 *Tunnelblick: OS X 10.9.5; Tunnelblick 3.4.1 (build 4054); prior version 3.4beta20 (build 3727)

2014-11-01 14:13:52 *Tunnelblick: Attempting connection with MPI_EVAN_macosx using shadow copy; Set nameserver = 1; monitoring connection

2014-11-01 14:13:52 *Tunnelblick: openvpnstart start MPI_EVAN_macosx.tblk 1337 1 0 1 0 16688 -ptADGNWradsgnw 2.3.4

2014-11-01 14:13:53 *Tunnelblick: openvpnstart log:

     Tunnelblick: 

     OpenVPN started successfully. Command used to start OpenVPN (one argument per displayed line):

     

          /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.3.4/openvpn

          --daemon

          --log

          /Library/Application Support/Tunnelblick/Logs/-SUsers-Sqiaomei_fu-SLibrary-SApplication Support-STunnelblick-SConfigurations-SMPI_EVAN_macosx.tblk-SContents-SResources-Sconfig.ovpn.1_0_1_0_16688.1337.openvpn.log

          --cd

          /Library/Application Support/Tunnelblick/Users/qiaomei_fu/MPI_EVAN_macosx.tblk/Contents/Resources

          --config

          /Library/Application Support/Tunnelblick/Users/qiaomei_fu/MPI_EVAN_macosx.tblk/Contents/Resources/config.ovpn

          --cd

          /Library/Application Support/Tunnelblick/Users/qiaomei_fu/MPI_EVAN_macosx.tblk/Contents/Resources

          --management

          127.0.0.1

          1337

          --management-query-passwords

          --management-hold

          --script-security

          2

          --up

          /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -f -ptADGNWradsgnw

          --down

          /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m -w -d -f -ptADGNWradsgnw


2014-11-01 14:13:52 *Tunnelblick: openvpnstart starting OpenVPN

2014-11-01 14:13:53 *Tunnelblick: Established communication with OpenVPN

2014-11-01 14:13:53 *Tunnelblick: Obtained VPN passphrase from the Keychain

2014-11-01 14:13:53 Multiple --up scripts defined.  The previously configured script is overridden.

2014-11-01 14:13:53 Multiple --down scripts defined.  The previously configured script is overridden.

2014-11-01 14:13:53 OpenVPN 2.3.4 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [PKCS11] [MH] [IPv6] built on Oct 15 2014

2014-11-01 14:13:53 library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08

2014-11-01 14:13:53 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2014-11-01 14:13:53 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2014-11-01 14:13:53 Error: private key password verification failed

2014-11-01 14:13:53 Exiting due to fatal error

2014-11-01 14:13:55 *Tunnelblick: No 'post-disconnect.sh' script to execute

2014-11-01 14:13:55 *Tunnelblick: Expected disconnection occurred.


Qiaomei Fu

unread,
Nov 1, 2014, 3:45:34 PM11/1/14
to tunnelbli...@googlegroups.com
Hello,
Based on the guide of  the other peoples questions, I change the Set DNS/WINS to “Do not set name server”
The Multiple —up complaint is gone

"2014-11-01 14:13:53 Multiple --up scripts defined.  The previously configured script is overridden.

2014-11-01 14:13:53 Multiple --down scripts defined.  The previously configured script is overridden."


But "this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2014-11-01 15:40:30 Error: private key password verification failed” is still existed.

The detail information is :

The  2014-11-01 15:40:29 *Tunnelblick: openvpnstart starting OpenVPN
2014-11-01 15:40:30 *Tunnelblick: Established communication with OpenVPN
2014-11-01 15:40:30 *Tunnelblick: Obtained VPN passphrase from the Keychain
2014-11-01 15:40:30 OpenVPN 2.3.4 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [PKCS11] [MH] [IPv6] built on Oct 15 2014
2014-11-01 15:40:30 library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08
2014-11-01 15:40:30 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2014-11-01 15:40:30 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2014-11-01 15:40:30 Error: private key password verification failed
2014-11-01 15:40:30 Exiting due to fatal error
2014-11-01 15:40:31 *Tunnelblick: No 'post-disconnect.sh' script to execute
2014-11-01 15:40:32 *Tunnelblick: Expected disconnection occurred

Best,
Q

--
You received this message because you are subscribed to a topic in the Google Groups "tunnelblick-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tunnelblick-discuss/QQq0SMcOViM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tunnelblick-dis...@googlegroups.com.
Visit this group at http://groups.google.com/group/tunnelblick-discuss.
For more options, visit https://groups.google.com/d/optout.

jkbull...gmail.com

unread,
Nov 1, 2014, 4:37:17 PM11/1/14
to tunnelbli...@googlegroups.com, qiao...@gmail.com
The message about "this configuration may cache passwords in memory -- use the auth-nocache option to prevent this" is normal and can be ignored. Or you can do as they suggest and add the "auth-nocache" option.

The real problem is that the private key (passphrase) is apparently invalid. Assuming it was read from the Keychain (you didn't provide the "diagnostic info", so I can't tell), delete the existing credentials from the Keychain as follows:
  1. Open the VPN Details… window.
  2. Click on "MPI_EVAN_macosx" in the list on the left so it is selected
  3. Click on the little "gear" button at the bottom of the list
  4. Click on "Delete Configuration's Credentials in Keychain…"
When you try to connect, you will be asked for the passphrase. Provide it and set the "Save in Keychain" checkbox if you wish.

Tunnelblick should ask you for the passphrase if the one stored in the Keychain isn't accepted, but perhaps there's a bug.

If you have further problems, please follow the instructions in Read Before You Post.
Reply all
Reply to author
Forward
0 new messages