Cloudron Forum

Great that works I'm backup and running thanks for your help.

The posted error logs do not seem to be related as far as I can tell. But anyways if some food solves it, even better, hopefully also stays that way

Glad it worked in the end. Otherwise for reference please follow the instructions at https://docs.cloudron.io/troubleshooting/ to troubleshoot this.

Disabling Cloudflare seemed to work. Thanks.

After a reboot, it seems fine for now. Let’s see if it persists

@BrutalBirdie Thanks for providing that information. Much appreciated!

@mpeterson0418 I found that the root file system was either corrupt or "reset" . I don't know and unable to guess what happened to the disk (maybe power outage?), but I can explain what I did to recover. I found host MySQL to be empty. The box database had tables but was empty. The fact that it had tables meant that migration scripts were run on this . Maybe /home/yellowtent/box/setup/start.sh was run at some point on an empty (i.e no tables even) database. Usually, the last well known mysql dump is located /home/yellowtent/boxdata/box/box.mysqldump . One can also find the same inside the latest backup (inside the box.tar.gz) . To "restore", mysql -uroot -ppassword < /home/yellowtent/boxdata/box/box.mysqldump Then I found, docker won't start. In Cloudron, containers are throw away infrastructure since data is stored outside the containers. I tried cloudron-support --recreate-docker but this did not work. On investigating further, it seems /var/lib/containerd was also corrupt . Corrupt here means no docker commands work. So, I removed that directory as well. After that, cloudron-support --recreate-docker worked. The best way to migrate in Cloudron is not to do the above but instead just restore from backups. See https://docs.cloudron.io/backups/#move-cloudron-to-another-server .

@uwcrbc said in My App domain filter with unused domains / external domain: At the moment, filtering per domain shows the list of domains configured on the Cloudron server regardless whether there is an app using it or not. Right, this is how it works currently. The same is possible for All States / Groups as well. Just because there are no apps to list, the item does not get hidden. This can be confusing or not depending on user expectations. It also does not allow to filter for proxy app'ed "external" domains. In the common case, the proxy URL is an IP address and not a domain. In fact, the thing is a URL and not a domain (so we cannot put it in the filter).

cloudron.io - this is Cloudron's website (the company) console.cloudron.io - this is the place where Cloudron's customers login to manage billing. you cannot manage apps or anything of that sort here yourdomain.com - this is the domain you gave when you installed Cloudron, the software, on your server. IMPORTANT: cloudron the company has no access to your servers. Cloudron the software is entirely selfhosted and only you have access to the server. my.yourdomain.com - this is your server's dashboard. this is where you manage apps and other things my.cloudron.io - this is actually Cloudron the company's, cloudron installation. you should not (and cannot) login here! With this in mind: When attempting to login us assigned IP it would redirect to my.cloudron.io. this cannot ever happen. how would I reach login when IP Changed/DNS is not available If IP changes, go to your DNS and then just change the IP address of my.yourdomain.com manually to the new IP. Are you talking about dynamic IP here? If so, use the Dynamic DNS feature. It will automatically update the DNS with a changing IP. Finally, if DNS itself is not available, I guess you have to use /etc/hosts . See also - https://docs.cloudron.io/troubleshooting/#unreachable-dashboard

@philkunz

@privsec said in Can not restore/reinstall cloudron: I have set up cloudron to use the same 7.5.2 version of my current install. On the new install after I update the DNS records to the new IP address, I get this After the cloudron installation, did you do the domain/dns setup and create an admin account? If so, you should not do that. Setup new server with cloudron --version 7.5.2 Go to https://ip For good meaure, I would power off your old server. This prevents any dns caching issues wrt my.domain.com pointing to your old server. Start restore from the setup view Cloudron will automatically navigate to https://my.domain.com 'Already activated' means that you already setup admin account on that server. After that, you cannot restore anymore for security reasons. For example, if you find a cloudron installation in the wild and try to restore, it won't work. That route is completely locked.

@girish Yes Everything is back to normal. Thanks a lot !!!

Thanks @girish for the quick reply. I'm getting there.

Already fixed bugs are the best bugs

Ok. I will doublecheck this. Give me a few hours for this. Thanks for the moment Update: Solution work fine! Thanks a lot.

@girish Are you saying that the user manually updated the node version, which I assume is the one that Cloudron that installed, and it installed that version so that it works, but then had this issue because they did something that they aren't advised to do (which is manually update)??? It might be worthwhile to highlight the fact (on the homepage or in the install instructions) that Cloudron manages the VPS for the user so that new users don't keep doing this, _running apt-get update on their own!

Yes, see the instructions at https://docs.cloudron.io/troubleshooting/#expired-domain . If that's too technical, please feel free to mail us at support@cloudron.io and we can help switch it.

Hi, brilliant - that was the solution thank you so much kr, Andreas @girish said in Forgot primary domain: cloudron-support --admin-login

@matthewdykstra issue is somewhere on the DNS side. Is that domain using Cloudflare? If so, for a start I would disable Cloudflare proxying for my.mjsiebolt.pro and just make that point to your server (so a single A record). Once that starts working, you can re-enable Cloudflare proxying and see.

@Linda-Mendez Not easily. I guess you can hack on the dashboard code to come up with something but this will get overwritten during updates.