Antonio Quartulli <[email protected]> writes: > On 19/03/2026 10:18, Gert Doering wrote: >> On Thu, Mar 19, 2026 at 10:08:45AM +0100, Antonio Quartulli wrote:
>>> It sounds as if you are looking for the --port-share option? >>> It's been there for a while (way before multisocket was implemented) and it >>> seems to be what you are looking for. >> I think he wants it the other way round - connections go to nginx, >> and >> *if* openvpn, then forward to openvpn. > > Ah. This would require nginx to be able to detect OpenVPN packets and > forward them accordingly. Not sure this can be done at all. Yes. I don't want to make my web service dependent on openvpn. These days, it seems things can mostly be set up on their own port on 127.0.0.1 and then have nginx reverse proxy for them. I would also like the TLS connection from openvpn to appear to any networks in between just like web traffic, at least until you look at timing and data sizes. I am finding that many wifi networks purportedly for customer convenience at businesses are blocking openvpn's udp/1194. It would be nice if openvpn's TCP support could somehow be over https and a prefix within the webroot (or vhost, if it must be). I think I'm asking for "openvpn over https" instead of "openvpn over tcp". But we're arriving to a world where https to 443 works and much else is blocked. _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
