Configure openvpn-as Docker Image tag 3.0.2-xxx with Docker-compose

Databes

I wanna running the openvpn-as in VPS using Docker Image with Docket Compose. My docker-compose.yml is like the quickstart from the documentation image "openvpn-as" wroted. Expect i was binding the port 443 to 8082.

I expect to proxy the 8082 port with Apache2.4 web server. But, the container itself can be access via SSH Tunnel.( If need the logs, i will be glad drop to next section discusstion cause i writing this on smartphone ).

I tried to running image from local computer. Its working as expected then i can even go futher access via SSH Tunnel.

I glad to hear your suggestion guys. Thanks you.

The Johan

Sorry, it's a bit hard to understand what the problem is that you're facing.

I see you try to instead of port 443 use another port. Okay, but then you have to update in the Access Server configuration too, because that will still default to 443. Changing port in the docker configuration doesn't mean it changes in Access Server too. They have to both be the same port.

Regarding proxying with Apache2, yeah, I wouldn't do that if I were you. You may be able to get the web traffic to work, but port 443 TCP also doubles as a fallback port for TCP OpenVPN connectivity. And Apache2 doesn't proxy that, so you basically broke half the connectivity for VPN connections by putting Apache2 inbetween.

Is there any reason to put Apache2 as proxy? We really don't think that's necessary or recommended. Just run it straight.

Databes

The Johan
What I mean by "binding port" is not to change the Docker container or rebuild the openvpn-as image—just bind host_port:container_port in the ports key of the docker-compose.yml file.

The reason I was using Apache as a proxy is because I have domain-based vhosts running on port 443. So I can't use port 443 directly. I don't fully understand by the proxy work in Apache and how it will not working for OpenVPN connection cause Apache in between, I'm sorry.

Is there any alternative solution for this case?

The Johan

You're talking about this right?

docker run -d \
--name=openvpn-as --device /dev/net/tun \
--cap-add=MKNOD --cap-add=NET_ADMIN \
**-p 943:943 -p 443:443 -p 1194:1194/udp **
-v <path to data>:/openvpn \
--restart=unless-stopped \
openvpn/openvpn-as

And then changing it so the outside port is different than the inside port? Or changing both? In both cases you need to also let Access Server know because either Access Server won't listen on the new port you specify or it will tell the VPN clients to connect on the wrong port.

I don't have a solution for the sharing of web services on the same port with other domains when used with Access Server. It is technically possible I suppose but not intended. You could consider running AS entirely on different port so it doesn't interfere with your already in use TCP port 443.