Running a self hosted server with IPv6 is still a nightmare in 2025

First of, a disclaimer: I have NOTHING against IPv6. I find it great. I find also AWESOME that all my devices behind my ISP's router/modem/box (I'll just call it a "box"), are provided with a public IPv6 address.

1.

But then...you have mobile clients who use 4G/5G. And guess what, some telecommunication operators, in 2025, still do not support IPv6 over 4G. That means, that you're feel completely MAD as YOU can access ALL you services from "outside" your local network using a computer. But when you switch to a phone -> you dead. Then you enable the WiFi connection on your Phone and NOW your services are accessible again

2.

Some software DO NOT support IPv6. For instance Arma 3 server doens't support IPv6. Arma 3 is a 2013 game, which is still sold for a good price on Steam (27.99€, last time I checked https://store.steampowered.com/app/107410/Arma_3/), and the game is still played A LOT https://steamcharts.com/app/107410. So money is flowing, don't tell me this couldn't be fixed/updated.

And this is just ONE example.

3. IPv6 SHOULD be the default if available. That's the policy that should be implemented EVERYWHERE. I'm talking over the Internet, ok? I don't mean for our local networks at home (even if honestly, it's the same thing EXCEPT that the addresses are not easily memorizable for a human).

Windows 10 (up to date, even if, yes technically they're not updating it any longer), doesn't have IPv6 enabled by default! You have to do it manually, and THEN, sometimes, for no reason it's disabled again, or weirdly malfunctions in mysterious ways. (Now it's stable on my machine tho)

4.

All those little troubles add A LOT of time figuring out how could I solve my problem. The solutions, to this day are limited in some ways:

Buy a VPS, tunnel everything there (easier said than done, but doable). The problem is: I do not want to have to subscribe to a VPS just because IPv6 isn't supported properly.

Install some kind of cloudflare tunnel. And I hate that. I hate it. To set it up, I had to run some kind of docker container, that registered something somewhere, generated a URL that I clicked on, then I had to change my nameservers on my registrar's side and I have to keep a service running for this tunnel to be working.

All of those things are NOT in my control, and I cannot accept it as a "valid solution". And GUESS WHAT? Today, Cloudflare is down ( https://news.ycombinator.com/item?id=45963949 ) -> BOOM perfect example, you delegate ONE service to the cloud -> all my services are inaccessible. And I'm not criticizing Cloudflare here, they provide a tunnel for me, for free, but the thing is, I installed that solution reluctantly.

5. What works amazing well with IPv6:

* Linux -> just works

* DNS, nameserver, registrar -> you set up the AAAA register for your domain/subdomain, boom job done. And this seems like a detail, but we all know the joke "it's always the DNS" as in "it's always the DNS' fault", but, get that, DNS (the protocol) works perfectly with IPv6.

6. I think about small businesses, small associations, NGOs, small clubs, etc. -> if they have the will to host their own services.

Because let's say that their data must be protected or simply, like me, they like to own and host stuff, because it is technically and intellectually satisfying to finally be able to use Internet as it was intended (thank you all the Gods of Olympus for my symmetric gigabit fiber optic connection) -> well, if their ISP is as stingy as mine and running out of IPv4 addresses, they're gonna end up having to do things in IPv6...and it'll surely be the beginning of a series of small technical nightmares for them.