Also, note that changing the nameserver sometimes takes a bit of time. So, you might have to wait a bit between step 2 and step 3.

@PRajShar To clarify what this error is trying to say: Let's assume that you have an existing website app (i.e external to Cloudron) on app.domain.com. Now, you go to Cloudron and try to install an app in the domain app.domain.com. Cloudron will detect that the DNS already has an entry for this and fail with the above error. To fix this, go to your DNS provider and remove the app.domain.com entry. Then in Cloudron, click the Repair (wrench icon) and it should work. Alternately, just use another subdomain app2.domain.com or something.

Done, added notification for the next release.

@murgero Thanks for reporting, this was indeed a regression. Fixed now for the next release.

Indeed, missed that. Just making a blog post for 4.1 release which will include it.

I tried to reply via your support email already. The cert on your domain looks valid to me, so please clear your history and cache locally for that domain first.

From what you wrote, are you running the server behind your home server in a NAT by any chance? Yes indeed. @uiharu Does host cloudflare.com 127.0.0.1 work? I'll update later

Had this issue on support couple of times already: https://git.cloudron.io/cloudron/box/issues/610

Oh I pasted the wrong link apparently, fixed it now.

@uiharu Ah, thanks!

@TheNils For new domains, the NS record sometimes takes to propagate. That error message means that it's not propagated to the Cloudron server yet. You can try this: SSH into the Cloudron host -t NS mydomaine.net (This should not display NXDOMAIN) If the above works, it should work on Cloudron as well. If not, can try sudo systemctl restart unbound and then try adding the domain again? We will improve the error message to be more descriptive (https://git.cloudron.io/cloudron/box/issues/548).

It works. Thanks.