Kill OVPN client connection
-
Browser was Chrome : BUT only when remotely connected via another OpenVPN tunnel.
-
Also on Android Dolphin via OpenVPN
-
Sorry for the multiple replies; I realised I didn't answer your other question:
Yes the same error message appears under Status / OpenVPN.I find I have to restart the service if I want to manually disconnect a connection.
Browser Latest version of Chrome: Version 63.0.3239.84 (Official Build) (64-bit).
-
I can't seem to reproduce that here at all. And it definitely doesn't make sense that it only happens when you connect over some other VPN.
Unless you are killing your own VPN connection, which would mean the web server couldn't respond back to you which could result in an AJAX error. But that doesn't make sense if restarting the service fixes it.
From the logs it appears to be taking the correct action, however. It's possible it's an error in OpenVPN itself and not a bug in pfSense.
-
Just an idea,
What if login into OpenVPN`s management interface using telnet/netcat and kill client there… -
I can execute a shell command via SSH but;
How do I kill an individual client on a particular openvpn service? -
Currently no access to PFSense box but first find the line in the server config file
management IPaddress PortThen in SSH do
nc IPaddress PortCan use telnet too, then nc=telnet
You will see like:>INFO:OpenVPN Management Interface Version 1 -- type 'help' for more infoType help and also look here:
https://openvpn.net/index.php/open-source/documentation/miscellaneous/79-management-interface.html -
I'm guessing I will need to edit the server config file to include this.
Current file has : "management /var/etc/openvpn/server2.sock unix"Can I edit it in pfSense ; or just directly?
-
Could try with connecting to socket:
nc -uU /var/etc/openvpn/server2.sockor
socat - UNIX-CONNECT:/var/etc/openvpn/server2.sockAlso see –management in manual:
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage -
OK, so I have done as suggested:
Via ssh:
nc -w 20 -U /var/etc/openvpn/server2.sock
kill xxx (cn)Result:
SUCCESS: common name 'xxx' found, 1 client (s) killedThat functions, but (of course) - still not via the web interface.
I have tested the web interface (kill openvpn) on my central server and also on client machines (SG-1000 & APU)
and all exhibit the same error message. -
I am still at a loss as to why I get an error message from the gui.
Are there any tests I should run, or config changes to further investigate? -
@Gil:
I get an error:
An error occurred. (-1)
when I attempt to kill an OpenVPN client connection on my APU server box status screen.
This never used to happen prior to 2.4.0 upgrade.Same here on 2.4.2. Also no errors in logs.
Tried with Chrome, Safari and Edge via Web-gui.
-
@Gil:
OK, so I have done as suggested:
Via ssh:
nc -w 20 -U /var/etc/openvpn/server2.sock
kill xxx (cn)Result:
SUCCESS: common name 'xxx' found, 1 client (s) killedThat functions, but (of course) - still not via the web interface.
I have tested the web interface (kill openvpn) on my central server and also on client machines (SG-1000 & APU)
and all exhibit the same error message.From the result I would think it`s not an OpenVPN issue…
-
Thanks Pippin.
Generic googling tells me (-1) errors often relate to hardware.
My errors occur on all my devices APU and SG-1000. -
I should also mention; all my devices run a bridge for a tap openvpn.
peter808 : Are you similar? -
I have an OpenWRT OpenVPN connection that also gives the same error on my pfSense Server
-
Same here on 2.4.2. Also no errors in logs.
Tried with Chrome, Safari and Edge via Web-gui.
Same here
-
The "Error occurred" pop-up on the dashboard is caused by a race condition where the widget is requesting status from a resource that no longer exists. Annoying no doubt but it should not affect functionality.
Fixed in the next snapshot
-
Thanks Steve_B .
I take it that the fix will not only stop the error popup, but also execute the kill OpenVPN command? -
Small clip of the GUI behaviour
