Jump to content
Not connected, Your IP: 34.207.82.217
Sign in to follow this  
lambrinoul

Unable to connect - Tunnelblick & Viscosity

Recommended Posts

In the last week or two I am experiencing problems in connecting to airvpn.

 

I have been using viscosity without problems but It stopped connecting. I tried with tunnelblick and I receive the same error :

 

 

Tunnelblick was unable to start OpenVPN to connect AirVPN_Europe_UDP-443. For details, see the log in the VPN Details… window

 

Contents of the openvpnstart log:

*Tunnelblick: openvpnstart log:

     Tunnelblick: Loading tun-signed.kext

     Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).

     Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).

     Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).

     Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).

     Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8).

     Tunnelblick: Unable to load net.tunnelblick.tun and/or net.tunnelblick.tap kexts in 5 tries. Status = 71

 

Share this post


Link to post

The same problem as with tunnelblick. 

 

 

 

The OpenVPN subsystem could not be started. Please see the log section (the third icon) in the Details window for more information.

 

Sep 18 12:52:47: Viscosity Mac 1.5.1 (1232)
Sep 18 12:52:47: Viscosity OpenVPN Engine Started
Sep 18 12:52:47: Running on Mac OS X 10.9.4
Sep 18 12:52:47: ---------
Sep 18 12:52:47: Checking reachability status of connection...
Sep 18 12:52:47: Connection is reachable. Starting connection attempt.
 
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Make sure Viscosity is not running under a File Vault protected location (put Viscosity in the Applications folder).
- Make sure the configuration is valid. Check the connection settings for the connection using Viscosity and make sure all settings are correct.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...