docker-ipsec-vpn-server VS algo

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

Since we're already presuming you have a functional PFSense box with Wireguard installed and a VPS stood up, now you need to get Algo installed on the VPS. I'm not going to write this part out in detail, but basically you need to follow the procedures here to get Algo installed. However, *before* running ./algo you probably want to edit some of the config.cfg settings. I disabled IPSec (which saves a bunch of package installs and prevents a bunch of failures I saw on some of my VPSs), set my reduce_mtu setting to 80 just to prevent any MTU issues down the line, turned off DNS encryption, and renamed my users to the servers in question (for example: pfsense, vps_server, etc)

Check out the command line args for Auto1111, it talks about a gradio setup that can be accessed remotely. There's a time limit on gradio links though, I think. You could also set up a vpn that will allow you to access your PC remotely, then run A1111 with the --listen command and access it that way. I've done this with an Algo VPN on Azure and a Wireguard client for Windows for Android, but any VPN that lets you access your PC remotely would work.

One way you could try to get around is building your own VPN service, like this: https://github.com/trailofbits/algo/blob/master/README.md

Things I have tried so far: Clear network cache and reset adapters - IDK it fix aprevious problem I had https://github.com/trailofbits/algo/discussions/14504

(I can simply install Algo and get the Wireguard tunnel working, easy peasy... But from there, I can never get Plex port 32400 open... so I'm just trying from scratch now...)

Maybe try running algo vpn (following the road-warrior setup) in a VM instead? It has very light requirements. https://github.com/trailofbits/algo/blob/master/docs/deploy-to-ubuntu.md