I'm using Cloudron on a home server. I just set this up in the last couple of days, migrating it from a Linode.
I thought I'd worry about dynamic IP later since I find that if I keep the router connected I can go six months without the IP updating.
But oops, I wasn't thinking about that when the new router arrived today. There is a new IP address after router install. I immediately changed all the DNS records manually at Namecheap to point to the new IP.
The URL using the domain name is indeed hitting my server but I'm getting unsafe browsing warnings and when I "go ahead anyway" I get
Forbidden. Your client does not have permission to get this page from this server.
Setting up the static local IP on the server as well as port-forwarding 443 and 80 are all good to go. I can ssh into the server without issue.
It seems like LetsEncrypt needs to run again but I have no way of getting to the dashboard.
When I ssh'd in I noticed that letsencrypt/certbot is not installed on the server. I thought about installing it but thought the better of it since this is clearly controlled by Cloudron magic and so I stopped fussing and came here to get support.
@shai Can you tell us more about your setup? I am pretty sure it's not cert related, because certs are not affected by IP changes.
- Did you change DNS records to the internal home IP or the public IP?
- You can check if the DNS has actually propagated by doing
host my.cloudrondomain.comon your laptop. Does it display the correct IP?
@girish thx. It was really helpful for you to say that you didn't think the problem was with the cert. It got me thinking outside that box.
The problem was that I hadn't properly set up Nat loopback support on the new router (the config for that was different from the one on the old router).
I had to un-tick the box "Stop DNS Rebind" in order to get my site to resolve on my local computers (access from outside my network was fine --which I hadn't realized at first).
There was a big warning when I unticked that setting. Any thoughts on this. It's possible that I have some other local network or router setting that isn't quite right.
@girish wrote "I remember mentioning NAT loopback in https://blog.cloudron.io/installing-cloudron-on-a-home-server/."
That is indeed where I learned about it and was diligent when I set up the old router... but forgot about it it completely when setting up the new one. Always a good idea to work from docs and not just your own head.
@girish. Hi, I knwo this case is cloesed and a bit old but I have a related question.
I use the funciton for the dynamic DNS update and it works fine for the "main" domain, but for my apps, I created manually A-type entries, as mentioned in a documentation and the IP addresses of the apps are not being updated.
Is there something I'm missing or that I can do differently?
Thanks in advance.
@OneTools-Project are you using one of the programmatic DNS providers (like cloudflare, digitalocean, linode, vultr) etc for the app domain(s) ? Cloudron can only update the DNS if it has programmatic access to the DNS. So, if the domains are manual/wildcard, the dynamic DNS functionality won't work.