Cloudron Forum

@mmtrade Okay, after a thorough analysis of my account. I have a VPS the cheapest, where I could not change the IP address. It remains technical support to solve this and as you in which you manage the server you have the task of securing the server.

It is as @humptydumpty said. Cloudron 8 (not yet released) has IPv6 only support.

I remember now. We have this issue with the DNS server (unbound) we use which doesn't work properly with just IPv6 with our configuration. We are working on getting away from unbound altogether because of various other issues, so will get to do this after that.

@BrutalBirdie said in Automatically sync DNS when enabling IPv6: Right now you either have to just wait for it to happen some time Actually, it never happens automatically (this might appear to be automatic if you had Dynamic DNS enabled).

@girish Thank you. Your solution did the trick. But we needed the ipv6 to be functional. So what we did to make it work was > reinstall Ubuntu 22.04 LTS OS and didn't install unbound in advance. All is good now.

@ccfu right... if DNS is not mainained by Cloudron, we have to show some message/alert the user. This requires some work, this is why this feature is not done yet It seems like quite some work for very little value.

@jdaviescoates does curl -6 https://ipv6.api.cloudron.io/api/v1/helper/public_ip work on the server? If not, check the IPv6 setup. You can also disable Cloudron's IPv6 with Network -> IPv6 -> Disabled .

@AartJansen for new apps, AAAA is automatically added. For existing apps, go to Domains -> Sync DNS.

@AartJansen Ah ok, looks like a limitation of the domain host. You can also just create entries for each (sub)domain you use. If you have an app at foo.domain.com, create an AAAA record for that subdomain. Repeat for every app. You should also switch to "manual" instead of "wildcard" DNS provider for this. It will remind you to setup A/AAAA records manually when you install an app.

@girish said in IPv6 in automated DNS propagation: After enabling, click the sync DNS button to make it add the AAAA records for existing apps. This is what I missed. Thank you so much! Everything works fine now

Thanks for the reply @MooCloud_Matt! Proxmox is set to bridge and works with ipv4 without any problem. But the problem is probably elsewhere, I tried opening the ipv6 test page on my laptop and it said my provider doesn't support ipv6, which is bullshit. I actually have two public ipv6s assigned from it. So I would need to somehow run the installation with only ipv4, is it possible to do that? [image: Sn-mek-obrazovky-z-2023-01-09-16-07-51.png]

You can try ping6 ipv6.api.cloudron.io and see if that works. Without it, IPv6 won't work.

@girish Thanks Girish. I assume that'll be fixed in the next bug-fix release as it looks fixed already in the code from this bug report (referencing for others): https://git.cloudron.io/cloudron/dashboard/-/commit/b62da8ba70dd8b4a8964de5a2c01e6ff7afa0e99

@imc67 essentially the patch for this is https://git.cloudron.io/cloudron/box/-/commit/eb0662b2455e0687ab3ce5dd02d2466e16670092 so two files need to be adjusted. The .ejs file is a template which will result in /etc/nginx/applications/my.<domain.com>.conf so besides the editing the .ejs file additionally edit that file and then systemctl restart nginx and systemctl restart box.

@samuelbevan2000 you have to port forward port 443 in the router to the vm.

@thpuffin yup, working on ipv6 support for 7.1!

@girish I did not know the term. I certainly did know the effect ^^ (I might have to invest in an actual rubber duck... maybe they are especially effective)

You can close this topic. -.- I realized that homeassistant is limited to IPv4 support actually. =/

@jodumont from experience I know MX doesn’t work because the mailserver doesn’t respond to IPv6. That way we’ve lost some mails before we discovered that.