New Cloudron install. No Signup with cloudron.io page

[bbking]

New install of Cloudron on Ubuntu 22.04.1 LTS.
After install and reboot. I had some difficulty getting to the admin page but finally got the page to come up. Now I can't get the Signup with Cloudron.ip page to come up. I keep getting

You are seeing this page because the DNS record of x.x.x.x is set to this server’s IP but Cloudron has no apps configured for this Doman

I tried using https://x.x.x.x and https://my.doman.net and https:doman.net with no luck. I'm trying to access it locally.

Thanks for any help.

[nebulon]

So to be on the same page, you were able to go through the Cloudron setup pages after visiting https://<ip-address> doing domain and admin account setup?

[subven]

@bbking said in New Cloudron install. No Signup with cloudron.io page:

but finally got the page to come up

What have you done? Just waiting? Setup went through 100%? Are all systemd services up and running?

What DNS provider are you using and are the zone settings correct? If you did manual/wildcard, you might missed to set a record.

If you did the domain setup correct, the next step is the admin account creation. You should reach your dashboard at https://my.domain.com. If this is not the case, check services, check DNS and/or wait for DNS to propagate (try from your phone without wifi on just for fun ^^).

[bbking]

That is correct

[bbking]

@subven Hi, I'm not trying to access it from outside. I'm trying to access it local. I do not have wifi setup for that IP address range and cannot use a phone. I have tried different browsers but get the same outcome.

[nebulon]

Cloudron is mainly designed to be reachable from the public internet and works best there. There are some options to get it working only locally and you can read about this at https://docs.cloudron.io/networking/#private-dns but it may be a bit tricky depending on your specific setup.

[bbking]

@nebulon Oh, ok. I look at the document, thanks. So is it possible to access cloudron both internally and externally. I was hoping to test it internally before port forwarding.

[bbking]

@bbking did not make any changes but now I getting error code ssl_Error_no_Cypher_Overlap. The message reads Secure Connection Failed. Cannot communicate securely with peer: no common encryption algorithm(s).

[james]

Closed due to inactivity