Unable to right-click OpenVPN Gui after successful connect

[delebre]

As stated in the subject, I am unable to right-click OpenVPN Gui after successfully connecting to the VPN server.

I am running Windows 7 (32-bit) Home Prem with SP1
Using: OpenVPN 2.2.0

I am running the program with 'Run as administrator' checked.

Help? I cannot disconnect without logging out of my username in Windows...

[george]

When you say, ca't right click the icon, I assume you mean the system tray icon. Does it not show up any longer after you connect? Can you right clcik any of the other icons when this is happening?

You could always use the taskkill command to stop the process.

[kmoerder]

I have a similar problem on a windows 7 pro machine.

I had a worinng client install with openvpn 2.2.0. I uninstalled and then installed 2.2.1. After that, I have the same problem that after successfully making a vpn connection, a right click on the openvpn gui in the system tray has no effect. Hovering shows the normal tool tip data. left click darkens the icon momentarily as it did before, but right click has no effect.

Before making a connection, the right click works fine.

Uninstalling and then installing 2.2.0 did not fix the problem.

Thanks,

Karl

[george]

As I asked in my last post, can you get a right click context menu from another system tray icon?

Can you double click the icon and open up the status display?

Have you tried using the taskkill command to kill the process rather than logging out of windows?

Have you changed the system tray's hide icon settings for the openvpn-gui icon?

[pfoerster]

Hi,
same problem. Unable to right click after succesfull established the vpn connection. All other Icons works properly.
The only way to end the vpn session is to kill both processes via task manager.
I'm working with windows 7 - 64 bit.
Any idea?

[oidvoid]

Hi,

Exactly the same problem as others. In response to @george's questions:

Can you double click the icon and open up the status display? No

Have you tried using the taskkill command to kill the process rather than logging out of windows? Yes. Actually, I use an app called KillProcess which allows me to right-click on openvpn-gui in the list of running processes. I can then select "Show process window" which brings up the window and allows me to disconnect. If I go to the list of running processes again, I can terminate the process from there once I have gracefully disconnected.

Can you get a right click context menu from another system tray icon? Yes, all others work.

Have you changed the system tray's hide icon settings for the openvpn-gui icon? Yes.

As @kmoerder stated, before making a connection, the right click works fine.

I'm running Windows 7 Professional x64

Thanks in advance for any help on this.

[kmoerder]

Exactly the same for me. Right click before connection is fine, after connection, no right click response from the openvpn gui. All other right click in the system tray works fine. My machine is windows 7 pro 32 bit.

The Openvpn gui used to work fine on my machine. It stopped working after I uninstalled openvpn version 2.2.0 and installed version 2.2.1. Reverting to version 2.2.0 did not solve the problem. I tried a variety of uninstall/reinstalls but the problem persists.

The taskkill approach is problematic for me because I need to disable/enable the tap interface in order to connect to my home network again. So this is currently a show stopper for me.

Is there any other information that would help identify the source of the problem.

Thanks,

...Karl

[twofish]

I have the exact same problem. I am able to click all other icon except OpenVPN. Nothing happens when I left/right click OpenVPN tray icon after it's connected. I use windows 7 x64 all up to date. I also tried plenty of compatibility modes, like XP, 2000, Vista, and all the other compatibility options like Disable Themes. I have to taskkill the process.

[twofish]

IS there any update on this problem? It seems I'm not the only one with it.

[Mimiko]

I tryed on Windows 7 Pro Eng x32 licensed - after connection OpenVPN GUI tray icon respons normally to the right click.

Unfortunally, in my practice with Windows 7 I encoutered some compatibility issues with some programs, when defined same Windows 7 same Pro same language and x32, but from different install DVDs (different builds and customizations). I got the problem that on some Win7 the programs works on others - not.

This is a proble of Windows itself. When you encounter problem with right click on OpenVPN - try reinstalling Windows from another build (DVD). Its happens that your current installation disk are not the right one.

[twofish]

I'm sure if I talked to a M$ dev they would blame this issue on Openvpn. I'm also sure that if I talked to an openvpn dev, they would blame the issue on M$.

My point is, this issue will never be fixed.

[iglezh]

I am having exactly the same problem, after succesfully installing and operating a customized version of openvpn for quite some time, at some point the tray icon stoped responding. I am assumming that it is a windows update, but without knowing which one it is impossible to rollback the installed update. It is installed in several windows 7 devices, so it must be related to the enviroment and the update.

Has anybody else been succesfull in pinpointing the cause of the problem ?

Has any body installed a debugging version of the opengui to find out how the events are being processed ?

Let me know

Thanks !!

[Mimiko]

at some point the tray icon stoped responding.

If you think that an update is causing the problem, you can pinpoint the update which were installed. Just remember when it last worked and when it started to hang. See the update logs between those two dates to find which update where installed.

Unfortunatelly, I can't simulate the steps to hang the tray icon.

[iglezh]

I can't, but I'll see if I can replicate it in another identical system,

Thanks

[hrast]

I have the exact same problem on a Windows 7 x64 Pro install (first OpenVPN install on this system, ever. OpenVPN 2.2.1). The secondary mouse click on the icon in systray brings up a menu until the connection completes and the connection log window hides. After that, secondary clicking on the systray icon is non-responsive.

Secondary click on Systray icon works:

When freshly started (icon screens are red)
When connecting (icon screens are yellow)

Secondary click on Systray icon is unresponsive:

When connected (icon screens are green)

I'll be more than happy to test any ideas....

[jjmcnelly]

I am having the same issues. Win7 32 bit. I installed the gui version and have had the issues since installation. Installed the same on another win 7 machine with no issues.

[rolfieo]

At the moment I have the same issue.

I have a dual boot systeem (2 * Windows Ultimate 64Bits ENG). And on my new Windows installation, i have the issue.
When the OpenVPN is connected, right click does no longer work.

Very very unuseful.....

I have done some testen, but its a strange BUG.
Asson as the connection is made, the tray icon does not function anymore.
Even after i kill the openvpn.exe it still will not workany more.

But Why?
The other tray icons do still work.

Very very irritating BUG.

[orchidanni]

Similar issue(s):

I have OpenVPN installed on a Windows XP 32 bit installation. According to my friendly tutorial site, I should be able right click and get a menu which allows me to adjust some of the config settings with a GUI window (am trying to use tun instead of tap). I do get a menu when I right click, but the shortcuts there open the config files in Notepad. Unfortunately, I don't have the chops to know what exactly isn't working or how to fix it.

When I try to run it, OpenVPN looks like it's connected to the VPN I'm using, but I get the following info and 'warnings' and all of the pages I try to load time out:

Thu Oct 06 09:00:55 2011 OpenVPN 2.1.4 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 8 2010

and

Thu Oct 06 09:01:25 2011 WARNING: 'dev-type' is used inconsistently, local='dev-type tap', remote='dev-type tun'
Thu Oct 06 09:01:25 2011 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1573', remote='link-mtu 1541'
Thu Oct 06 09:01:25 2011 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500'

I know the VPN, my account and passwords are good, the fingerprint on the CA.pem looks good, and these all work swimmingly on my Ubuntu installation.

Bearing in mind that I don't have a whole lot of Windows knowledge (as in I can find the Command Prompt with the GUI shortcut, and that's about as much as I know on my own), how can I change the settings so it works?

Information that may also be relevant: although the readout I get when I 'connect' with VPN shows that I'm running on version 2.1.4 (see above), when I open the 'about' info from the right click menu, it tells me that I'm running "GUI v1.0.3". What's up with that?

Anyway, thanks to the team for writing open source software and thanks for helping out 'the little people'.

[Mimiko]

orchidanni, I see you don't have the same problem. You are right clicking and the menu is showing and you click and something happens.

although the readout I get when I 'connect' with VPN shows that I'm running on version 2.1.4 (see above), when I open the 'about' info from the right click menu, it tells me that I'm running "GUI v1.0.3". What's up with that?

OpenVPN GUI is just an interactive interface for OpenVPN client. Ofcourse they are different versions.

Thu Oct 06 09:01:25 2011 WARNING: 'dev-type' is used inconsistently, local='dev-type tap', remote='dev-type tun'
Thu Oct 06 09:01:25 2011 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1573', remote='link-mtu 1541'
Thu Oct 06 09:01:25 2011 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500'

Edit your config file and change to "dev tun", "link-mtu 1541" and "tun-mtu 1500". It must be as on server.

[orchidanni]

Mimiko:

Apologies for posting in the wrong place, and thanks for the suggestion. The only thing I was able to find in my config file was 'dev tap'. You were quite right: changing this to 'dev tun' was the adjustment needed. Many thanks, and again, excuse me for posing on the wrong thread.