Best way to get IPv4 connectivity to my self-hosted services
-
Small and stupid question.
Why don't use a ddns client to update your ipv6 evytime it changes? With a ttl of a minute your shouldn't be able to see any downtime...
I (genuinely) thinks you are trying to solve a small problem in the complicated and hard way.. M
Plenty of IPv4 only networks still exist from which you would not be able to access the services. I am in a similar situation as OP with my offsite address being IPv6 + CGNAT IPv4 and my own address being IPv4 only.
-
I'd just set up the reverse proxy on the VPS and make it forward everything via IPv6. But you could also use a tunnel/VPN, everything from Tailscale to Wireguard or even an SSH tunnel would work. And there are dedicated services like Cloudflare, nohost, neutrinet, pagekite...
wrote on last edited by [email protected]I'll add Pangolin to the list, it's a self-hosted Cloudflare tunnel alternative.
-
Ionos.de has a €1 a month VPS
I think 1 core, 1gb ram, and 10gb.
Use either caddy or Nginx proxy manager. Both are easy to setup. Also both are dockerized.
I use Tailscale as my tunnel.
Total latency is about 70-90ms for me.
wrote on last edited by [email protected]I did something very similar via netcup tiny vps, nginx and wireguard.
I could post my setup notes tomorrow if someone needs them. -
If someone manages to get root (!) access on this VPS it's over either way.
NO, an attacker getting control over a vps used as a tunnel could not read Data captured in the past.
Also they could not do a MITM with decrypted SSL without breaking HSTS
