Cloudron Forum

Thanks! I was hesitant to use Nextcloud Talk initially since Cloudron is raising awareness about third party Nextcloud apps.

Checking it, thanks everyone!

This topic can be marked as closed. I decided to buy an instance with more memory and it worked well.

Distributing of PGP keys was painful or not effective. Web Key Directory (WKD) is solving this by providing the public key umder the actual domain.

It is described in detail here:
https://wiki.gnupg.org/WKD
(Alternatively, there is also the Web Key Service)

It would be nice if this could be added next to the other well-known location fields.

For reference: there is already an instance of this wish in App list:
https://forum.cloudron.io/post/23272

However, I don't think a separate App is required.

Thanks of this nice product, cloudron

I was able to solve the issue by stopping the nextcloud app and afterwards rebooting the Cloudron Server. After the Cloudron Server came up again, I waited for a grace period and started the Nextcloud App afterwards again.

It should be mentioned that the reboot of the server took exceptionally long, more than 45 min. I didn't investigate the root cause.

This topic can be marked as solved.

@girish More update on this: I found a discussion how to change the Admin in the DB directly. Seems to be the solution with less pain.

Role = 1 should to do the trick in the user table

https://github.com/firefly-iii/firefly-iii/discussions/5295

(Maybe the title of this thread is more about "How to change the admin user")

In my Cloudron instance, the CPU Usage graph is scaled up to 400%, although the actual value is ranging around 20%.

Is there a way to configure it, e.g. with a max of 100%?

@girish Yes, Thunderbird supports WKD.

From the Thunderbird FAQs it is explained like this:

Currently, it will search for published keys using the WKD protocol, and it will search for keys in the keys.openpgp.org keyserver.

Source:
https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq#w_how-do-i-get-the-public-keys-of-my-correspondents

Slightly off-topic, but related:
Provider posteo also offers to publish public Keys via wkd, as described in this FAQ:

https://posteo.de/en/help/easygpg-how-do-i-publish-my-public-pgp-key-in-posteos-key-directory-via-web-key-directory-wkd

Thank you for the fast answer!

Okay, interesting. I just realized that the AWS Market Place image is still on version 7.2.4

Is there any way to downgrade my current instance version?
Or is it possible to upgrade Cloudron before configuring?
Or does the Cloudron instance also update itself periodically without being configured?

Your hint helped me to find the root cause, thanks

The main advantage of using Cloudron's storage over managing backups with a provider like DigitalOcean directly is simplicity and convenience. Cloudron could offer a storage solution that’s already configured for you, so there’s no need to mess with setting things up yourself. It’s essentially a one-click solution: everything’s integrated seamlessly within Cloudron.

Yes, you could handle backups directly with DO or other providers, but having Cloudron manage the backup configuration can save time and reduce the potential for errors. You don't have to worry about ensuring all the settings are right: Cloudron takes care of it, and if anything goes wrong, their support has a better idea of the setup. For someone who values ease of use, that could justify the markup.

While Cloudron may not offer more control over issues related to the provider itself, the advantage lies in reducing your manual workload. You’re essentially paying for that added convenience and peace of mind.

@robi Thank you! I will try uprading the marketplace instance.

@humptydumpty Valid points, but the main focus here is how Cloudron could simplify backups by providing an already-configured solution. Sure, it may require some initial setup, but the idea is that it reduces ongoing manual work and offers peace of mind. If one fails to setup the backup, data is eventually lost. Lost DNS entries are less severe. Things like running Restic or leveraging higher support levels could be added advantages if Cloudron manages the infrastructure. Let's keep the discussion about whether that kind of convenience and integration is worth considering, rather than comparing unrelated scenarios.

@girish Thank you, that helps.

I was unsure how I can setup cloudron with a minimal setup.

But I found this post which helped me:
How to use cloudron without a domain name or opening ports?

Thanks for being active in supporting in the forum guys! This is really an important arguement for cloudron for me

Hi All,

thanks for continously working on Cloudron.

After the update to v7.4.1 my instance ran out if memory. Hence I spinned up a new server with bigger disk (35GiB).

One app is a nextcloud app which is saving all its data on external storage volume (efs). The amount of data is comparably high (>30GiB).

While restoring, it fails with following error:

Task Error: Task 2167 crashed as it ran out of memory

The error message makes sense since the server has only 1GiB of memory (+ 1 GiB swap).

I could now restore the previous EFS Backup from external source, i.e. there is no is no need for cloudron to recover this app.

How can I recover nextcloud?

I can neither change the memory limit nor can I enable the recovery mode (both disabled/greyed out).

The remote backups (S3) do not exist, but the local db entries are still.
However, they get eventually deleted once the time come.
I already wanted to recover an app to a non existing version, but I was scared to break sth^^

My backup interval is daily 3 am and for Retention Policy it is

3 daily, 4 weekly, 6 monthly

I thought it means I will effectively have backups of the last 3 days, older than 3 days there are only backups 1 per week (up to 4 weeks) and older than 4 weeks there is only 1 per month.

Is that wrong?

Because I see more like 4/5 days daily, and there is 30th June, 1st and 2nd July in a row although more than 3 days ago.

Today (= 15/07/2023)
Yesterday (=14/07/2023)
13/07/2023
12/07/2023
11/07/2023
09/07/2023
02/07/2023
01/07/2023
30/06/2023
25/06/2023
31/05/2023

Urgency and importance of this question is low for me, but curious.

Is the Nextcloud data backuped being on an mounted volume?

Having the following setup:

• Nextcloud installed as app
• mounted an (AWS) EFS volume in the Cloudron instance
• selected this EFS volume for the Nextcloud Apps data

As shown in the "Mounts" section screenshot, it is written that "data is not included in the app's backup".
However, in the upper part of the Screenshot in the "Data Directory" section, it is written "any data here is part of the app's backup".

The reason why I use EFS is the "unlimited growth" capacity.

Additional info: I mounted S3 in the Nextcloud instance (from the Nextcloud interface itself) and I am wondering if there would be any issues if I need to restore the Nextcloud app in terms of accessing the EFS volume from Cloudron and even further with the S3 external storage.

I also read this thread, but I am not really getting the point: https://forum.cloudron.io/topic/6778/volumes-and-backup

Anyone else observing that cloudron grows over time? After maybe 6 to 8 month it looks like below.
I have 8 apps installed, all the app data sums up to not more than 50 MB. Only exception is the platformdata with 1 GB.

Is there anything I can do to reduce it?
I have another free volume availble, but I am not sure what I can use it for to release /root, which is /dev/sda1 mounted at /

• docker 16 GB
• /apps.swap 4 GB
• docker-volumes 4 GB
• Everything else (Ubuntu, etc) 8 GB

The Nextcloud app seems to be caught in an infinite restart loop since few hours.
Checking the logs, I can see one outstanding recurring log entry in red:

Aug 06 18:17:45 <30>1 2024-08-06T16:17:45Z [...] - Command "upgrade" is not defined.

This is "the whole loop"in truncated logs, execpt the App updates:

activity files_sharing sharebymail
Aug 06 18:24:19 admin_audit files_trashbin support
Aug 06 18:24:19 bruteforcesettings files_versions survey_client
Aug 06 18:24:19 circles firstrunwizard suspicious_login
Aug 06 18:24:19 cloud_federation_api logreader systemtags
Aug 06 18:24:19 comments lookup_server_connector text
Aug 06 18:24:19 contactsinteraction nextcloud_announcements theming
Aug 06 18:24:19 dashboard notifications twofactor_backupcodes
Aug 06 18:24:19 dav oauth2 twofactor_totp
Aug 06 18:24:19 encryption password_policy updatenotification
Aug 06 18:24:19 federatedfilesharing photos user_ldap
Aug 06 18:24:19 federation privacy user_status
Aug 06 18:24:19 files provisioning_api viewer
Aug 06 18:24:19 files_downloadlimit recommendations weather_status
Aug 06 18:24:19 files_external related_resources workflowengine
Aug 06 18:24:19 files_pdfviewer serverinfo
Aug 06 18:24:19 files_reminders settings
Aug 06 18:24:19 activity files_sharing sharebymail
Aug 06 18:24:19 admin_audit files_trashbin support
Aug 06 18:24:19 bruteforcesettings files_versions survey_client
Aug 06 18:24:19 circles firstrunwizard suspicious_login
Aug 06 18:24:19 cloud_federation_api logreader systemtags
Aug 06 18:24:19 comments lookup_server_connector text
Aug 06 18:24:19 contactsinteraction nextcloud_announcements theming
Aug 06 18:24:19 dashboard notifications twofactor_backupcodes
Aug 06 18:24:19 dav oauth2 twofactor_totp <30>1 2024-08-06T16:24:19Z - encryption password_policy updatenotification <30>1 2024-08-06T16:24:19Z - federatedfilesharing photos user_ldap <30>1 2024-08-06T16:24:19Z - federation privacy user_status <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - files provisioning_api viewer <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - files_downloadlimit recommendations weather_status <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - files_external related_resources workflowengine <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - files_pdfviewer serverinfo <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - files_reminders settings <30>1 2024-08-06T16:24:19Z ip-10-0-0-114 - ==> Copying htaccess
Aug 06 18:24:38 ==> update config
Aug 06 18:24:58 ==> run migration
Aug 06 18:25:16 Nextcloud is not installed - only a limited number of commands are available
Aug 06 18:25:18 2024-08-06T16:25:18.000Z
Aug 06 18:25:19 <30>1 2024-08-06T16:25:19Z ip-10-0-0-114 - Command "upgrade" is not defined. <30>1 2024-08-06T16:25:19Z ip-10-0-0-114 - <30>1 2024-08-06T16:25:19Z ip-10-0-0-114 -
Aug 06 18:25:42 ==> Updating apps <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - ==> Old apps:
Aug 06 18:25:42 activity files_sharing sharebymail <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - admin_audit files_trashbin support <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - bruteforcesettings files_versions survey_client <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - circles firstrunwizard suspicious_login <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - cloud_federation_api logreader systemtags
Aug 06 18:25:42 comments lookup_server_connector text <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - contactsinteraction nextcloud_announcements theming <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - dashboard notifications twofactor_backupcodes <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - dav oauth2 twofactor_totp <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - encryption password_policy updatenotification <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - federatedfilesharing photos user_ldap <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - federation privacy user_status <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files provisioning_api viewer <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_downloadlimit recommendations weather_status <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_external related_resources workflowengine <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_pdfviewer serverinfo <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_reminders settings
Aug 06 18:25:42 activity files_sharing sharebymail <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - admin_audit files_trashbin support <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - bruteforcesettings files_versions survey_client <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - circles firstrunwizard suspicious_login <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - cloud_federation_api logreader systemtags <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - comments lookup_server_connector text
Aug 06 18:25:42 contactsinteraction nextcloud_announcements theming <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - dashboard notifications twofactor_backupcodes <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - dav oauth2 twofactor_totp <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - encryption password_policy updatenotification <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - federatedfilesharing photos user_ldap <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - federation privacy user_status <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files provisioning_api viewer <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_downloadlimit recommendations weather_status <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_external related_resources workflowengine <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_pdfviewer serverinfo <30>1 2024-08-06T16:25:42Z ip-10-0-0-114 - files_reminders settings

After trying to restore cloudron on a new server, I am getting this error while attempting to restore nextcloud:

[no timestamp]  tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?

It worries me, that there is no timestamp.

Until now I tried to

1. reboot the server (multiple times)
2. restore older backups (not only the one from directly before)

Further logs before the log above:

Oct 11 20:09:04 - [POST] /clear
Oct 11 20:12:35 box:backupformat/tgz tarExtract: ./data/appdata_ocofjozos9pc/preview/2/0/9/d/1/9/5/83606/4096-4096-max.png 98592 file to /home/yellowtent/appsdata/39b0914d-1add-4a32-966f-d331fb91f589/data/appdata_ocofjozos9pc/preview/2/0/9/d/1/9/5/83606/4096-4096-max.png

[...]

Oct 11 20:12:35 box:apptask run: app error for state pending_restore: BoxError: tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped? at tarExtract (/home/yellowtent/box/src/backupformat/tgz.js:225:26) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /home/yellowtent/box/src/backupformat/tgz.js:248:9 at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20) at async Object.download (/home/yellowtent/box/src/backupformat/tgz.js:244:5) at async download (/home/yellowtent/box/src/backuptask.js:100:5) at async Object.downloadApp (/home/yellowtent/box/src/backuptask.js:133:5) at async install (/home/yellowtent/box/src/apptask.js:368:9) { reason: 'External Error', details: {} }
Oct 11 20:12:35 box:tasks setCompleted - 2703: {"result":null,"error":{"stack":"BoxError: tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?\n at tarExtract (/home/yellowtent/box/src/backupformat/tgz.js:225:26)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async /home/yellowtent/box/src/backupformat/tgz.js:248:9\n at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)\n at async Object.download (/home/yellowtent/box/src/backupformat/tgz.js:244:5)\n at async download (/home/yellowtent/box/src/backuptask.js:100:5)\n at async Object.downloadApp (/home/yellowtent/box/src/backuptask.js:133:5)\n at async install (/home/yellowtent/box/src/apptask.js:368:9)","name":"BoxError","reason":"External Error","details":{},"message":"tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?"}}
Oct 11 20:12:35 box:tasks update 2703: {"percent":100,"result":null,"error":{"stack":"BoxError: tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?\n at tarExtract (/home/yellowtent/box/src/backupformat/tgz.js:225:26)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async /home/yellowtent/box/src/backupformat/tgz.js:248:9\n at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)\n at async Object.download (/home/yellowtent/box/src/backupformat/tgz.js:244:5)\n at async download (/home/yellowtent/box/src/backuptask.js:100:5)\n at async Object.downloadApp (/home/yellowtent/box/src/backuptask.js:133:5)\n at async install (/home/yellowtent/box/src/apptask.js:368:9)","name":"BoxError","reason":"External Error","details":{},"message":"tarExtract pipeline error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?"}}
Oct 11 20:12:35 box:taskworker Task took 241.42 seconds
[no timestamp]  2024-10-11T17:53:16Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:C 11 Oct 2024 17:53:16.518 * Configuration loaded
[no timestamp]  2024-10-11T17:53:16Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:C 11 Oct 2024 17:53:16.518 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=12, just started
[no timestamp]  2024-10-11T17:53:16Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:53:16.565 * RDB memory usage when created 0.90 Mb
[no timestamp]  2024-10-11T17:53:16Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:53:16.566 * Done loading RDB, keys loaded: 0, keys expired: 0.
[no timestamp]  2024-10-11T17:53:16Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:53:16.566 * Ready to accept connections tcp
[no timestamp]  2024-10-11T17:53:18Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:53:18,146 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:55:07.306 * Saving the final RDB snapshot before exiting.
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:55:07.308 * DB saved on disk
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:55:07.308 * Removing the pid file.
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:M 11 Oct 2024 17:55:07.309 # Redis is now ready to exit, bye bye...
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 12:signal-handler (1728669307) Received SIGTERM scheduling shutdown...
[no timestamp]  2024-10-11T17:55:07Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1010 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:55:07,274 INFO waiting for redis, redis-service to die
[no timestamp]  2024-10-11T17:58:47Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:58:47,457 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
[no timestamp]  2024-10-11T17:58:47Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:58:47,457 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
[no timestamp]  2024-10-11T17:58:47Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:58:47,482 CRIT Server 'unix_http_server' running without any HTTP authentication checking
[no timestamp]  2024-10-11T17:58:47Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:58:47,483 INFO supervisord started with pid 1
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:C 11 Oct 2024 17:58:48.694 * Configuration loaded
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:C 11 Oct 2024 17:58:48.694 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=13, just started
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 17:58:48.778 * RDB age 221 seconds
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 17:58:48.778 * RDB memory usage when created 0.83 Mb
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 17:58:48.779 * DB loaded from disk: 0.002 seconds
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 17:58:48.779 * Done loading RDB, keys loaded: 0, keys expired: 0.
[no timestamp]  2024-10-11T17:58:48Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 17:58:48.779 * Ready to accept connections tcp
[no timestamp]  2024-10-11T17:58:50Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 17:58:50,463 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[no timestamp]  2024-10-11T18:07:05Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:05.456 * Saving the final RDB snapshot before exiting.
[no timestamp]  2024-10-11T18:07:05Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:05.458 * Removing the pid file.
[no timestamp]  2024-10-11T18:07:05Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:05.459 # Redis is now ready to exit, bye bye...
[no timestamp]  2024-10-11T18:07:05Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:signal-handler (1728670025) Received SIGTERM scheduling shutdown...
[no timestamp]  2024-10-11T18:07:05Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1009 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 18:07:05,461 INFO stopped: redis (exit status 0)
[no timestamp]  2024-10-11T18:07:33Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 18:07:33,814 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
[no timestamp]  2024-10-11T18:07:33Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 18:07:33,832 INFO RPC interface 'supervisor' initialized
[no timestamp]  2024-10-11T18:07:33Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 18:07:33,833 CRIT Server 'unix_http_server' running without any HTTP authentication checking
[no timestamp]  2024-10-11T18:07:33Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 2024-10-11 18:07:33,833 INFO supervisord started with pid 1
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:C 11 Oct 2024 18:07:34.906 * Configuration loaded
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.909 * monotonic clock: POSIX clock_gettime
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.921 # Failed to write PID file: Permission denied
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.921 * Running mode=standalone, port=6379.
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.922 * Server initialized
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.927 * DB loaded from disk: 0.006 seconds
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.927 * Loading RDB produced by version 7.2.1
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.927 * RDB age 29 seconds
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.927 * RDB memory usage when created 0.90 Mb
[no timestamp]  2024-10-11T18:07:34Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32-966f-d331fb91f589 - 13:M 11 Oct 2024 18:07:34.927 * Ready to accept connections tcp
[no timestamp]  2024-10-11T18:07:35Z username redis-39b0914d-1add-4a32-966f-d331fb91f589 1011 redis-39b0914d-1add-4a32

Thanks for your input!

It didn't restore in the sense that the nextcloud app was restoring - as all other Cloudron apps - but ended up with the error message:

Error : External Error - tarExtract pipeline error: incorrect header check

The status of the nextcloud app is "Error".
I tried to restore again the whole cloudron server as well as deinstalling the nextcloud app and import only the backed up version. Neither of them did work.

It sounds to me that the password is wrong or that the algorithm for decrypting would be wrong.

The backuped file is on the server. Will try to decrypt it manually. The nextcloud backup has 12 GB of size, the server has more than 100 GB free