Cloudron Forum

@AartJansen for new apps, AAAA is automatically added. For existing apps, go to Domains -> Sync DNS.

@DualOSWinWiz do you think "Encrypt DNS" in your router mean DNSSEC ? If that is the case, an idea is to just disable DNSSEC in unbound instead of for your domain . https://docs.cloudron.io/networking/#unbound .

I figured out my issue. Turns out that even though I read the documentation I made one critical mistake right at the beginning. I had to create my email accounts and the addresses I wanted to work in Cloudron first. Then Install the Snappy mail client and set up the email accounts there second. Once I deleted the Snappy mail client and reinstalled it everything worked. I'm not sure how but this topic can be marked as resolved.

@jdaviescoates said in Regular short getaddrinfo EAI_AGAIN outages: I recently enabled email notifications on my Uptime Kuma and I've noticed there are regular short outages. Something to do with getaddrinfo EAI_AGAIN [image: 1678353141627-screenshot-from-2023-03-09-09-08-30-resized.png] Any idea what's causing this and how to resolve it? Apparently EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error. According to https://stackoverflow.com/questions/40182121/whats-the-cause-of-the-error-getaddrinfo-eai-again Oh, and here it says: EAI_AGAIN means the DNS server replied that it cannot currently fulfill the request. (If you want the hairy details, the RCODE field in the response is set to 2, SERVFAIL.) There is no single solution because it entirely depends on why the DNS server sends that back. Maybe it's overloaded, maybe the network is down, maybe it got the same reply from its upstream server. Learn more In general, the best you can do is wait a while and try again. Hope that helps. I wonder what the specific issue is in my case (perhaps just network issues with Netcup?) Same thoughts. I t has been addressed in the beautiful manner.

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