Tunnelblick: openvpnstart status #242: Error: OpenVPN returned with status 1

[GoogleCodeExporter]

What steps will reproduce the problem?
unable to connect after click on connect button. (First time installed)

What is the expected output? What do you see instead?
log list as below:
*Tunnelblick: Attempting connection with openvpn.conf; Set nameserver = 1;
monitoring connection
*Tunnelblick: openvpnstart status #242: Error: OpenVPN returned with status
1. Possible error in configuration file. See "All Messages" in Console for
details

I am not sure the way I check for the detailed in console is correct or
not, following is the detail while I tried to execute tunnelblick in
console mode

(kernel) Kext foo.tap not found for unload request.
Failed to unload foo.tap - (libkern/kext) not found.
(kernel) Kext foo.tun not found for unload request.
Failed to unload foo.tun - (libkern/kext) not found.
Error: Unable to unload tun and tap kexts. Status = 3
Hung-Shawnteki-MacBook-Pro:macos shawn$ ./tunnelblick

What version of Tunnelblick are you using? On what version of OS X? PPC or
Intel?
I am using 3.0b24 and Snow leopard and couldn't google any information
about regarding what cause status #242

Any kindly help will be highly appreciated..   please..

Original issue reported on code.google.com by mosi1...@gmail.com on 17 Jan 2010 at 2:42

[GoogleCodeExporter]

The error #242 is an openvpnstart (part of Tunnelblick) error code meaning that 
OpenVPN itself returned an 
error status (of 1 in this case; success is code = 0). Usually the problem is 
an error in the OpenVPN 
configuration file, hence the message "*Tunnelblick: openvpnstart status #242: 
Error: OpenVPN returned with 
status 1. Possible error in configuration file. See "All Messages" in Console 
for details

To check the messages in the console, start the "Console.app", which is in the 
Utilities subfolder of the 
Applications folder. If you don't see a log list on the left, click "Show Log 
List" button at the top left. Then 
click on "All messages" (usually the second item in the left column). Then 
click the "Clear Display" button. 
Then try to connect. When you get the error, go to the Console window. A bunch 
of messages will appear on 
the right side of the Console window. They show the OpenVPN output (and may 
have various irrelevant system 
messages mixed in, too).

If you can see the problem and correct it from there, please reply so we can 
close out this Issue. If you can't 
figure it out, select all of the messages (with Command-A), and copy them (with 
Command-C), then paste 
them into a reply. You should look through them and obfuscate the IP address of 
your server, and send the 
reply.

Original comment by jkbull...@gmail.com on 17 Jan 2010 at 6:28

[GoogleCodeExporter]

Thanks. After checking the log in console, I found the source of the problem is 
from
the location of key files. Some of the origional information I google out is 
that
default key files folder is under /home/user/resources/application
support/tunnelbrick. Because there is a space between the folder name 
"application
support", openvpn.conf not read complete key files folder location.
The problem is solved after I put most of the key file to /home/user/ and 
re-config
the openvpn.conf.
Many thanks again.

Original comment by mosi1...@gmail.com on 17 Jan 2010 at 9:32

[GoogleCodeExporter]

If you put your key and cert files in the same folder as the configuration 
file, you don't use a path to refer to them, you 
just use the file name. For example, if your key file is in the same folder as 
the configuration file, and is named 
"abcde,key", put

     key abcde.key

in the configuration file. In effect, the "current working directory" when 
OpenVPN parses the configuration file is the 
folder that the configuration file is in.

(Note that the above won't necessarily work with deployed versions of 
Tunnelblick because under certain 
circumstances Tunnelblick sets the "current working directory" for OpenVPN to a 
different directory; see the Deploying 
Tunnelblick wiki for details.)

Original comment by jkbull...@gmail.com on 17 Jan 2010 at 9:46

• Changed state: Invalid

[GoogleCodeExporter]

I have the same problem. I use Mac OS X and Tunnelblik 3.1.6 (build 2190.2392) 
and i correctly set the path to my key in the same directory of the config file.

I think that the problem was to set-up the TUN device to established the 
connection and not the key path

My Console Log:

20/02/11 11.08.18   [0x0-0x45045].com.openvpn.tunnelblick[880]  2011-02-20 
11:08:18.819 installer[887:e07] Tunnelblick Installer: Changed ownership to 0:0 
on /Library/Application Support/Tunnelblick/Shared/Server.tblk and its contents

20/02/11 11.08.18   [0x0-0x45045].com.openvpn.tunnelblick[880]  2011-02-20 
11:08:18.822 installer[887:e07] Tunnelblick Installer: Changed permissions to 
0600 on /Library/Application 
Support/Tunnelblick/Shared/Server.tblk/Contents/Resources/unicondor.key

20/02/11 11.08.18   Tunnelblick[880]    Copied configuration file 
/var/folders/tt/ttntfhLYERCLPhjoWfmvZU+++TI/-Tmp-/TunnelblickTemporaryDotTblk-kX
UjOU/Server.tblk to /Library/Application Support/Tunnelblick/Shared/Server.tblk 
and secured the copy

20/02/11 11.08.23   kernel  Kext foo.tun not found for unload request.

Original comment by flavio.pace on 20 Feb 2011 at 10:14

[GoogleCodeExporter]

Please post your configuration file and the complete log from Tunnelblick's 
"Details…" window.

X out the IP address or URL of your server and the contents (but not the 
filename) of any keys.

Original comment by jkbull...@gmail.com on 20 Feb 2011 at 12:10

[GoogleCodeExporter]

I have a similar problem.  New to Tunnelblick and having difficulty configuring 
setup so that it works.  The error I get is also #242.  The details reads: 
2011-02-21 00:27:36 *Tunnelblick: Attempting connection with riseup; Set 
nameserver = 1; monitoring connection
2011-02-21 00:27:36 *Tunnelblick: 
/Applications/Tunnelblick.app/Contents/Resources/openvpnstart start riseup.ovpn 
1337 1 0 0 0 51
2011-02-21 00:27:36 *Tunnelblick: openvpnstart status #242: Error: OpenVPN 
returned with status 1. Possible error in configuration file. See "All 
Messages" in Console for details

My config file reads:
client
dev tun
auth-user-pass
remote vpn.XXX.net 1194
ca /Users/username/Library/XXX.pem

any ideas?

Original comment by nate.fra...@gmail.com on 21 Feb 2011 at 5:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@nate.fra... --

Please post the *complete* log from Tunnelblick's "Details…" window.

What was in the Console log? See my comment 1 at
http://code.google.com/p/tunnelblick/issues/detail?id=141#c1

I can't remember if you are allowed to have a full path in the "ca" line. If 
not, that may be the problem. To get around it, try making a Tunnelblick VPN 
Configuration

To make  a Tunnelblick VPN Configuration (brief version):
1. Copy the config file and the XXX.pem file in a (new) folder on your Desktop
2. Change the "ca" line in the config file to "ca XXX.pem" (i.e., remove all 
path info)
3. Name the folder "ZZZ.tblk", where ZZZ is the name you want the configuration 
to have. (The folder's icon will change.)
4. Launch Tunnelblick, but do not connect or anything.
5. Double-click the folder to install the configuration.

Full instructions for making a Tunnelblick VPN Configuration are at
http://code.google.com/p/tunnelblick/wiki/wPkgs#Creation

Original comment by jkbull...@gmail.com on 21 Feb 2011 at 12:00

[GoogleCodeExporter]

unicondor@MacBook:flavio.tblk> ls
config.ovpn   unicondor.key

unicondor@MacBook:flavio.tblk> cat config.ovpn 
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
;client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote 192.168.1.60 1194
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
;ca ca.crt
;cert client.crt
key unicondor.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server".  This is an
# important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server".  The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

if i use this configuration on my Slack, he works fine..

Original comment by flavio.pace on 21 Feb 2011 at 12:42

[GoogleCodeExporter]

My Details in Tunnelblick

2011-02-21 13:47:48 *Tunnelblick: Attempting connection with Server; Set 
nameserver = 1; monitoring connection
2011-02-21 13:47:48 *Tunnelblick: 
/Applications/Tunnelblick.app/Contents/Resources/openvpnstart start Server.tblk 
1337 1 0 3 0 49
2011-02-21 13:47:48 *Tunnelblick: openvpnstart status #242: Error: OpenVPN 
returned with status 1. Possible error in configuration file. See "All 
Messages" in Console for details

Original comment by flavio.pace on 21 Feb 2011 at 12:50

[GoogleCodeExporter]

@flavio -

Thanks.

1. It is unusual to have the "client" line commented out -- this is a client, 
not a server, right? So try taking out the semicolon (";") so the line just 
looks like:
     client

2. It is unusual for the VPN server to be located on a private network, as is 
indicated by:
     remote 192.168.1.60 1194
Is that correct?

If it still doesn't work, please post the __complete__ log from Tunnelblick's 
"Details…" window. (Quit and start Tunnelblick again, try to connect, then 
get the __complete__ log.)

Good luck!

Original comment by jkbull...@gmail.com on 21 Feb 2011 at 12:55

[GoogleCodeExporter]

Thanks for replace... i find the "stupid" problem on my configuration file.

My Tunnel it's Point-To-Point with a secret static key 'unicondor.key' , so i 
simply replace

"key" with "secret" in configuration 

secret unicondor.key

Now He works fine... thanks a lot for the replace :D

Flavio

Original comment by flavio.pace on 24 Feb 2011 at 1:37

[GoogleCodeExporter]

I have same problem, but more painful since there's no log message in the 
Console reported from Tunnelblick while it is attempting to connect.
I am sure that my Tunnelblick installation *is* capable to do logging - I can 
see some messages when editing configuration file for example (logs about 
permission changes).
I tried to set verbobse level to 15 in the .ovpn config file, but this had no 
effect on connection attempt. OpenVPN seems to mystify me. How can I force it 
to trace log messages into Console?

Original comment by obr...@gmail.com on 7 Aug 2011 at 5:08

[GoogleCodeExporter]

What exactly do you mean by "same problem"?

Please post your configuration file and the complete log from Tunnelblick's 
"Details…" window. X out the IP address or URL of your server and the 
contents (but not the filename) of any keys.

There are some circumstances in which OpenVPN tellsTunnelblick that there was 
an error in the configuration file, but does not put an error message to the 
console. The "verb" level in the OpenVPN configuration file does not affect 
this. If I recall correctly, such things as unknown control characters will 
cause this problem. Try searching the Tunnelblick Discussion Group [1] for 
threads about this.

[1] https://groups.google.com/forum/#!forum/tunnelblick-discuss

Original comment by jkbull...@gmail.com on 7 Aug 2011 at 5:21

[GoogleCodeExporter]

In my case, if i click Connect, a message box appears:

"Tunnelblick was unable to start OpenVPN to connect private, For details, see 
the OpenVPN log in the Details... window"

* See below on my default config file contents (the file was copied from 
Windows7 where OpenVPN installation is working OK with it). I also used that 
wizard in Tunnelblick to create sample config file for me, and adjusted all 
options there according to my default config file - but it produces same result 
in Details... window, no message in Console.

client
dev tun
proto udp
remote xxx.xxx.xxx.xxx 1194
resolv-retry infinite
nobind
user xxxxxx
group nogroup
persist-key
persist-tun
auth-user-pass
ca cacert.crt
cert private.crt
key private.key
comp-lzo
verb 15
route-method exe
route-delay 2

[Details...] window contents:

2011-08-07 19:26:58 *Tunnelblick: OS X 10.5.8; Tunnelblick 3.1.7 (build 
2190.2413); OpenVPN 2.1.4
2011-08-07 19:27:00 *Tunnelblick: Attempting connection with private; Set 
nameserver = 0; not monitoring connection
2011-08-07 19:27:00 *Tunnelblick: 
/Applications/Tunnelblick.app/Contents/Resources/openvpnstart start 
private.ovpn 1337 0 0 0 1 49
2011-08-07 19:27:00 *Tunnelblick: kextload: extension 
/Applications/Tunnelblick.app/Contents/Resources/tun.kext is already loaded
2011-08-07 19:27:00 *Tunnelblick: openvpnstart status #242: Error: OpenVPN 
returned with status 1. Possible error in configuration file. See "All 
Messages" in Console for details

I will snuff the thread [1] if someone has similar experience.

Original comment by obr...@gmail.com on 7 Aug 2011 at 5:44

[GoogleCodeExporter]

I believe there are two problems:

The "user XXXX" and "group nobody" lines. If user xxxxxx does not exist or is 
not understood by OpenVPN (which is probably the case), that is an error in the 
configuration file. The xxxxxx should be "nobody" (without the quotation marks) 
-- it should NOT be your username.

In fact, I suggest that you comment out these two lines and get the 
configuration working first, then add them back in only if you wish (but as 
"user nobody" and "group nobody"). That will make it easier to figure out 
what's causing any problems. There are reasons NOT to use "user nobody" and 
"group nobody" lines. They will, for example, make it impossible for OpenVPN to 
restore routes when a connection is terminated if the routes were set up by 
OpenVPN, which is usually the case and appears to be your situation.

The reference to "route-method exe" is also a problem. I believe that is a 
Windows only option. I think you can just comment it out or delete the line 
altogether.

 Either or both of these might be considered by OpenVPN to be configuration errors. It would be a bug if OpenVPN doesn't make an entry in the Console, but that may indeed be the case.

Original comment by jkbull...@gmail.com on 7 Aug 2011 at 6:33

[GoogleCodeExporter]

Ok I checked it and it's working now. The options of 
route-method exe
route-delay 2
make no trouble to OpenSVN, it just lives with that. But the username was 
really the cause of my problem - the one used is uknown to system, thus OpenVPN 
failed. 

Apparently, the best way to solve 'status #242' is to check openvpn command 
docs for options used in the config file. At least before spamming issue 
tracker...

Thanks!

Original comment by obr...@gmail.com on 7 Aug 2011 at 7:17

[GoogleCodeExporter]

I believe I'm having a similar problem: My Tunnelblick setup recently broke 
after I changed my OS X username (short name). So all my files now have 
permissions problems, and the Tunnelblick fails with error #242 saying it can't 
start "openvpn" executable. I've reset my permissions several times using a 
couple different methods. I'd like to follow this thread to see if there's a 
way to reset the certificate permissions as well. 

Original comment by butler.b...@gmail.com on 4 Jan 2013 at 5:42

[GoogleCodeExporter]

bulter.brendon --

Please post the *complete* log from Tunnelblick's "Details…" window.

What exactly was in the Console log? See my comment 1 at
http://code.google.com/p/tunnelblick/issues/detail?id=141#c1

Original comment by jkbull...@gmail.com on 4 Jan 2013 at 12:23

[GoogleCodeExporter]

i've got a similar issue:
openvpnstart status #242: Error: OpenVPN returned with status 1. Possible error 
in configuration file

tunnelblick log

2013-06-09 22:50:02 *Tunnelblick: OS X 10.5.8; Tunnelblick 3.2.9 (build 
2891.3328)
2013-06-09 22:50:02 *Tunnelblick: Attempting connection with riseup; Set 
nameserver = 1; monitoring connection
2013-06-09 22:50:02 *Tunnelblick: 
/Applications/Tunnelblick.app/Contents/Resources/openvpnstart start riseup.tblk 
1337 1 0 0 0 49 -atDASNGWrdasngw 
2013-06-09 22:50:02 *Tunnelblick: openvpnstart status #242: Error: OpenVPN 
returned with status 1. Possible error in configuration file. See "All 
Messages" in Console for details
2013-06-09 22:50:02 *Tunnelblick: openvpnstart: 
/Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn 
--cd /Users/plyvinyl/Library/Application 
Support/Tunnelblick/Configurations/riseup.tblk/Contents/Resources --daemon 
--management 127.0.0.1 1337 --config /Users/plyvinyl/Library/Application 
Support/Tunnelblick/Configurations/riseup.tblk/Contents/Resources/config.ovpn 
--log /Library/Application 
Support/Tunnelblick/Logs/-SUsers-Splyvinyl-SLibrary-SApplication 
Support-STunnelblick-SConfigurations-Sriseup.tblk-SContents-SResources-Sconfig.o
vpn.1_0_0_0_49.1337.openvpn.log --management-query-passwords --management-hold 
--script-security 2 --up 
/Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w 
-d -atDASNGWrdasngw --down 
/Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m 
-w -d -atDASNGWrdasngw --up-restart

console

Jun  9 22:50:02 plyvinyls-macbook-3 openvpn[3685]: Options warning: Bad 
backslash ('\') usage in /Users/plyvinyl/Library/Application 
Support/Tunnelblick/Configurations/riseup.tblk/Contents/Resources/config.ovpn:1:
 remember that backslashes are treated as shell-escapes and if you need to pass 
backslash characters as part of a Windows filename, you should use double 
backslashes such as "c:\\openvpn\\static.key"
Jun  9 22:50:02 plyvinyls-macbook-3 openvpn[3685]: Use --help for more 
information.

any thoughts? i read an earlier comment about the space in "application 
support" throwing things off. should i modify the .plist to change the filepath 
so there are no spaces? how would i do that again...?

Original comment by pvfi...@gmail.com on 10 Jun 2013 at 5:45

[GoogleCodeExporter]

oh yea my .ovpn file looks like this

client
dev tun
proto udp
auth-user-pass
remote seattle.vpn.riseup.net 1194
remote-cert-tls server
resolv-retry infinite
nobind
;mute-replay-warnings
ca RiseupCA.pem

i followed the directions for creating this vpn from this post
http://code.google.com/p/tunnelblick/issues/detail?id=141#c8

Original comment by pvfi...@gmail.com on 10 Jun 2013 at 5:49

[GoogleCodeExporter]

pvfilms:

OpenVPN seems to be complaining about the configuration file, but it looks OK 
to me.

I am not sure what ".plist" you are referring to. If you are putting an 
Info.plist into the .tblk, that could be the problem -- please post it (it 
should be in XML).

The only other cause I can think of is that there could be some invisible 
"garbage" characters in the configuration file. You might try copying the 
contents of it from you post and pasting them into the file, replacing whatever 
is in there.

Finally, Tunnelblick 3.3beta54 contains additional logging which might be of 
some help in finding this problem.

Original comment by jkbull...@gmail.com on 10 Jun 2013 at 12:30

[GoogleCodeExporter]

i installed the latest Beta version. here's the log.
anything jump out at you as no bueno?

2013-06-10 09:07:49 *Tunnelblick: OS X 10.5.8; Tunnelblick 3.3beta54 (build 
3415)
2013-06-10 09:07:50 *Tunnelblick: Attempting connection with riseup using 
shadow copy; Set nameserver = 1; monitoring connection
2013-06-10 09:07:50 *Tunnelblick: openvpnstart start riseup.tblk 1337 1 0 1 0 
305 -atADGNWradsgnw 
2013-06-10 09:07:50 *Tunnelblick:

Could not start OpenVPN (openvpnstart returned with status #236)

Contents of the openvpnstart log:
*Tunnelblick: openvpnstart log:
     Loading tun-20090913.kext
     stdout from kextload: kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-20090913.kext loaded successfully

     OpenVPN returned with status 1, errno = 13:
          Permission denied

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

          /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn
          --cd
          /Library/Application Support/Tunnelblick/Users/plyvinyl/riseup.tblk/Contents/Resources
          --daemon
          --management
          127.0.0.1
          1337
          --config
          /Library/Application Support/Tunnelblick/Users/plyvinyl/riseup.tblk/Contents/Resources/config.ovpn
          --log
          /Library/Application Support/Tunnelblick/Logs/-SUsers-Splyvinyl-SLibrary-SApplication Support-STunnelblick-SConfigurations-Sriseup.tblk-SContents-SResources-Sconfig.ovpn.1_0_1_0_305.1337.openvpn.log
          --management-query-passwords
          --management-hold
          --script-security
          2
          --up
          /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -f -atADGNWradsgnw
          --down
          /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m -w -d -f -atADGNWradsgnw
          --up-restart

     Contents of the OpenVPN log:

     More details may be in the Console Log's "All Messages"

from console

Jun 10 09:13:04 plyvinyls-macbook-3 Tunnelblick[703]: DEBUG: 
currentIPInfo(Name): IP address info was fetched in 866 milliseconds
Jun 10 09:13:04 plyvinyls-macbook-3 Tunnelblick[703]: DEBUG: 
currentIPInfo(Name): [216.7.77.52, 49211, 205.233.73.66]
Jun 10 09:13:04 plyvinyls-macbook-3 Tunnelblick[703]: openvpnstart status from 
compareShadowCopy: 251
Jun 10 09:13:05 plyvinyls-macbook-3 openvpn[740]: Options warning: Bad 
backslash ('\') usage in /Library/Application 
Support/Tunnelblick/Users/plyvinyl/riseup.tblk/Contents/Resources/config.ovpn:1:
 remember that backslashes are treated as shell-escapes and if you need to pass 
backslash characters as part of a Windows filename, you should use double 
backslashes such as "c:\\openvpn\\static.key"
Jun 10 09:13:05 plyvinyls-macbook-3 openvpn[740]: Use --help for more 
information.

Original comment by pvfi...@gmail.com on 10 Jun 2013 at 4:00

[GoogleCodeExporter]

I don't see anything.

What about the .plist -- what were you writing about?

Also, can you post the full output from "Copy Diagnostic Info to Clipboard" 
button on the "Log" tab?

Original comment by jkbull...@gmail.com on 10 Jun 2013 at 4:13

[GoogleCodeExporter]

forge t the .plist thing i was thinking of the solution from this earlier post 
http://code.google.com/p/tunnelblick/issues/detail?id=141#c2
and trying to implement the same

here's the diagnostic form keyboard
i clicked the 'copy to clipboard' button and tunnelblick froze up on me - beta 
version was not running smooth so i reinstalled 3.2.9

2013-06-10 21:42:33 *Tunnelblick: OS X 10.5.8; Tunnelblick 3.2.9 (build 
2891.3328)
2013-06-10 21:42:33 *Tunnelblick: Attempting connection with riseup; Set 
nameserver = 1; monitoring connection
2013-06-10 21:42:33 *Tunnelblick: 
/Applications/Tunnelblick.app/Contents/Resources/openvpnstart start riseup.ovpn 
1337 1 0 0 0 49 -atDASNGWrdasngw 
2013-06-10 21:42:33 *Tunnelblick: openvpnstart status #242: Error: OpenVPN 
returned with status 1. Possible error in configuration file. See "All 
Messages" in Console for details
2013-06-10 21:42:33 *Tunnelblick: openvpnstart: 
/Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn 
--cd /Users/plyvinyl/Library/Application Support/Tunnelblick/Configurations 
--daemon --management 127.0.0.1 1337 --config 
/Users/plyvinyl/Library/Application 
Support/Tunnelblick/Configurations/riseup.ovpn --log /Library/Application 
Support/Tunnelblick/Logs/-SUsers-Splyvinyl-SLibrary-SApplication 
Support-STunnelblick-SConfigurations-Sriseup.ovpn.1_0_0_0_49.1337.openvpn.log 
--management-query-passwords --management-hold --script-security 2 --up 
/Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w 
-d -atDASNGWrdasngw --down 
/Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m 
-w -d -atDASNGWrdasngw --up-restart

i attached another error that i was getting with the latest beta version...i 
could not find this cursed backslash that tunnelblick thinks i've got going on 
in my config file.........something about a backslash.....!?!
hohum

thanks for helping me out

Original comment by pvfi...@gmail.com on 11 Jun 2013 at 4:40

[GoogleCodeExporter]

pic

Original comment by pvfi...@gmail.com on 11 Jun 2013 at 5:15

Attachments:

• hmm.jpg

[GoogleCodeExporter]

Thanks for supplying the image of the error from the beta when trying to 
install your .tblk. That provided a clue. I think your config file has 
something like the following line:

ca RiseupCA.pem<BACKSLASH><SPACE>

The <BACKSLASH><SPACE> character combination would be displayed as a space -- 
you wouldn't see the backslash. But it is still there.

And that makes me think that there may be other backslashes in your config file.

Here's what you need to do -- start over from scratch:
     1. Uninstall Tunnelblick (see https://code.google.com/p/tunnelblick/wiki/cInstall#Uninstalling_Tunnelblick)
     2. Create a .tblk, with newly-downloaded files from Riseup, per https://code.google.com/p/tunnelblick/wiki/cConfigT#Creating_and_Installing_Tunnelblick_VPN_Configuration
     3. Install and launch the latest beta.
     4. When prompted, install the .tblk by double-clicking it. If it doesn't install, diagnose that problem.

If you have problems, please don't do anything else, it just muddles things 
(especially following instructions that are more than three years old). Just 
post the results of "Copy Diagnostic Info to Clipboard". If Tunnelblick freezes 
when you try to do that, put your .tblk into a .zip post it into a NEW issue 
report. But it can take several seconds for Tunnelblick to copy the diagnostic 
info, so make sure it really has frozen and isn't just working -- give it forty 
or fifty seconds, at least.

Original comment by jkbull...@gmail.com on 11 Jun 2013 at 6:22

[GoogleCodeExporter]

pvfilms posted a separate report, Issue 234 for the problems. It turns out the 
configuration file he was using was a "rich text" file, instead of a "plain 
text" file.

Original comment by jkbull...@gmail.com on 12 Jun 2013 at 10:04