@qimmiq Just quickly reading the upstream docs at https://www.namecheap.com/support/api/methods/domains-dns/get-hosts/ and also the code, it looks like maybe the issue is that the domain is completely empty in namecheap? Can you add a DNS entry in namecheap (any dummy entry is fine) and try if it works after that? If it works, then I think we have to fix our code.

Ahh there was a "URL Redirect" record in Namecheap that was causing the problem. It wasn't obvious because it didn't have the IP address in the record but once I deleted that it worked. Thanks!

@mastadamus If you use namecheap API, you don't need port 80. This is because Cloudron will use Let's encrypt DNS automation to get certs. Note that this will require you to sometimes type "https://" explicitly in some browsers because some browsers will default to connecting on port 80 and then the redirect will take it to the https site. In addition, Cloudron has HSTS, so future connects will directly be to 443 and no redirect dance.

@girish Im tracking with what you saying but the API didn't create any A records. In fact i couldn't get to the dashboard at all until i created that * wild card. I still have no idea why its not redirecting to HTTPS if i put int http://www.mydomain.com. The only files the API created in dns were 2 txt records and a testcloudrondns at 127.0.0.1

@girish
So i'm pretty sure I figured it out, but only time will tell.

Both of these domains the initial domain propagation and automation through cloudron's domain controller (from the main dashboard) all the way to the deployment and installation to applications was rushed. The initial rushing of it meant that the install got either halfway finished (or a migration from one original install to the new domain) was botched in some way.

Manually removing all DNS records doesn't work and cloudron gets all confused. The way I was able to remedy this and fix it all was to delete all DNS records and add an A record for my server: host @ & www respectively, two entries. So it'd be the following

@ my.server.ip
www my.server.ip

-Remove all other dns records.
-uninstall

I still haven't tried it out yet.

@atrilahiji said in Installation gets stuck in "checking DNS" step:

@jakobgreenfeld Oh I missed the bit where theres only a txt record. Add an A record pointing my.domain.com to your IP. I've had nothing but trouble with Namecheap's API for configuring everything so I've started doing this:

A record for *.domain.com
A record for @

That did the trick! It's working now. Thanks!

@brutalbirdie Yeah, I tried their Ghost hosting once, until I found how far behind their version updating lagged, which led me to discover Cloudron 😄

@shai Yeah, it's tricky 😊
Thanks for your this hint, anyway, here's a screenshot for lazy ppl

Screenshot 2020-12-10 at 01.05.01.png

Screenshot 2020-12-10 at 01.07.01.png

@girish feeling lazy, will wait for the official update 🙂

@bossbarnes07 It seems an 'A' record with the subdomain 'my' is missing. It should point to your IP (209.97.x.x). Cloudron should have added this automatically, I wonder why it didn't get added. Can you add an A record manually and then go to your server and do "systemctl restart box". You can then visit https://ip again and re-do the setup.

@atrilahiji I use Namecheap too, decent service but equally the Cloudflare free DNS services is pretty solid and not had any trouble with that & Cloudon. Just mentioning in case you got stuck or hadn't compared that option.