Cloudron Forum

@girish thanks for the explanation! Yeah the change happened ~14 hours ago and the TTL was set to 24 hours I reckon. I'll just wait until tomorrow to continue 😉

My plan would have been to lower the TTL a few days prior to the A record, so the caches would invalidate sooner.

@jdaviescoates said in Installed at map.bridport.coop then deleted, then reinstalled on same location: server not found:

Is there a way to flush the NXDOMAIN cache on routers/ computers?

Not that I am aware of. These days browsers also do their own DNS caching complicating things even more.

@girish ok, sounds good to me.

@girish thanks, that worked 🙂

Hey y'all. Used another domain I had that was correctly propagated. It's perfect. Now I gotta wait for my DNS records to update before I do the switch!

@prusaman If the instance has no IPv4, how do you ssh in ? Via a jump host?

@redegelde said in server cloudron install ubuntu 22.04:

The fiddle was after installing Cloudron.

Cloudron tells you not to do so in the banner if you login over SSH after installation ^^ Everything you can do or change is documentated in the docs.

@redegelde said in server cloudron install ubuntu 22.04:

What is/are the good workaround to move from one to other vps

The easiest way for a fresh installation is setting up a new VPS with Cloudron and restore from a recent backup during setup.

For migrating Mastodons user management I can't give you any advice but there are various topics regarding this if you look through the Cloudron forum.

@Jonaz said in You are seeing this page because the DNS record of x.x.x.x is set to this server's IP but Cloudron has no app configured for this domain.:

I updated DNS, and my.cloudron works but not cloudron. which is fine with me. Thanx

As @subven said, wildcard DNS entry does not include the bare domain. So, you have to put cloudron separately in DNS and not just *.cloudron

@girish said in Incorrect error when removing an obsolete alias for a service:

Did you happen to set this up manually?

Hmm, I don't actually know. It's not impossible I guess...

Good to know though, I'll work on cleaning DNS up 🙂

@girish Thank you - now its working again.

@ajtatum Congrats on the success and all the learning! 😎

@Robin Yeah, I think what you did is the correct approach. Given that we don't have a "I know what I am doing button..." 🙂

@nebulon hey there, thanks for your reply, cloudron works now for me. maybe it was a dns propagation issue

@girish said in Cloudron often having problems with connection, "DNS_PROBE_FINISHED_NXDOMAIN", connection times out:

sudo nano /etc/hosts

thanks girish!!!

Just to note, it seems it was a timing issue, where the DNS in this case took longer than expected for full propagation.

I would be interested to know if someone does this outside of Cloudron for their existing business/personal use. Seems like a lot of work (and probably just easier to switch out your NS provider if they are flaky). We use route53 for cloudron.io and AFAIK it has never gone down.

@briankb-0 said in Root Domain Hosts Shopify Site Subs Are Cloundron:

What happens if I add the domain to Cloundron so I can use it to setup sub-domains for NodeBB and Ghost?

When you add a domain:

To validate credentials, the code will add a cloudrontestdns A record and remove this immediately. To configure the server to send emails: If there is an existing SPF record, it is edited to have a:my.my.domain.com . The SPF record essentially whitelists which servers can send email on behalf of the domain. This is NOT destructive, your existing SPF record is only amended. A DKIM record is added under <random>._domainkey.domain.com. This is used to sign/verify emails by mail servers. Because of the 'random' part, it won't conflict with any of your existing DKIM keys If there is no existing DMARC record, we create one with the value "v=DMARC1; p=reject; pct=100". This essentially is a strict DMARC policy not allowing anyone outside the SPF record to send emails on behalf of the domain.

Other than that, it is what @BrutalBirdie said. The bare/root domain is untouched. Cloudron only adds entries when you install apps. Also, if you had a root domain DNS entry already, it will warn you that it's in use, if you try to install an app on the root domain (it does this check for any subdomain).

@humptydumpty Err, I forgot that I already removed those last week as well - https://git.cloudron.io/cloudron/dashboard/-/commit/72ba61ad91d326c3f287a2f538809cc78afcfdc8 . So, this should be fixed in next release.

@nebulon really love you guys for never failing to provide a helpful response, you even have this "rare case" covered in the docs

@Mastadamus From the earlier screenshot you posted, the issue seems to be "Could not establish chain of trust". So, I would investigate that angle (which is DNSSEC related)