Cloudron Forum

Ok. I will write to support. Thank you

She back on line ..... remove DB and now she up this line got me 2nd time what the sic ? it just password not sic that was the old password if I recall Change the root password to password (sic) - and I had to rerun the cloudron-support --troubleshoot but she back think it was not low space but may be time to add ( sure I can scrip or even take box offline by doing a stop ) at 5% space take the system offline or pause ( sure docker can pause ) hyper v does it if see low pause ( or email @ 10 % then pause at 5% ) think it time to re billed time let see how easy it is to move to a new VM under promox look at the space had backup from 2022 in /var/backup remove that drop back down for 87% to 63% [image: 1782209664835-8f7809b8-08ed-496b-8259-0a6ebae8ba6f-image.jpeg] thanks @james and @nebulon

@james, I got it back up. Working on getting everything updated.

Good catch. nc is not part of the base image it seems (not explicitly). I have replaced that code with bash logic.

@joseph Thank you. That seems to have fixed the problem.

IMO having a backwards compatibility is nice but to what extent? Just checking network6 var and if empty return a useful error would suffice for me.

This most likely just looks like a port forwarding issue. Are port 80 and 443 forwarded properly to your VM?

Reinstalled from a backup. I lost a few apps but the critical one are back with all data. This post can be closed. Thank you all for fast replies.

@im-fabian can you reach out at support@cloudron.io ? I think we have debug further with access to the server. thanks!

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

oh nevermind. I read the "you can try" instructions in the output sudo ln -sf /usr/local/node-20.18.0/bin/node /usr/bin/node sudo ln -sf /usr/local/node-20.18.0/bin/npm /usr/bin/npm sudo systemctl restart box And that seems to have gotten it going again. /phew

@berryd great you sorted it out!

@jtippetts atleast the dashboard seems up now. Not sure why the machine shutdown itself though.

@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 .

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.

you can check it your self with GRC shields up https://www.grc.com/x/ne.dll?bh0bkyd2

Thank you @girish , this worked. For those coming through in the future note that cloudron-support may ask you to reboot and run again, keep an eye out for it.

I didn't uncover the cause, but I believe it was related to the VM running out of disk space. I wound up reinstalling. I let a large upload job run unattended and wound up completely filling the drive on the VM running Cloudron. I then cleared about 100 GB, rebooted for good measure, resized the partition using parted, expanded the filesystem, rebooted again, and let it run normally for a few days. That's when I noticed I couldn't install any new apps. I suspect that either the partition / filesystem resize or the disk being full broke something internally. In hindsight I wish I had taken the time to dig into the logs a little more and see what was happening. But this is likely a direct result of my unusual environment fault.

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

Thank you very much @girish, you rock!