I set up an OpenVPN Access server with the "port-share" option to share the 443 port with secure webserver.
The web server and the openvpn server are working correctly and I am able to connect with different openvpn clients in linux and windows. However, when I try to connect with the openvpn client downloaded from the OpenVPN Web UI (openvpn-connect-2.0.8.106.msi) the requests to connect to the vpn are redirected to the webserver and I am not able to connect. If I disable the port-share option, then I am able to connect with the openvpn-connect client.
I guess this is because the Connect client is a browser based as mentioned in the OpenVPN AS SysAdmin manual. Is there a way to make the Connect client work when the port-share option is enabled?? And if not, what should I do so that a different client is downloaded from the WebUI instead of the Connect client?
openvpn connect client not working on sever with port-share
-
- OpenVpn Newbie
- Posts: 1
- Joined: Sat Nov 22, 2014 2:57 pm
- novaflash
- OpenVPN Inc.
- Posts: 1073
- Joined: Fri Apr 13, 2012 8:43 pm
Re: openvpn connect client not working on sever with port-sh
The default configuration works with UDP daemons on port 1194, TCP daemons on port TCP 443, and the web services on TCP 943.
This default configuration works fine with the Connect Client.
If you change port settings, all clients must be reinstalled to get the updated configuration.
If you somehow try to squeeze your own web server in here and use port-sharing to redirect to that, you will cause problems with the API that Connect Client and Access Server use to communicate. If you do this, you will need to switch the Connect Client to advanced mode and manually install a user-locked or autologin profile, instead of relying on the built-in API to negotiate with the Access Server for a connection profile.
https://docs.openvpn.net/under-the-hood ... ent-basic/
This default configuration works fine with the Connect Client.
If you change port settings, all clients must be reinstalled to get the updated configuration.
If you somehow try to squeeze your own web server in here and use port-sharing to redirect to that, you will cause problems with the API that Connect Client and Access Server use to communicate. If you do this, you will need to switch the Connect Client to advanced mode and manually install a user-locked or autologin profile, instead of relying on the built-in API to negotiate with the Access Server for a connection profile.
https://docs.openvpn.net/under-the-hood ... ent-basic/