M
I am after upgrading my Cloudron version to 8.1.0
There is still a problem in the latest version as in the previous version that is after extracting from .zip or .tar it changes the ownership.
After extracting, the folder changes from “www-data” to “root”.
During the change from “root” to “www-data” at the end it seems to switch to “root” at the last second. You have to take a good look at what is happening. Because of this, I can't update the app.
After changing the port, then you have to connect this way:
ssh user@ip_server -p 202
@falkfyre
Well, it is during this troubleshooting that “proxy” should be disabled
@falkfyre
How do you connect and have a message about an erroneous certificate. At the bottom you have a button “Advanced” and there you have a button to go to the page.
@falkfyre
Try again, just to be sure, in another browser, you need to confirm connections to the dashboard the wrong certificate.
@falkfyre
You must manually refresh the certificate under “Domains & Certs”
Just today I got a notification about an erroneous backup of the server where I have Nextcloud installed (150GB size) and I backup once a week.. I should add that the previous backups were successful. The provider is Backblaze B2.
Oct 06 01:02:32 box:storage/s3 Upload progress: {"loaded":1073741824,"part":2,"key":"102/snapshot/app_50d07945-bf1b-4345-8e8c-c146e86c12a7.tar.gz.enc"}
Jan 01 01:24:00 node:events:496
[no timestamp] throw er; // Unhandled 'error' event
[no timestamp] ^
[no timestamp]
[no timestamp] write EPIPE
[no timestamp] at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
[no timestamp] 'error' event on TLSSocket instance at:
[no timestamp] at emitErrorNT (node:internal/streams/destroy:169:8)
[no timestamp] at emitErrorCloseNT (node:internal/streams/destroy:128:3)
[no timestamp] at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
[no timestamp] errno: -32,
[no timestamp] code: 'EPIPE',
[no timestamp] syscall: 'write'
[no timestamp] }
[no timestamp]
[no timestamp] v20.12.2
Oct 06 01:02:32 box:shell backup-snapshot/app_50d07945-bf1b-4345-8e8c-c146e86c12a7: /usr/bin/sudo -S -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_50d07945-bf1b-4345-8e8c-c146e86c12a7 tgz {"localRoot":"/home/yellowtent/appsdata/50d07945-bf1b-4345-8e8c-c146e86c12a7","layout":[]} errored BoxError: backup-snapshot/app_50d07945-bf1b-4345-8e8c-c146e86c12a7 exited with code 1 signal null
[no timestamp] at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:122:19)
[no timestamp] at ChildProcess.emit (node:events:518:28)
[no timestamp] at ChildProcess.emit (node:domain:488:12)
[no timestamp] at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
[no timestamp] reason: 'Shell Error',
[no timestamp] details: {},
[no timestamp] code: 1,
[no timestamp] signal: null
[no timestamp] }
Oct 06 01:02:32 box:taskworker Task took 152.05 seconds
Oct 06 01:02:32 box:tasks setCompleted - 2443: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
Oct 06 01:02:32 box:tasks update 2443: {"percent":100,"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
[no timestamp] Backuptask crashed
[no timestamp] at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)
[no timestamp] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[no timestamp] at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)
[no timestamp] at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)
[no timestamp] at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)
On other servers the backups are successful.
@andreasdueren
Apparently, you can as primary storage, but the risks are high for Nextcloud applications in Cloudron, e.g.: resetting the file where the environment variable settings are located, or restoring the application, where there will be a conflict between the database and files located in external S3 storage.
In the application you need to run “External Storage support”. After launching in the settings you need to add. Then it will appear as a “folder”
I just got access to the test already. I currently have it connected to Nextcloud as an external drive. So far it looks promising 
Very fast processing ie uploading large files from the server to disk storage and downloading.
In my case, it works correctly to create a backup with the application above 100GB after applying the above settings that I sent.
Just because you have a dedicated server doesn't mean you have a full link or performance.
The stability of the link between providers depends on the network that the provider uses and how it allocates the link to the server. And very many providers have shared with other hosts.
If the provider is ZAP Hosting https://zap-hosting.com/en/
I looked by the name of the organization, which has an assigned pool of addresses to serve. I see that the provider is 95% known for gaming servers. I have the impression that the high network load is caused by online games and causes a lot of lag and suspension of the link by the load on the link by other hosts.
I recommend to have a server with a provider that has full transit link support with Tier-1 providers i.e. an example provider as to the quality of the price is Hetzner in the Cloud offering. The latest servers if you hit has a connection with speeds up to 20Gbps
@cocam123
And could you specify the VPS provider ?
Basic question:
I also had this problem a few weeks ago. During the migration from Contabo, creating a backup was so problematic that I started fiddling with the parameters.
It was only with the help of these parameters that it started to stabilise and now performs the backup correctly.
Storage Format: Tarball
Memory Limit: 4GB
Upload Part Size: 512 MiB
What was interesting was that after restoring from the backup on the new server, the settings reset. I only noticed when I had an error message related to the backup.
You have to update to version 24.04 yourself.
https://docs.cloudron.io/guides/upgrade-ubuntu-24/
I personally made a second server with Ubuntu 24.04 and did a Cloudron restore using a backup.
@humptydumpty I also think. On the server where the copy is running the size of the application does not exceed 1GB, and on the production server I have Nextcloud where the size exceeds 100GB is not successful.
I also have a similar problem. I have the same as you, Hetzner server and Backblaze. @girish has already made an improvement and it will be in the new version 8.0.4 next week.
But it's interesting, on the development server where I have an application running that I prepare in LAMP it runs a copy with no problem.
@bennyv53
Change host "postgresql" to "172.18.30.2"
The only message was only related to PTR. And there was no other message. Maybe it was a special case or a problem with the request and the question was whether from my server or on the provider's side.
After I clicked sync DNS, I left it for another 24 hours just to be sure, because the proprogation could have been prolonged. After 24 hours there was still a problem , then I did a record analysis and noticed as I wrote above one record A was not updated.
In general, the situation embraced. You can close the topic 
only waiting for the improvement of the results from PTR. Generally I have changed but FCrDNS has not been updated.