Namecheap API and Home server with Public IP HELP
-
I'm trying to install cloudron but my install keeps getting hung on "waiting on DNS" during the initial setup. I've whitelisted my IP and gotten an API key. My home router has DDNS already. Is there something I can do to make this work? I can't setup the DDNS in cloudron till i get past this step. I've tried adding two a records for 1. *.mydomain.com and 2. @ and when i refreshed I've seen that the cloudron added 2 txt records but its still stuck in the "waiting for DNS loop" How long does this take usually?
-
@mastadamus port 80 needs to be reachable in your firewall.
-
@mastadamus Usually, it only takes a minute. Can you see what it's waiting for in
/home/yellowtent/platformdata/logs/box.log
? Also, is this a new domain (or recently moved to namecheap) ? -
@robi It was. I got on live chat with name cheap and "magically" it started to working. After me letting it spin for about 45 mins. I did add a * A record. the API dns method only added txt records.
Now the issue i'm having is though, nothing is redirecting to HTTPS my.mydomain. if i type in mydomain.com it will just got to http version of that and i get "you've found a cloudron in the wild" so im thinking cnames? -
@mastadamus Does the redirect issue happen with
http://mydomain.com
orhttp://my.mydomain.com
? If it's the former, this is expected. You have to install an app on the bare domain, for Cloudron to serve up something there. For the latter, it will redirect tohttps://my.mydomain.com
, does it not? -
@girish You guys are awesome. just and fyi. very quick and prompt help. Thank you. I didn't think it was because i was getting a "insecure site warning flag thing" but it was actually due to the cert. I renewed certs and everything is working great as far as it only doing https. The only question i have is why is my certificate showing untrusted?
-
@mastadamus sorry i was wrong If i don't block port 80 on my firewall it doesn't redirect to https if i type "www.mydomain.com" it doesn't redirect to https://www.mydomain.com
-
@mastadamus Do you have an app installed on "www.mydomain.com" ?
To clarify a bit:
- You have setup wildcard DNS (*.mydomain.com) to point to cloudron. Because of this, you can type
anyrandomsubdomain.mydomain.com
and it will hit the Cloudron server. Though of course there is nothing on Cloudron there and it will just show you the default "cloudron in the wild" page. - Because you use namecheap API, you don't need the
*.mydomain.com
DNS entry. You can remove this from the DNS. - When you install an app, Cloudron will setup the DNS automatically (via the namecheap API) and also get the certs automatically (via Let's encrypt).
- Finally, "www" and "" are all just subdomains of
mydomain.com
. Unless you install some app on those subdomains, nothing will appear when you visit those domains on the browser.
Hope that clarifies.
- You have setup wildcard DNS (*.mydomain.com) to point to cloudron. Because of this, you can type
-
@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
-
Hello Friends,
Setting up a Home server with a public IP for Namecheap API is a great idea! Ensure you have a static IP, configure port forwarding on your router, and secure your server. Namecheap's API allows you to manage DNS and domain settings programmatically, making it a powerful combo for hosting your services. Good luck! -
G girish marked this topic as a question on
-
G girish has marked this topic as solved on