Cloudron Forum

@IniBudi there's many threads in their forum if you speak german. Like https://forum.netcup.de/administration-of-a-server-vserver/vserver-server-kvm-server/9565-ipv6-einrichten/ https://forum.netcup.de/administration-of-a-server-vserver/vserver-server-kvm-server/17978-verbindung-über-ipv6-nicht-möglich/ . Since, I don't speak german, I am quite lost in that forum.

Just for the reference: netplan try is usually a better way, as it might save from end up getting locked out from the server. I also usually run a background cron task, that removes those temporary files from /etc/netplan, when messing with the network.

@jdaviescoates Yes I had done that a while ago

@Bedrijfstak14 in v8, the IPv6 defaults to auto-detected. Probably best to choose this explicitly based on your setup.

@nebulon said in All Offline adter update or db can't restart.: by avoiding disabling by avoiding disabling at least I think that's what you mean?

@msbt yes, exactly. It will also get into error state only after some time (because it will retry a lot)...

@girish moreover, the package.json on my WS indicates the version installed as being "version": "5.9.0"so then I still tried from the git directory and I still get: No image found, please run `cloudron build` first or use --image Now, when I try without the git to the repo then I get: App repair error: No CloudronManifest.json found Ho my...

Indeed, after sync I enable the IPv6, the app store works just fine as well as the current apps running, i test a few other case this also resolve issues with sometimes the manifest of the updated apps not shown From my experience, don't syn the DNS while having the IPv6 Networ Enabled in Cloudron if no AAAA records in apps or domain I don't know if it happens to anyone else using the Cloudron version 8.x but since I set my networks both work with IPv4 and 6, and it seems everything works normal

@awestenb it means that IPv6 record is not set up. try host -t AAAA my.domain.name . This should be the ipv6 address of you server. If your server does not have IPv6, then in the cloudron setup page -> advanced -> disable ipv6.

Great that you managed to resolve it quickly and thanks for the update here with the solution.

For anyone else out there that is having trouble, I was able to fix this issue by disabling ipv6 within ubuntu. First I did the curl test as mentioned by @nebulon - it worked as expected, but when adding the --ipv6 option it failed. When running "ip a" I could see an ipv6 address was present. Using the link that @playsia supplied, I carried out the steps described in section 1: Disable IPv6 using Sysctl. I didn't need to modify the /etc/rc.local file. Running "ip a" again, there was no more ipv6 addresses shown. I only had these issues after upgrading to V8.0.3 and Ubuntu 24.04.1.

This is handled in support by now. The AAAA records for that domain are not set up.

@mmtrade yeah, that's the problem. IPv6 is not working on the server. Can you also try ping6? $ ping6 ipv6.api.cloudron.io PING ipv6.api.cloudron.io (2604:a880:800:10::b66:f001) 56 data bytes 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=1 ttl=45 time=122 ms 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=2 ttl=45 time=235 ms

Hi All Work it out IPV6 on the OS level Need to make sure that is off ( will look at how to make sure the OS stop using it )

Yup, you are right that Cloudron needs IPv4 currently. IPv6 only setup is coming only in Cloudron 8

@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.