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?

Hello @davejgreen @davejgreen said: I tried the rsync attempt last week, then I erased everything on the new server to try again. Ah! Thanks for the clarification. I indeed did not understand you correctly. @davejgreen said: Then when I start the restore from there, doesn't this happen on the new server? https://docs.cloudron.io/backups/#dry-run-restore Dry run skips DNS updates. The new server won't be publicly accessible - you access it using /etc/hosts entries on your local machine. Dry run will not change any DNS records. This also means, as soon as you hit the restore with dry run, when a redirect happens to your restored domain, you DNS will resolve to your production server. This is why you need to update your local device /etc/hosts to prevent this. If one does not do that, you can have a mixed view of the dashboard of cached content, the old server serving stuff and the new system serving stuff. @davejgreen said: The first error message started with "Access denied." which makes me think the problem might be related to file and folder ownership and/or permissions, as I am often confused by these. This could be an issue. With this partial mount that is failing, can you review the access to that mounted NFS?

Hello @ntnsndr and @valexico That two times a Hostinger set up is having the same issue is not a coincidence. Still, I am not sure what is going on. The file in question exists. So why does the docker daemon suddenly act in this way.

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

Glad you found the issue and thanks for sharing the fix.