![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
61·
4 months agoJust a reminder that even though the tunnel itself is encrypted, the whole connection is not E2E encrypted between your remote client and the server. Cloudflare as a CDN/PoP provider can see the traffic in plaintext.
In all other aspects, this is a great solution, as we even get to use the edge caching(over top of all others mentioned above) facility - which further reduces the requests to origin server.
From IPv6.rs FAQs I get the impression that they only provide IPv6 route through their tunnel. I think self-hosting something only reachable via IPv6 would cause you trouble accessing it in IPv4 only networks - which are still far more common compared to IPv6.
Hurricane Electric provides such IPv6 over IPv4 tunnel facility with /48 block routed to your network. I’ve only used this service for testing my IPv6 knowledge, so performance-wise I’m not sure how good it is. Thus, if IPv6.rs provides a significant performance over the HE-TunnelBroker, then I’d suggest you go with IPv6.rs given a decent price for the service.
If you are considering a simple to set-up tunnel utility for your self-hosting applications, I’d suggest you consider other tunneling options which have both IPv4 and IPv6 capabilities. Some widely used ones are Cloudflare Tunnel and Ngrok. You may also use Tailscale to connect both server and client via VPN. Using Cloudflare or Ngrok would involve some privacy concerns, as they can see the traffic passing through the tunnels in plain text.
E: better words substitution