Cloudron Forum

Have you read through https://docs.cloudron.io/networking/#private-dns already? Seems like this outlines your situation.

@LoudLemur As @scooke mentioned, there is a blog about it, but the basic steps are the same. Difference here is opening the ports on your modem (or firewall) manually. The defaults are gonna be 25, 465, 587, 993, 443, & 80 (basic email and web server functionality) though according to that blog post, only 443 is required

@nightmare thx i try that later

Looks like this is fixed upstream with next release then https://github.com/nextcloud/richdocuments/pull/1412

@girish Hey, did just that, and I'm having trouble resolving names AFTER setting them. Cloudron is able to set dns records on aws just fine, but then the check to see if the records are created never gets done. Checked the logs and it's server timeouts. Tried running an nslookup query, to no avail as well.

Kinda weird, seems like the same problem I had on the hosting provider, with unbound, maybe? When I try to sudo, it also says sudo: unable to resolve host ubuntu: Resource temporarily unavailable, but it gets me to root anyway.

I'm a bit beyond my skills here, though, if anyone would like to chime in, I'd appreciate it.

@grimm1369 Let's continue this further at https://forum.cloudron.io/post/44414