Cloudron Forum

Is ianoautomatico.online the real domain? If so, it has no nameservers per host -t NS ianoautomatico.online

@nebulon Fully agree, it's really odd that Wix doesn't allow AAAA records in this day and age.

I'll change that domain to noop for now then as recommended, but my preference is to have the logic of the location DNS propagation check change so that domains in manual status can still be successful even if only one IPv4 or one IPv6 address is set rather than both. The noop is for development after all, isn't it?

As long as one of the DNS records exists, that should be seen as successful IMO, since it will work in terms of getting traffic to the site still. There shouldn't be a reason to fail that.

Since porkbun returns an 400 error, I might guess something is wrong with the API call we do. Sadly https://porkbun.com/api/json/v3/documentation is not very detailed here, nor is the error message itself.

Possibly the API requires something else for the naked domain, since the subdomains work apparently fine then. But also I can't find anything mentioned in the docs 😕

Can you check if this might be a record conflict error which just reports as 400? Like do A records for that already exist?

Looks like there is some DNS issue on your system. Can you run the following via SSH:

host -t A api.cloudflare.com

Also maybe

cloudron-support --troubleshoot

@salmonetc said in Changing DNS provider and email with minimal downtime.:

I started trying to "add" the domain. However, I get the following error: Zone not found: 200 {"result":[],"result_info":{"page":1,"per_page":20,"total_pages":0,"count":0,"total_count":0},"success":true,"errors":[],"messages":[]}

Have you added domain.com into cloudflare ? When you create a token also make sure that you add the domain in the Zone Resources list. See https://docs.cloudron.io/domains/#cloudflare-dns

The issue here was server DNS related . The upgrade to Cloudron 8 left the system in a broken state where DNS was not working. Fixing up /etc/systemd/resolved.conf to have DNS servers resolved the problem.

And I would appreciate if this fix get published soon. I need to update it, because I accidently did not renew but delete the API key and there is no way back. (Really not "no bullshit" like years ago @gandi) @girish

I think @nebulon means host -t NS vysvr.org . This should resolve to your nameservers.

@nebulon something is slipping out here...

If it works from host abra-ka-da-bra.mydomain.com command, but does not from Cloudron - isn't it something specific to Cloudron implementation?

Thanks for sharing . Right... our current domain/location configuration follows an all or nothing approach. If one or more fail, it will refuse to bring the app up and will get "stuck" forever . We have a task somewhere to make this more smart and also make the app repair feature smarter but it always gets pushed out as low priority.

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

Great. No further things should be required. Maybe some ubuntu dist-upgrade in the past didn't go as planned and something messed with the unbound installation. But glad it got solved.

It's ok, resolved thank you very much

You can read more about ports and firewall setup with cloudron at https://docs.cloudron.io/security/#cloud-firewall

@TheMoodBoardz YW dude 😉

https://my.hussainwh.info works for me. Note that for https://hussainwh.info to work, you have to install an app on that domain. When there is no subdomain , it's called the bare/naked/apex/root domain .

Right, in the Cloudflare Token UI, you can actually create readonly tokens.

image.png

@humptydumpty thanks for the info! Cloudron should not be affected, no. We don't rely on name servers IPs. Also, I think this is for people having vanity nameservers, which Cloudron does not support.

I should have changed DO DNS to AWS before deleting it then, but I didn't quite understand how to do that either.

I guess that'll be the worry of the next person who runs into a similar situation.

@AmbroiseUnly Good find... Cloudron does not support IPv6 only setups yet. But it's coming in the next release (Cloudron 8).