Cloudron Forum

@nebulon I have bumped up the memory as well. My nextcloud has gotten quite large and I didn't empty the recycle bin. Trying a backup after the delete permanently runs.

Any recommended backup host?

I tried to adjust the part size. I now get:

Task 3427 crashed with code 1

Looking at the logs, no footprint of a crash.

@nebulon I am using Backblaze

https://github.com/s3tools/s3cmd/issues/613

I can provide the full log if needed.

timestamp] /home/yellowtent/box/node_modules/aws-sdk/lib/services/s3.js:712
[no timestamp] resp.error = AWS.util.error(new Error(), {
[no timestamp] ^
[no timestamp]
[no timestamp] Part number must be in the range 1 - 10000

I am trying to get grav git sync to work.

Starting with a bare repo https://git.knownelement.com/reachableceo/reachableceo.com .
root@274c4e05-0aea-49c1-8c4a-aff47c566f65:/app/data/user# git status
fatal: detected dubious ownership in repository at '/app/data/user'
To add an exception for this directory, call:

    git config --global --add safe.directory /app/data/user

root@274c4e05-0aea-49c1-8c4a-aff47c566f65:/app/data/user# git config --global --add safe.directory /app/data/user
error: could not lock config file /root/.gitconfig: Read-only file system
root@274c4e05-0aea-49c1-8c4a-aff47c566f65:/app/data/user#

Any way to solve this?

If I use a repo that is initalized, it complains about divergent branches. And the suggested ways to fix all involve git --config which fails.