IPv6 only Cloudron
-
I have tried this a few months ago as well.
The next blocker is that the setup code does some domain IP validation, and refuses to continue of there are no IPv4 addresses available. I worked around it in the setup code of the box project on my machine, but that is of course highly discouraged
. Sadly, I lost that code (it wasn't too bad). I'm not entirely sure whether it works with a private IPv4. I haven't tested that. I don't think so though.Once the box supports primary IPv6, then the rest will more or less work. Because it support IPv6 mostly fine after setup. Thinks like the web front-end, and mail all work with IPv6.
Individual apps may or may not work if they do something other than standard HTTP(S). The OpenVPN app for example does not work correctly yet. At least it does not route IPv6 through the tunnel, possibly because the Docker containers are all IPv4-only.
@jk said in IPv6 only Cloudron:
possibly because the Docker containers are all IPv4-only.
internally, IPv6 is enabled for containers. Could be some other issue though.
Previously, the biggest blocker was both npm and docker hub not supporting ipv6. Both of these support ipv6 now. I think the biggest blocker is really the UX at this point. Practically all public wifis (cafes, airports) and most home networks still have only IPv4. This makes the server unreachable... I have been working out of a co-working space which doesn't have IPv6 either!
-
G girish moved this topic from Discuss on
-
G girish marked this topic as a question on
-
G girish has marked this topic as solved on
