@davejgreen said: on the new server, I created my user before installing cloudron FYI, afaict all the issues you've faced were caused by you doing something that isn't needed e.g. the above creating a user, plus editing hosts files stuff mentioned previously. I've migrated my Cloudron server probably 3 or 4 times without any issues

@valexico issue is not specific to hostinger . Ubuntu has pushed a new kernel which is causing problems with Cloudron's firewall. We are making a new release to workaround this issue.

Hello @ruihildt I just visited the website and there is a big banner: We are aware of an ongoing issue with our API that is resulting in 503 error code returns. This is currently being investigated and we hope to resolve this soon. Domain and account management from within Porkbun.com is still functioning normally. Oink! So I think we can wait for that to be resolved.

Hello @mathieuepitech Okay, so the network issue is resolved by the applied patch. When you configure your docker registry in the Cloudron Dashboard, is there any error when saving?

Just tried updating the CLI via npm install -g cloudron@8.2.1 and it seems to work now Thanks for looking into it.

This too might be related to the ubuntu kernel issue. Can you check the output of uname -nar ?

@tlem4 The dashboard issue is related to the latest ubuntu kernel having a regression. You are running 110 which has a bug . See https://forum.cloudron.io/topic/15265/unusable-application/39

Ok I did restore a previous state and then proceeded to update. This instance was not critical so no data loss

Hello @mendoksai That checks out with our other topic. A RAID failure can cause such a catastrophic issue.

From that error log it seems that other app is sqlite related: "[DB] INFO: Database Type: sqlite" Is this all related to the same rocket.chat app uninstall issue or some other problem? For mongodb not running, with latest Cloudron we stop unused services, so this sounds actually correct.

Needed to run cp /etc/docker/daemon.json /etc/docker/daemon.json.bak printf '{}\n' > /etc/docker/daemon.json systemctl restart docker systemctl status docker --no-pager As per the Hostinger AI, there were an issue aroundlog-driver in conflict

Thanks for the answer - I'll check until monday. Yes, I used AI but I personally checked and validated and understood the problem before posting.

@james Yes, this is a great find. Thanks a lot for your cooperation. In email service’s logs no any log... Whenever you want, I can reproduce issue and I can send you raw log. Keep me posted.

@imc67 So were we using the same rules from @d19dotca ? For now I removed from all istances, but in future I want to keep only rules who works in local, not requiring any outbound connection.

This is now fixed for the next release with https://git.cloudron.io/platform/box/-/commit/a4ea80cf5eb26b08462430111e8b6f75175e749d

@james said: I suspect that this might happen in the backup process and thus changing the amount of files. I think that's actually unlikely in this case because I'm pretty much the only active user of this instance and it backs up while I'm asleep. But I'll try to give enabling maintenance mode a try to see what we can see...

Ah, actually, I think it's likely just that my Firefox is glitching out as it's everywhere for me right now.

Similarly described in Unusable application: Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all. I tried upgrading to Ubuntu 24.04 and it seems to work as expected now (versions file + icon on the same server without issue).