search

vaibhav-rbs / tunnelblick

Automatically exported from code.google.com/p/tunnelblick
0 stars 0 forks source link

Tunnelblick don't load at boot #254

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I have upgraded to latest stable : 3.4.1 (build 4054)
2. And reboot
3. Tunnelblick is configured to load the configuration when the computer start

What is the expected output?
It should load Tunnelblick when the computer start

What do you see instead?
It does not load

What version of Tunnelblick are you using? On what version of OS X?
 3.4.1 (build 4054) on Mavericks 10.9.5

It was working great on the stable version before this one.
In the system.log file, I can see this, maybe it's related:

Nov 13 10:04:10 MyMac com.apple.launchd[1] 
(net.tunnelblick.tunnelblick.startup.openvpn[101]): Exited with code: 254

Thanks

Original issue reported on code.google.com by spij...@gmail.com on 13 Nov 2014 at 10:08

GoogleCodeExporter commented 9 years ago 
Please try the following:

     1. Use Activity Monitor to quit all processes named "openvpn" (be sure you view "All processes" and not "My processes")
     2. Set all configurations to connect "Manually"
     3. Look in /Library/LaunchDaemons and remove all files that start with "net.tunnelblick" (if there are any)
     4. Make the connection "private"
     5. Make the connection "shared"
     6. Set the configuration to connect "When computer starts"
     7. Restart the computer and see if the connection starts

Please report the results back here.

Original comment by jkbull...@gmail.com on 13 Nov 2014 at 2:31

GoogleCodeExporter commented 9 years ago 
I have done each point and it works, thanks !

For information, on point 3 I don't have an existing net.tunnelblick file, I 
suppose point 2 has deleted it correctly.

Original comment by spij...@gmail.com on 13 Nov 2014 at 11:17

GoogleCodeExporter commented 9 years ago 
Thanks for reporting back your results.

Yes, that's correct, point 2 should have deleted the file, but I wanted to make 
sure so I had you check for it at point 3.

I am closing this Issue as "WontFix", meaning I will not take any further 
action.

Original comment by jkbull...@gmail.com on 13 Nov 2014 at 11:31