Seems like a connectivity issue. I assume you can connect via the browser. Is your system using a http proxy or anything like that? Does curl https://my.domain.com work ?

@scooke I wanted to clarify my concern about this issue. Previously, after a system reboot was completed, the "reboot" button in notification would automatically fade to grey and disable the reboot button. This functionality appears to have changed (button remains clickable and red). The color difference you mentioned wasn't actually my concern. At this point, I understand this is the new expected behavior, so I consider this matter resolved.

Well, apparently the only way to "fix" this, is to docker stop the yellow services Mail / Mongo / Postgres / MySQL and then restart them in the dashboard and they start up succesfully, and then you can start other apps that have been stopped.

Thank you the problem is solved.

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

My problem is solved now using this command: sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv Thank you DeepSeek hehe

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

As I have a similar and bigger issue, I created a new thread: https://forum.cloudron.io/post/101241

@SansGuidon I think your approach is the best as of right now. We will have to add automatic restart built into Cloudron at some point.

@timconsidine thanks, I have added a validation check now.

@nebulon Yes, I had a look of Cpu load and it was by msql, but now seems to be ok

@moktan.bj does this not work ? what message do you get if you try ? [image: 1738538867547-screenshot-2025-02-02-at-23.26.06-resized.png]

For those who hit this 8.2.4 is out . It's marked as unstable just to not have everyone update at the same time but it should be stable and has the fix for this issue.

@jdaviescoates Yes I had done that a while ago

@humptydumpty said in At home self-hosted Cloudron - migrate to larger main disk. Advice and sanity check my thoughts.: Having a GUI is preferable. I would also have recommended dd Something I havent used in ages, but i think would satisfy the gui criteria is https://clonezilla.org/

It's fine to keep the post around, helps others in the future @igaudette said in Custom app database wiped after migration: Looks like the backup is not backing up the database of the custom apps, is it possible? FWIW, the backup strategy is the same for custom apps and apps from app store. The only difference is that one uses a customer docker image/registry and the ones from the appstore use a appstore provided docker image/docker hub.

The best and easiest way is to use a single larger VPS to handle the different traffic apps. If uptime and stability are more matter in your case then you can run one app per VPS in critical services. Also, you can do a hybrid approach. The hybrid approach contains the separation of resource-heavy apps and low-traffic apps ones together. It can also work well. If you consider the cost then a single VPS is easier to manage and allows flexible resource allocation. But, it creates an issue like one application could impact others. Multiple smaller VPS instances provide better isolation and redundancy to one service that stays online if another fails. I prefer to use a single 4GB vps to a single app mostly. Still, if you want to use one vps for all apps then you have to prefer at least 8GB vps for sure.

Can you check if basic DNS resolution works ? See https://docs.cloudron.io/troubleshooting/#dns-resolution . Also, are you hosting at home or some private network (these have complications with loopback checks).

@osobo the power of the forum, thanks are due to @jdaviescoates and all those who went before on this issue.

@joseph said in Frequent Email is not configured properly notice: Maybe DNS is periodically failing on your servers. Do you know which DNS servers your server is using? You can use resolvectl to figure this. Thanks for the explanation! my DNS servers are : Current DNS Server: 1.1.1.1 DNS Servers: 1.1.1.1 9.9.9.9