Looking for help on this.
so I have got my own domain from namecheap together with Premium DNS.
for some reason I couldn’t get it to work.
I tried with no-ip and DuckDNS both work fine, but couldn’t configure the DNS from namecheap.
Port 80 and 443 already forwarded.
total noob here, can anyone describe step by step how to do it?
They have also an option to use dynamic dns to update your IP: https://www.namecheap.com/support/knowledgebase/article.aspx/595/11/how-do-i-enable-dynamic-dns-for-a-domain
If it works with no-ip or duckdns you can just create a cname entry to them from namecheap. But it’s a bit dirty because you use more services than really required (so you are dependent on two services).
Thank you for the answer @tflidd , yes, good tip to link the two.
But first I was trying to have Nexcloud setup with their DNS, do you know where I can use the DNS password that is generated in namecheap? (the last screenshot in the link)
I am not sure, there are tools in Linux like ddclient, I don’t know what is used in NCP, they just have some default providers, you probably have to add the namecheap one. Normally it’s some kind of link/url, username and password or some token.
Adding some info in case anyone else uses namecheap with NCP…
Since NCP does not offer a baked in config option for namecheap, I manually configured these settings using ddclient. If it isn’t already installed, there’s a great tutorial at Raspberry Pi Port Forwarding & Dynamic DNS - Pi My Life Up
Once ddclient is installed (the second section of the tutorial titled " Setting up Raspberry Pi Dynamic DNS"), and you get to step 5 (sudo nano /etc/ddclient/ddclient.conf), these are the settings you want to use specific to namecheap…
# Configuration file for ddclient generated by debconf
password=[password provided by namecheap in Advanced DNS Settings]
Cntl-X, and “y”, then
which should update namecheap with your current IP address. Assuming your ports are correctly forwarded, your domain name should now hit your RPi NCP from outside your network.
You should also now be able to run the LetsEncrypt script under the Networking section of the NCP admin panel. Once you have an SSL cert, you can also turn on Force HTTPS (nc-httpsonly) under the CONFIG section.
My experience was I couldn’t get LetEncrypt to work because I had manually forced https only by including "ssl=yes’ in the ddclient.config file, and it was preventing my namecheap ip address from updating properly. Once I removed that, namecheap updated and I was able to run LetsEncrypt, after which I activated nc-httpsonly).
Hopes this helps anyone else that might run into this issue.