Won't progress past "Making TCP connection"

6,411 views
Skip to first unread message

ron.me...@gmail.com

unread,
Sep 29, 2014, 9:08:10 AM9/29/14
to tunnelbli...@googlegroups.com
Hi
Tunnelblick was working successfully till recently.  
After clicking Connect, the lettering changes to yellow "Making TCP connection" (with a timer increasing) and icon has three black dots in sequence
However, the lettering now does not change to green (as it did) and the icon settle.
The Making TCP connection (in yellow) continues with no change.

This is a copy of the Diagnostic Info:

*Tunnelblick: OS X 10.9.5; Tunnelblick 3.4beta36 (build 3945); prior version 3.4beta34 (build 3935); Admin user

"Sanitized" condensed configuration file for /Library/Application Support/Tunnelblick/Shared/178.62.15.177-direct.tblk:

client
remote 178.62.15.177 636
dev tun
proto tcp
cipher AES-256-CBC
auth SHA256
resolv-retry infinite
nobind
persist-key
persist-tun
ns-cert-type server
comp-lzo
key-direction 1
verb 3
route 178.62.15.177 255.255.255.255 net_gateway
<ca>
[Security-related line(s) omitted]
</ca>
<cert>
[Security-related line(s) omitted]
</cert>
<key>
[Security-related line(s) omitted]
</key>
<tls-auth>
[Security-related line(s) omitted]
</tls-auth>


================================================================================

"Sanitized" full configuration file

client
remote 178.62.15.177 636
dev tun
proto tcp
cipher AES-256-CBC
auth SHA256
resolv-retry infinite
nobind
persist-key
persist-tun
ns-cert-type server
comp-lzo
key-direction 1
verb 3
route 178.62.15.177 255.255.255.255 net_gateway

<ca>
 [Security-related line(s) omitted]
</ca>

<cert>
 [Security-related line(s) omitted]
</cert>

<key>
 [Security-related line(s) omitted]
</key>

<tls-auth>
 [Security-related line(s) omitted]
</tls-auth>



================================================================================

Cannot list unusual files in 178.62.15.177-direct.tblk; not a private configuration

================================================================================

Configuration preferences:

autoConnect = 1
-onSystemStart = 0
-lastConnectionSucceeded = 0

================================================================================

Wildcard preferences:


================================================================================

Program preferences:

launchAtNextLogin = 1
notOKToCheckThatIPAddressDidNotChangeAfterConnection = 0
askedUserIfOKToCheckThatIPAddressDidNotChangeAfterConnection = 1
tunnelblickVersionHistory = (
    "3.4beta36 (build 3945)",
    "3.4beta34 (build 3935)",
    "3.4beta30 (build 3893)"
)
lastLaunchTime = 433687771.183685
showConnectedDurations = 1
connectionWindowDisplayCriteria = showWhenConnecting
maxLogDisplaySize = 102400
lastConnectedDisplayName = 178.62.15.177-direct
installationUID (not shown)
keyboardShortcutIndex = 1
updateCheckAutomatically = 1
updateSendProfileInfo = 1
NSWindow Frame SettingsSheetWindow = 337 309 829 424 0 0 1440 878 
NSWindow Frame ConnectingWindow = 525 519 389 187 0 0 1440 878 
detailsWindowFrameVersion = 3945
detailsWindowFrame = {{297, 299}, {920, 468}}
detailsWindowLeftFrame = {{0, 0}, {164, 350}}
leftNavSelectedDisplayName = 178.62.15.177-direct
haveDealtWithSparkle1dot5b6 = 1
haveDealtWithOldTunTapPreferences = 1
haveDealtWithOldLoginItem = 1
SUEnableAutomaticChecks = 1
SUScheduledCheckInterval = 86400
SUSendProfileInfo = 1
SULastCheckTime = 2014-09-29 12:49:30 +0000
SULastProfileSubmissionDate = 2014-09-28 19:43:05 +0000
SUHasLaunchedBefore = 1
WebKitDefaultFontSize = 11
WebKitStandardFont = Lucida Grande

================================================================================

Tunnelblick Log:

2014-09-29 13:49:30 *Tunnelblick: OS X 10.9.5; Tunnelblick 3.4beta36 (build 3945); prior version 3.4beta34 (build 3935)
2014-09-29 13:49:30 *Tunnelblick: Attempting connection with 178.62.15.177-direct; Set nameserver = 1; monitoring connection
2014-09-29 13:49:30 *Tunnelblick: openvpnstart start 178.62.15.177-direct.tblk 1337 1 0 3 0 16689 -ptADGNWradsgnw 2.2.1
2014-09-29 13:49:30 *Tunnelblick: openvpnstart starting OpenVPN
2014-09-29 13:49:31 *Tunnelblick: openvpnstart log:
     Tunnelblick: Loading tun-signed.kext
     Tunnelblick: 
     OpenVPN started successfully. Command used to start OpenVPN (one argument per displayed line):
     
          /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn
          --daemon
          --log
          /Library/Application Support/Tunnelblick/Logs/-SLibrary-SApplication Support-STunnelblick-SShared-S178.62.15.177--direct.tblk-SContents-SResources-Sconfig.ovpn.1_0_3_0_16689.1337.openvpn.log
          --cd
          /Library/Application Support/Tunnelblick/Shared/178.62.15.177-direct.tblk/Contents/Resources
          --config
          /Library/Application Support/Tunnelblick/Shared/178.62.15.177-direct.tblk/Contents/Resources/config.ovpn
          --cd
          /Library/Application Support/Tunnelblick/Shared/178.62.15.177-direct.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-09-29 13:49:31 *Tunnelblick: Established communication with OpenVPN
2014-09-29 13:49:31 OpenVPN 2.2.1 i386-apple-darwin [SSL] [LZO2] [PKCS11] [eurephia] built on Sep  1 2014
2014-09-29 13:49:31 MANAGEMENT: TCP Socket listening on 127.0.0.1:1337
2014-09-29 13:49:31 Need hold release from management interface, waiting...
2014-09-29 13:49:31 MANAGEMENT: Client connected from 127.0.0.1:1337
2014-09-29 13:49:31 MANAGEMENT: CMD 'pid'
2014-09-29 13:49:31 MANAGEMENT: CMD 'state on'
2014-09-29 13:49:31 MANAGEMENT: CMD 'state'
2014-09-29 13:49:31 MANAGEMENT: CMD 'bytecount 1'
2014-09-29 13:49:31 MANAGEMENT: CMD 'hold release'
2014-09-29 13:49:31 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2014-09-29 13:49:31 Control Channel Authentication: tls-auth using INLINE static key file
2014-09-29 13:49:31 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2014-09-29 13:49:31 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2014-09-29 13:49:31 LZO compression initialized
2014-09-29 13:49:31 Control Channel MTU parms [ L:1572 D:180 EF:80 EB:0 ET:0 EL:0 ]
2014-09-29 13:49:31 Socket Buffers: R=[131072->65536] S=[131072->65536]
2014-09-29 13:49:31 Data Channel MTU parms [ L:1572 D:1450 EF:72 EB:135 ET:0 EL:0 AF:3/1 ]
2014-09-29 13:49:31 Local Options hash (VER=V4): '504bba81'
2014-09-29 13:49:31 Expected Remote Options hash (VER=V4): '165db97f'
2014-09-29 13:49:31 Attempting to establish TCP connection with 178.62.15.177:636 [nonblock]
2014-09-29 13:49:31 MANAGEMENT: >STATE:1411994971,TCP_CONNECT,,,
2014-09-29 13:49:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:49:46 MANAGEMENT: >STATE:1411994986,TCP_CONNECT,,,
2014-09-29 13:49:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:50:01 MANAGEMENT: >STATE:1411995001,TCP_CONNECT,,,
2014-09-29 13:50:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:50:16 MANAGEMENT: >STATE:1411995016,TCP_CONNECT,,,
2014-09-29 13:50:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:50:31 MANAGEMENT: >STATE:1411995031,TCP_CONNECT,,,
2014-09-29 13:50:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:50:46 MANAGEMENT: >STATE:1411995046,TCP_CONNECT,,,
2014-09-29 13:50:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:51:01 MANAGEMENT: >STATE:1411995061,TCP_CONNECT,,,
2014-09-29 13:51:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:51:16 MANAGEMENT: >STATE:1411995076,TCP_CONNECT,,,
2014-09-29 13:51:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:51:31 MANAGEMENT: >STATE:1411995091,TCP_CONNECT,,,
2014-09-29 13:51:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:51:46 MANAGEMENT: >STATE:1411995106,TCP_CONNECT,,,
2014-09-29 13:51:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:52:01 MANAGEMENT: >STATE:1411995121,TCP_CONNECT,,,
2014-09-29 13:52:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:52:16 MANAGEMENT: >STATE:1411995136,TCP_CONNECT,,,
2014-09-29 13:52:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:52:31 MANAGEMENT: >STATE:1411995151,TCP_CONNECT,,,
2014-09-29 13:52:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:52:46 MANAGEMENT: >STATE:1411995166,TCP_CONNECT,,,
2014-09-29 13:52:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:53:01 MANAGEMENT: >STATE:1411995181,TCP_CONNECT,,,
2014-09-29 13:53:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:53:16 MANAGEMENT: >STATE:1411995196,TCP_CONNECT,,,
2014-09-29 13:53:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:53:31 MANAGEMENT: >STATE:1411995211,TCP_CONNECT,,,
2014-09-29 13:53:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:53:46 MANAGEMENT: >STATE:1411995226,TCP_CONNECT,,,
2014-09-29 13:53:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:54:01 MANAGEMENT: >STATE:1411995241,TCP_CONNECT,,,
2014-09-29 13:54:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:54:16 MANAGEMENT: >STATE:1411995256,TCP_CONNECT,,,
2014-09-29 13:54:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:54:31 MANAGEMENT: >STATE:1411995271,TCP_CONNECT,,,
2014-09-29 13:54:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:54:46 MANAGEMENT: >STATE:1411995286,TCP_CONNECT,,,
2014-09-29 13:54:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:55:01 MANAGEMENT: >STATE:1411995301,TCP_CONNECT,,,
2014-09-29 13:55:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:55:16 MANAGEMENT: >STATE:1411995316,TCP_CONNECT,,,
2014-09-29 13:55:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:55:31 MANAGEMENT: >STATE:1411995331,TCP_CONNECT,,,
2014-09-29 13:55:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:55:46 MANAGEMENT: >STATE:1411995346,TCP_CONNECT,,,
2014-09-29 13:55:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:56:01 MANAGEMENT: >STATE:1411995361,TCP_CONNECT,,,
2014-09-29 13:56:11 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:56:16 MANAGEMENT: >STATE:1411995376,TCP_CONNECT,,,
2014-09-29 13:56:26 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:56:31 MANAGEMENT: >STATE:1411995391,TCP_CONNECT,,,
2014-09-29 13:56:41 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:56:46 MANAGEMENT: >STATE:1411995406,TCP_CONNECT,,,
2014-09-29 13:56:56 TCP: connect to 178.62.15.177:636 failed, will try again in 5 seconds: Operation timed out
2014-09-29 13:57:01 MANAGEMENT: >STATE:1411995421,TCP_CONNECT,,,
2014-09-29 13:57:08 *Tunnelblick: Disconnecting; VPN Details… window disconnect button pressed
2014-09-29 13:57:08 *Tunnelblick: Disconnecting using 'kill'
2014-09-29 13:57:08 TCP/UDP: Closing socket
2014-09-29 13:57:08 SIGTERM[hard,init_instance] received, process exiting
2014-09-29 13:57:08 MANAGEMENT: >STATE:1411995428,EXITING,init_instance,,
2014-09-29 13:57:08 *Tunnelblick: No 'post-disconnect.sh' script to execute
2014-09-29 13:57:08 *Tunnelblick: Expected disconnection occurred.

================================================================================

Console Log:

2014-09-29 13:49:14 Tunnelblick[5483] applicationShouldTerminate: termination because of Quit; delayed until 'shutdownTunnelblick' finishes
2014-09-29 13:49:14 Tunnelblick[5483] Finished shutting down Tunnelblick; allowing termination
2014-09-29 13:49:30 Tunnelblick[8226] Set program update feedURL to https://www.tunnelblick.net/appcast-b.rss
2014-09-29 13:49:31 Tunnelblick[8226] DEBUG: Updater: systemVersion 10.9.5 satisfies minimumSystemVersion 10.4.0
2014-09-29 13:49:31 Tunnelblick[8226] DEBUG: Updater: systemVersion 10.9.5 satisfies minimumSystemVersion 10.4.0
2014-09-29 13:49:31 Tunnelblick[8226] Ignoring attempt to 'tryToHookup' for '178.62.15.177-direct' -- already using port number 1337

================================================================================

Non-Apple kexts that are loaded:

Index Refs Address            Size       Wired      Name (Version) <Linked Against>
  108    0 0xffffff7f807e7000 0x7000     0x7000     com.sophos.nke.swi (9.1.50) <4 3 1>
  129    0 0xffffff7f807c1000 0x5000     0x5000     com.sophos.kext.sav (9.1.55) <5 4 1>



Can anyone help?
Many thanks
R

jkbull...gmail.com

unread,
Sep 29, 2014, 9:29:39 AM9/29/14
to tunnelbli...@googlegroups.com, ron.me...@gmail.com
Thanks for providing the diagnostic info.

This is unlikely to be a problem or bug with the Tunnelblick or OpenVPN software.

The problem is that the OpenVPN server you are trying to connect to is not responding, or your computer's request to it is not reaching it, or its response is not reaching your computer.

There are many possible reasons, among them:
  • The OpenVPN server is down
  • OpenVPN on the server has crashed
  • Something between your computer and the OpenVPN server is purposefully blocking the traffic (examples: your Internet Service Provider or the Great Firewall of China)
  • The OpenVPN server cannot be reached for some other reason (network equipment failure, incorrect routing information, etc.)
You need to contact whoever is providing the OpenVPN server.


The only other thing I can suggest is that you try using OpenVPN version 2.3.4. It is unlikely to work, but easy to try:
  1. Launch Tunnelblick
  2. Click on the Tunnelblick icon at the top of the display
  3. Click on "VPN Details…"
  4. In the new window that appears
    1. Select your configuration in the list on the left
    2. Select "2.3.4" from the list to the right of "OpenVPN version:" -- it is probably currently set to "Default (2.2.1)"
  5. Try to connect (you can close the "VPN Details…" window at any time)
If that fixes the problem, please report that back -- it would be very interesting. You should also un-do the change and see if you can connect -- it may be that the OpenVPN server was down and -- by coincidence -- came back up by the time you made the change.
Reply all
Reply to author
Forward
0 new messages