Cloudron keeps setting up during installation
-
Hi, I entered domain and chose Manual DNS provider. Now I can access the installation on the IP as well as on the domain.tl (also on my.domain.tl) After few days I keep getting "Already setting up or restoring" sign when checking the installation process. How long will the process take? What can be wrong?
-
It should not take hours at least. It heavily depends on the download speed of your server. Can you check the install log file at
/var/log/cloudron-setup.logon your server to see what is happening?@nebulon Thank you for your response. I'm sorry, but I'm quite new to SSH server connection, could you please describe full path to the log file or commands I should write? I tried cd home/myusername/var/log/cloudron-setup.log but it writes "No such file or directory" (I replaced "myusername" with my real username, of course)
-
Since you already started the install,
/home/yellowtent/platformdata/logs/box.logwill have the post-installation logs. You can also dosystemctl restart boxand click refresh on the browser to redo the DNS setup.@girish @nebulon Ok so I found it after all. This is the mistake it makes (I changed the addresses):
xpecting "SSH IP address" Match false
2022-03-03T19:40:19.817Z box:dns/waitfordns waitForDns: my.domain.tl at ns ns.domain.tl: not done
2022-03-03T19:40:19.818Z box:dns/waitfordns Attempt 507 failed. Will retry: ETRYAGAIN
2022-03-03T19:40:49.819Z box:dns/waitfordns waitForDns: nameservers are ["ns.domain.tl","ns.domain.tl","ns.domain.tl"]
2022-03-03T19:40:49.920Z box:dns/waitfordns resolveIp: Checking if my.domain.tl has A record at IP of NS
2022-03-03T19:40:49.930Z box:dns/waitfordns isChangeSynced: my.domain.tl(A) was resolved to Public IP at NS ns.domain.tl (IP of NS).There might be some misconfiguration of the IP adresses. One is for SSH and another is public. Do you have experience with that?
-
@girish @nebulon Ok so I found it after all. This is the mistake it makes (I changed the addresses):
xpecting "SSH IP address" Match false
2022-03-03T19:40:19.817Z box:dns/waitfordns waitForDns: my.domain.tl at ns ns.domain.tl: not done
2022-03-03T19:40:19.818Z box:dns/waitfordns Attempt 507 failed. Will retry: ETRYAGAIN
2022-03-03T19:40:49.819Z box:dns/waitfordns waitForDns: nameservers are ["ns.domain.tl","ns.domain.tl","ns.domain.tl"]
2022-03-03T19:40:49.920Z box:dns/waitfordns resolveIp: Checking if my.domain.tl has A record at IP of NS
2022-03-03T19:40:49.930Z box:dns/waitfordns isChangeSynced: my.domain.tl(A) was resolved to Public IP at NS ns.domain.tl (IP of NS).There might be some misconfiguration of the IP adresses. One is for SSH and another is public. Do you have experience with that?
One is for SSH and another is public. Do you have experience with that?
Do you mean you have one public IP and one private IP? And you have set the DNS to the private IP? Or do you mean you have to different public IPs and want to choose a specific one? Also, is this a home server setup?
Depending on your response, we have to configure the IP setup accordingly. If you do
systemctl restart boxand go back to the DNS setup screen, there you will Advanced at the bottom. If you click on it, you will find the various options as documented here - https://docs.cloudron.io/networking/#ipv4 . Also, if you want to set the DNS to private IP, you won't be able to get Let's Encrypt certificates. You then have to use "Self signed certificate" in the Advanced section. -
One is for SSH and another is public. Do you have experience with that?
Do you mean you have one public IP and one private IP? And you have set the DNS to the private IP? Or do you mean you have to different public IPs and want to choose a specific one? Also, is this a home server setup?
Depending on your response, we have to configure the IP setup accordingly. If you do
systemctl restart boxand go back to the DNS setup screen, there you will Advanced at the bottom. If you click on it, you will find the various options as documented here - https://docs.cloudron.io/networking/#ipv4 . Also, if you want to set the DNS to private IP, you won't be able to get Let's Encrypt certificates. You then have to use "Self signed certificate" in the Advanced section. -
@girish Hi, thank you for support. Finally I have found a solution to that with my friend. Thank you.
