Comment on Best way to get IPv4 connectivity to my self-hosted services

spanac@lemmy.zip ⁨1⁩ ⁨day⁩ ago

I have a similar situation, where I only get a public IPv6 prefix. I ended up renting small vps at netcup and installed OpenVPN and ha-proxy. My home router connects to the VPS’s public IP and I do port forwarding for the services I need, or use the proxy.

Initially I setup SNAT for my web server (otherwise replies were going out the wrong interface) and that meant you don’t see the public IP of the connecting client in your access logs.

Recently I switched to using ha-proxy which does tcp level proxying and works well with ports 80 and 443 and Traefik, which i use to expose my docker containers.

My connection chain looke like vps -> ha-proxy -> OpenVPN -> port forward to Traefik -> reverse proxy to the final service. It’s not a fast server, and I didn’t measure latency, but it’s for sure not small.

As others have mentioned, ha-proxying to your IPv6 might be an interesting solution, and I think I will also try it out.

source
Sort:hotnewtop