Restore backup failed after 20h - Error 70

[JScheumann]

Hey,
after a weekend of fun, try to restore a Cloudron App Backup (Nextcloud) i ended up with manual restore all files and database.
But because I'm not sure whether there is a real problem or whether I just haven't found the solution, I wanted to describe my problem here.

I wanted to restore my Nextcloud to an older version after an update failed and all my shared links stopped working.
To do this, I first restarted the corresponding backup with “Restore” in the Backup tab of the web UI.
This ran for a while and then stopped after about a day (20 hours), displaying only “Restoring (Queued)” in the web interface.
The second attempt also failed, so I searched the logs and found the following error, with error code 70.

2026-02-07T09:08:30.024Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:08:40.020Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:08:50.022Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:00.012Z box:scheduler sync: clearing jobs of 78872bb3-bd68-407f-9909-48b2cab3a4ec (cloud.haip-solutions.com)
2026-02-07T09:09:00.013Z box:docker deleteContainer: deleting 78872bb3-bd68-407f-9909-48b2cab3a4ec-housekeeping
2026-02-07T09:09:00.054Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:10.033Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:20.022Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:30.022Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:40.021Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:09:50.020Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:00.020Z box:scheduler sync: clearing jobs of 78872bb3-bd68-407f-9909-48b2cab3a4ec (cloud.haip-solutions.com)
2026-02-07T09:10:00.020Z box:docker deleteContainer: deleting 78872bb3-bd68-407f-9909-48b2cab3a4ec-housekeeping
2026-02-07T09:10:00.043Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:10.027Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:16.679Z box:shell tasks: timedout
2026-02-07T09:10:16.679Z box:tasks onTimeout: 8951
2026-02-07T09:10:16.680Z box:tasks stopTask: stopping task 8951
2026-02-07T09:10:16.680Z box:shell tasks: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/stoptask.sh 8951
2026-02-07T09:10:16.975Z box:shell tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 8951 /home/yellowtent/platformdat
a/logs/78872bb3-bd68-407f-9909-48b2cab3a4ec/apptask.log 15 12288 0 errored BoxError: /usr/bin/sudo exited with code 70 signal null
    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:82:23)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  reason: 'Shell Error',
  details: {},
  stdout: 'Service box-task-8951 failed to run\n' +
    'Service box-task-8951 finished with exit code 1 and status 70\n',
  stdoutLineCount: 2,
  stderr: 'Running as unit: box-task-8951.service\n' +
    'Finished with result: exit-code\n' +
    'Main processes terminated with: code=exited/status=70\n' +
    'Service runtime: 20h 212ms\n',
  stderrLineCount: 4,
  code: 70,
  signal: null,
  timedOut: true,
  terminated: false
}
2026-02-07T09:10:16.978Z box:tasks startTask: 8951 done. error: { message: 'Task 8951 timed out', code: 'timeout' }
2026-02-07T09:10:16.979Z box:tasks setCompleted - 8951: {"error":{"message":"Task 8951 timed out","code":"timeout"}}
2026-02-07T09:10:16.979Z box:tasks updating task 8951 with: {"completed":true,"error":{"message":"Task 8951 timed out","code":"timeout"}}
2026-02-07T09:10:16.997Z box:apps scheduleTask: task 8951 of 78872bb3-bd68-407f-9909-48b2cab3a4ec completed. error: { message: 'Task 8951 timed out', code: 
'timeout' }
2026-02-07T09:10:17.041Z box:locks write: current locks: {}
2026-02-07T09:10:17.041Z box:locks release: app_task_78872bb3-bd68-407f-9909-48b2cab3a4ec
2026-02-07T09:10:17.050Z box:locks write: current locks: {}
2026-02-07T09:10:17.050Z box:locks releaseByTaskId: 8951
2026-02-07T09:10:17.052Z box:scheduler resumeAppJobs: 78872bb3-bd68-407f-9909-48b2cab3a4ec
2026-02-07T09:10:20.024Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:30.029Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:40.020Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:10:50.023Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:11:00.017Z box:scheduler sync: clearing jobs of 78872bb3-bd68-407f-9909-48b2cab3a4ec (cloud.haip-solutions.com)
2026-02-07T09:11:00.017Z box:docker deleteContainer: deleting 78872bb3-bd68-407f-9909-48b2cab3a4ec-housekeeping
2026-02-07T09:11:00.029Z box:docker deleteContainer: deleting 78872bb3-bd68-407f-9909-48b2cab3a4ec-housekeeping
2026-02-07T09:11:00.051Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:11:00.267Z box:scheduler BoxError: (HTTP code 400) bad parameter - No such container: null 
    at Object.createSubcontainer (/home/yellowtent/box/src/docker.js:460:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2026-02-07T09:11:10.023Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:11:20.023Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:11:30.017Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive
2026-02-07T09:11:40.020Z box:apphealthmonitor app health: 1 running / 0 stopped / 1 unresponsive

So I tried to find out which task ended my restore process after 20 hours and where I could change the settings for it.
Unfortunately, I couldn't find anything about it in the web UI, the configs, or any forums.

My Nextcloud app data size is 750GB and i am downloading with average speed 120Mbit/s (15MB/S).
The ethernet connection speed should be more for my server, but i guess a lot of small files slows down the connection.

I don't find the amount of data for a Nextcloud instance particularly high, nor do I find my internet speed too slow.
Nevertheless, I am experiencing problems with timeouts.

Is there anything I've overlooked or a setting I haven't found? And if that's not the case, it's a problem with Cloudron or my systemd?

Perhaps someone here can help me with this or provide some answers.

Best regards,
Jesse

[james]

Hello @jscheumann and welcome to the Cloudron forum

Sorry that you had such an unpleasent experience.

Can you please provide the logs of that failing backup?
In the excerpt of the box.log you have provided the task ID is 8951 and should be in /home/yellowtent/platformdata/logs/tasks/

[nebulon]

There is also a Logs dropdown button in the backups view which opens the corresponding log file in the logsviewer, from there the full logs can also be downloaded, avoiding the need to ssh into the server.