Unable to finish setup in Browser
-
When I installed cloudron on Linode & AWS Ubuntu Server everything worked fine & I was able to visit the IP address in my browser and accept the self-signed certificate to finish setup.
I got 2 free apps working perfectly & I love using them.
Unfortunately when I try do the same at home on premise the IP address wont work & I cant finish the setup. Any advice on how to get this working on my home server? Appreciate any advice or point in the right direction. Thank you. -
@molinaire you need to temporarily forward port 80/443 to the install so it can finish setup.
-
B BrutalBirdie referenced this topic on
-
I'm having a similar issue. I wasn't sure if I should post a new post, but I saw a post linking here, so I'll ask here first. I've been using cloudron with guacamole at my old place and it was working just fine. I recently moved and changed ISP's. My network and IP's have obviously changed since, so I tried forwarding my ports 80 and 443 to the new IP address for my cloudron install, but I kept getting "You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain." when i go to the local IP, and I get "This site can’t be reached, Public IP took too long to respond." or my.domain.com took too long to respond.
I decided to just try to start fresh, did a fresh install of Ubuntu and reinstalled cloudron. I went to the IP address listed in the install, but same issue, not able to connect. The local IP still says "You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain." and the public IP is still giving the same error.
After a while of just trying the IP's I WAS able to see my setup page just once. I added my info and was able to see the app store once. I tried to install guacamole and it failed. I tried to re-install it but it didn't work again. After that I lost the ability to see the app store again or see the original set up page, and now just get the same errors when I go to the local and public IP/domain name now.
I can sign in to cloudron.io and see under "cloudrons" that my domain is there now, (which, before I reinstalled Ubuntu and Cloudron fresh, when I logged in it was not showing anything there) but when I click on it, it takes me to my.domain.com but still says "This site can’t be reached my.domain.com took too long to respond."
I'm sure there's something silly and simple I'm doing wrong, but I've been trying for two weeks now and I can't figure it out... also I'm really a newbie/hobbyist so my apologies in advance if its a really easy/silly question.
-
@saphirata this does sound a bit like you are getting new public IP addresses from time to time and thus the DNS records go out of sync. Are you using one of our automated DNS backends for that domain? In this case make sure to also use the dynamic DNS feature https://docs.cloudron.io/networking/#dynamic-dns
So for a start can you verify the your current IPv4 actually matches the DNS records you are seeing (note that there might be caching for quite a bit depending on TTL set on the DNS records)
If you visit the raw IP and you see the placeholder page talking about Cloudron, than at least we know you can reach there and the system is likely up and running fine, so that is a good start and likely just a DNS issue then.
-
@nebulon said in Unable to finish setup in Browser:
this does sound a bit like you are getting new public IP addresses from time to time and thus the DNS records go out of sync. Are you using one of our automated DNS backends for that domain?
This is exactly the case. I did switch my IP address in my DNS settings (I'm using cloudflare) but I did notice my ISP has reassigned a new IP, so I've updated that, and I will take a look at the DDNS docs and try to set that and figure that out next!
@nebulon said in Unable to finish setup in Browser:
If you visit the raw IP and you see the placeholder page talking about Cloudron, than at least we know you can reach there and the system is likely up and running fine, so that is a good start and likely just a DNS issue then.
When you say Raw IP do you mean the local or public? If I go to public, it still says cannot reach site, but I'm assuming thats something to do with DNS I still need to figure out. If I go to the local IP it does show the placeholder page for cloudron saying there are no apps yet installed here.
So my understanding is I have to make sure I make my DNS settings (through cloudflare) point my.domain.com to my public IP address and then port forward 443 and 80 to the local IP. Which as far as I can tell I've done. But I seem to keep ending up only reaching a placeholder page through local IP but nothing else. -- Sorry, I'm still really new to setting up servers and networking and using this as a learning project.. but I think I'm learning slowly lol. Thank you for your reply, and for reading
-
@saphirata if your IP of your ISP connection (local ip) keeps changing, then you need to keep the DNS records in-sync. So for your use-case it means you have to keep adjusting the settings in Cloudflare.
Maybe for a start you could disable Cloudflare proxying and use it normally as a DNS service, then configuring your domain in Cloudron to use our Cloudflare backend and enable https://docs.cloudron.io/networking/#dynamic-dns
