docker-ipsec-vpn-server VS openvpn3

IPSEC-L2TP is built into everything. No clients required on Windows, Mac, Android, iOS, Linux, etc. Great Docker container for cutting through most of the difficulty here: https://hub.docker.com/r/hwdsl2/ipsec-vpn-server

e.g: https://mingheng.medium.com/how-to-setup-an-openvpn-server-with-docker-on-an-aws-ec2-in-15-minutes-50443bd31dff atau https://github.com/hwdsl2/docker-ipsec-vpn-server

I'm currently using hwdsl2's VPN Docker container on my server so that I can access my internal network resources while away from my home network. However, it seems that if I connect through my DuckDNS pointer, the connection takes a long time to establish (iOS/macOS will simply say "Connecting..."). I know that this would be a question to raise an issue about, which I did so here. In a nutshell, the developer of the container believes that it would be an issue on DuckDNS' end.

Setup your VPN (one image I found on hub.docker.com is https://hub.docker.com/r/hwdsl2/ipsec-vpn-server)

https://hub.docker.com/r/hwdsl2/ipsec-vpn-server ..?

My suggestion: Don't open up ssh to the world, set up a vpn to your home network instead, then connect to your server just as if it was on the loc network. Here's a possible option to setting up a VPN using docker: https://hub.docker.com/r/hwdsl2/ipsec-vpn-server

I use this and it works very well for me

All our products builds on what we call the "OpenVPN Core". In essence, that is the OpenVPN 2.x project and the OpenVPN 3 Core library. This is the "low level" code which provides the core VPN functionality.

OpenVPN 3 (Core) is a complete rewrite and reimplements the OpenVPN protocol as a C++ library. The OpenVPN Connect (macOS, Windows) apps and OpenVPN 3 Linux project are all based on the OpenVPN 3 Core project. In addition, the OpenVPN 3 Core can be activated instead of OpenVPN 2.x on OpenVPN for Android. Currently all of these products and projects only implements the client side.