@mendoksai said:
Quick update — I just noticed cloudron-support --troubleshoot was reporting:
[FAIL] Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js
This is a bug in the tool and not a real problem. It's fixed in 9.1.5.
Not sure if cloning is exactly UI-friendly here. The user intention is to add another domain, which is a separate action than cloning. You'd assume you perform an action that is separate from other domains, I'd say.
For backup sites, I am more with you: There it makes more sense to use the same site, but change a detail.
Nevermind, it was just a matter of being patient. Everything was set up correctly.
For anyone else using Namecheap, it takes a minute for the DNS to sync. Give it some time (quite a bit more than you think) and it'll work.
Yeah, I don't have the original, because I repaired this manually already, but that is basically it - the CNAME was a standard of Porkbun pointing to their server.
Well, it's solved quickly, albeit manually.
@james I could not get it working at all, so I switched to use Sendgrid instead since we have an account and that is working fine. The issue is that I am using Cloudron as a VM inside of Truenas Community 25.04.1 and it is Truenas causing the issue and I would have to make some major changes and I don't want to affect the File Server side by doing this.
Hello @Shai
The second level domain, also known as @ in most DNS providers e.g cloudron.io has a different propagation time then third level domains aka. example.cloudron.io.
This could take up to 24 hours or more, depending on the hosters default TTL for the domain or what you've set.
Might even be resolved now when you retry it after 7 hours.
Do you have the "Enable proxying" flag enabled in the Domains -> Cloudflare configuration ? This whole discussion only applies if you have that flag changed. Cloudron does not touch the proxying flag if that is disabled.
When enabled, it will set the proxying flag when adding new cloudflare DNS records. This is set only when adding and in all other situations that flag is left untouched . It does this for both ipv4 and ipv6 records.
So it turns out DNSSEC is the problem. Unbeknownst to me, the previous registrar had enabled DNSSEC by default, when I transferred the domain some time ago, the records were not removed when the new registrar updated the nameservers. As they don't have DNSSEC management and my DNS resolver doesn't validate DNSSEC, I didn't notice anything was amiss.
Thank you for your help with this!
For those who hit this 8.2.4 is out . It's marked as unstable just to not have everyone update at the same time but it should be stable and has the fix for this issue.
@scooke said in Notes on domains?:
Christmas has passed; that same day was my birthday!
Happy Belated Birthday! You have the same birthday as my fly expert friend Erica McAlister - check out her books here https://www.ethicalbooksearch.com/uk?query=Erica+McAlister
