Cloudron Forum

IMO having a backwards compatibility is nice but to what extent? Just checking network6 var and if empty return a useful error would suffice for me.

@girish IPv6 is enabled on the server but not "in use", since some domains that are added manually don't have v6 and I don't want to run into troubles. Those are mostly Hetzner Cloud servers.

Thanks! Adding the line solves the issue. Time to roll out the update!

@BrutalBirdie think you missed Edit2: Yep its works fine now.

I contacted Namecheap support and they helped me out with that part. The domain setup is done now! Thank you for the help!

Dangit! So a reboot was the solution again.

@thoresson said in SPF failure for IPv6 – but IPv6 is disabled on my server: @joseph No idea how, all I did was to take a break from this to cook dinner, but now it works. Probably just took a while for the changes you made to propagate

@hakh looks like IPv6 connectivity in your server is not working. Does ping6 ipv6.api.cloudron.io work for you?

Yeah can confirm, and thanks for the help diagnosing. I wasn't given any advanced notice of the SMTP block, it was hidden in release notes somewhere. This is now unblocked.

Thanks, Looks like IPv6 is not on by default on Hetzner.

It's not, no. 8.3.2 only has a single change to fix postgres to support immich .

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

I use netcup too, I disabled IPv6 on the server entirely and since everything has been working with no issues. Though disabling IPv6 persistently on reboot was not straightforward and had to be done modifying netplan config, see above on the thread (https://forum.cloudron.io/post/102554).

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