Cloudron Forum

That fixed it, the home IP wasn't whitelisted. Thanks for your help

@alphy Is there a way for us to access the server? Not sure why unbound is not resolving but that's the root of the problem. If it's possible to access it, please send us info at support@cloudron.io and we can debug further.

🙌

@girish said in Support for .co.uk Namecheap domain:

I have fixed that too.

You are a wonder!

We had quite a few similar issues with namecheap in the last week on support. Check if your domain really only has no other DNS records reported via host <yourdomain> if there are multiple records reported, you have to ask namecheap support about this.

I figured out the issue - posting here for anyone who encounters the same...
I had not whitelisted my new server's IP address with my registrar (Namecheap). Once I did this, installs and uninstalls are now working.

The error was actually an external error passed from Namecheap, not an internal Cloudron error message 🙂

For namecheap, look at their docs - https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-do-i-set-up-host-records-for-a-domain/

@robi It might not be advertised. Also, I think it isn't a sale, and the renewal price is the same, though I may be mistaken.

@nebulon I just added a new dns record on Namecheap manually. After this action, cloudron was able to add my second domain 😅

I figured it out. There was an issue in namecheap because after checking the ip adress in dnschecker it had two ip addresses: One was the server ip and the other from namecheap. Now there is only one available after chatting with them.

Adding a redirection made things work.

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

@girish No I've not patched manually, I have assumed 😛 sorry
I assumed the latest update was with the CNAME/A-record fix was live.

The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4.

After that the DNS propagation didnt work any longer, as it had done before.

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

@Advika58 Are you a bot?

Nope, there's no AAAA record, just an "A+ Dynamic DNS Record"

Incidentally, I'm about to switch this domain to Hetzner, in any event. Namecheap is ok but also quite annoying from time to time...

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