Weird ip address when setting up in virtualbox
-
Hi all i hope you are well,
I have trieds to setup on two different virtual box systems
one was the new version of Ubuntu and 2nd was the new ubuntu server and i keep getting the same issue , it will install well and then at the end tell me the ip adressAfter reboot, visit one of the following URLs and accept the self-signed certificate to finish setup.
which i know is not hte ip for this pc, i am at a loss and this is the first time i an trying to install
-
-
yes i have but the IP addrsss isnt correct
-
i just did a install on a pc with a ip of 10.14.80.193 and at the end it tells me to go to ip 163.53.144.52 and this doesnt ggo any where
-
Looks like the public IP detection is not working as expected then. Can you open the setup wizard by the correct IP then? If that works, maybe finish that with manual DNS setup, you can change this later to use automated DNS backend once we know it works with manual explicit setup.
-
ok you lost me this is the first time i have done this lol how do i rerun the setup or change the settings
-
when i go to the correct ip it tries to go and then times out
-
@crashmailman might help to understand a bit on what is going on behind the scenes.
Cloudron needs an IP address to configure the DNS. There is also code to check if the DNS is configured correctly (for example, with wildcard or manual DNS). By default, the IP address is detected by calling
https://ipv4.api.cloudron.io/api/v1/helper/public_ip
. You can curl this from the VM and it will return the "automatically detected" IP. In your case, it seems to return163.53.144.52
.In some cases, the above detected IP is not what you want. For these, go to the Advanced Settings in the installation screen . Under Network -> IPv4 , choose a static one and provide your internal VM address, maybe? You have to also select the correct cert provider (in the same advanced section). If you use a programmatic DNS, it's all good, you have use whatever IP you want and get valid certs. If you use non-programatic, then you need a way for port 80 to be reachable publicly for Let's Encrypt to provide certs.
-
ok i got past that which is great am i in the dash board now i get a internal error when i try to create a app passwrod
-