[Solved] Problem converting OpenVPN configuration to Tunnelblick VPN Configuration

[jkbull...gmail.com]

A user reported a problem which was found to be caused by a backslash in the "ca" option of a configuration file, e.g.

ca /Users/name/Library/Application\ Support/Tunnelblick/Configurations/ca.crt

Tunnelblick does not allow backslashes in this option (due to either misreading the OpenVPN man page, or an error on it).

As a workaround, remove the backslash:

ca /Users/name/Library/Application Support/Tunnelblick/Configurations/ca.crt

or 

ca "/Users/name/Library/Application Support/Tunnelblick/Configurations/ca.crt"

or (if the configuration file and the ca.crt files are in the same folder), remove the path information completely:

ca ca.crt

I have committed a change (r2298) to the Tunnelblick source code to allow backslashes; the fix will be in the next release.

[jkbull...gmail.com]

Another problem that the converter is not able to handle is an invalid OpenVPN configuration file -- for example, one which refers to certificate or key files that do not exist.

For example, you have a configuration file that contains a line like:

ca ca.crt

and you move or copy that configuration file into a subfolder but do not also move or copy the "ca.crt" file into the same subfolder. In that situation, neither OpenVPN nor Tunnelblick will be able to find the "ca.crt" file, because they will both be looking into the subfolder. So OpenVPN will not allow you to connect using that configuration, and Tunnelblick will not be able to convert it to a Tunnelblick VPN Conversion.

The workaround is to move any such invalid configurations out of the "Configurations" folder (to the Desktop, for example), and retry the conversion with only valid configuration files in Configurations or its subfolders.

[jkbull...gmail.com]

Tunnelblick 3.3beta50 is available for download.

It fixes several problems relating to converting OpenVPN configurations to Tunnelblick VPN Configurations, including the problem described in the first post of this thread (backslashes in paths).

There is not anything in the new release to help with the problem described in the second post. That must be fixed as described in that post.

On Friday, May 10, 2013 11:23:38 AM UTC-4, jkbull...gmail.com wrote: