Cloudron Forum

Thank you @nebulon

@girish , maybe this is a good feature for 9.1?

@jcalag said in uninstalled app not deleted: Errors were encountered while processing: nginx-core nginx-common It can't load the dashboard because nginx is not running. You can try some of the methods here - https://superuser.com/questions/1386209/how-to-solve-this-dependencies-apt-fix-broken-install

@jdaviescoates Had some issues with Github, will post on my gitea sometime tomorrow

@girish I see it now, that’s great, thank you!

I have increased the solr indexing timeout and reduced the indexing batch size. Maybe it helps on slower machines .

@timconsidine Thank you for your fast response. No worries. Your documentation is very useful: https://git.cloudron.io/timconsidine/cloudron-moltbot/-/blob/main/POSTINSTALL.md?ref_type=heads so perhaps it will help me make OpenClaw work on DokPloy. I'll test additionally if I can self-host an LLM via Ollama on a Cloudron VPS and connect it to OpenClaw

Hello @jdaviescoates The whole profile is gone https://github.com/stalecontext/ maybe he has renamed his github account?

Will do, James. I have not been able to recreate the held lock issue. I was starting/stopping jobs a fair bit at one point, and can't... be precise about where in the backup cycle those cancellations happened that a cleanup might not have happened. I will watch for it in the future. When I said there was no RAM pressure, I meant that was true for the server. However, my jobs all had 1GB of RAM. Your suggestion clued me in; because that value must be set after you setup the backup job, I had never noticed it before... or, not realized how critical it might be. I have bumped them all to 6GB of RAM, and so far, I've been seeing backup successes. Barring the question below, I'd say we could close this issue. The lesson learned is that I need to provide my backup tasks more RAM. Because I have some RAM to spare, I'm going aggressive, and giving things 6GB. I did not attempt to settle on a smaller amount, for anyone who comes along after--- I just gave the tasks a limit that I considered to be "a lot" in this context. I still see some things like the errors below. The backup completes successfully, but I'm unclear why there would be errors like these sprinkled throughout the backup. Is the relative path full/snapshot/app_... actually correct? Or, should that be a full path (e.g. the base path I provided at setup time along with the relative path)? In the command that succeeds, it is a full path. Feb 13 16:11:00 box:shell filesystem: ssh -o "StrictHostKeyChecking no" -i /tmp/identity_file_d82bc09e-a419-4d60-84bf-95d631fd0ebb -p 22 user@nas.lan cp -aRl full/snapshot/app_c74efccf-d273-46c9-8afe-3fd427bb78c1 full/2026-02-13-210356-064/app_git.jadud.com_v1.37.4 errored BoxError: ssh exited with code 1 signal null Feb 13 16:11:00 at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:82:23) Feb 13 16:11:00 at ChildProcess.emit (node:events:519:28) Feb 13 16:11:00 at maybeClose (node:internal/child_process:1101:16) Feb 13 16:11:00 at ChildProcess._handle.onexit (node:internal/child_process:304:5) { Feb 13 16:11:00 reason: 'Shell Error', Feb 13 16:11:00 details: {}, Feb 13 16:11:00 stdout: <Buffer >, Feb 13 16:11:00 stdoutString: '', Feb 13 16:11:00 stdoutLineCount: 0, Feb 13 16:11:00 stderr: <Buffer 63 70 3a 20 63 61 6e 6e 6f 74 20 73 74 61 74 20 27 66 75 6c 6c 2f 73 6e 61 70 73 68 6f 74 2f 61 70 70 5f 63 37 34 65 66 63 63 66 2d 64 32 37 33 2d 34 ... 50 more bytes>, Feb 13 16:11:00 stderrString: "cp: cannot stat 'full/snapshot/app_c74efccf-d273-46c9-8afe-3fd427bb78c1': No such file or directory\n", Feb 13 16:11:00 stderrLineCount: 1, Feb 13 16:11:00 code: 1, Feb 13 16:11:00 signal: null, Feb 13 16:11:00 timedOut: false, Feb 13 16:11:00 terminated: false Feb 13 16:11:00 } Feb 13 16:11:00 box:storage/filesystem SSH remote copy failed, trying sshfs copy Feb 13 16:11:00 box:shell filesystem: cp -aRl /mnt/managedbackups/1ec6c6b4-7566-4369-b2ce-466968b00d5d/full/snapshot/app_c74efccf-d273-46c9-8afe-3fd427bb78c1 /mnt/managedbackups/1ec6c6b4-7566-4369-b2ce-466968b00d5d/full/2026-02-13-210356-064/app_git.jadud.com_v1.37.4 Feb 13 16:11:07 box:backuptask copy: copied successfully to 2026-02-13-210356-064/app_git.jadud.com_v1.37.4. Took 7.889 seconds

Even though I thought cloudron-support --troubleshoot had already done this, i tried docker system prune -a --volumes again and managed to free up 2.954GB - now updating

DNS propagation is an asynchronous process. I have no way of knowing exactly when the DNS record has changed globally. My assumption was: as soon as the domain starts resolving to the Cloudron server (i.e., the first external requests hit the new IP), Cloudron could automatically begin issuing the certificate and complete the app setup. Is there a technical reason why this approach would not be feasible?

@mathieu this is a bit technical but you can update the custom package over your existing installation. As long as the data is compatible between the packages it will work.

It looks like Plane have given up on Gantt charts. Epics fits into the Plane hierarchy like this: Hierarchy: Issues → Epics → Initiatives (Initiatives group multiple Epics for even larger scopes).

How much memory does the whole server have? Maybe it overall runs out of memory, so non of the limits set are even hit?