Cloudron Forum

I checked this out the last days and this looks really awesome!

Hi, I just wanted to follow up on this. We found the relating issue in this case which resulted in several different problems. In that case, it was bug in a firmware update on a firewall and not related to Cloudron and can be marked as resolved. Thank you anyway for your help.

I actually still have this issue. The instance is also not able to renew the certs, however on the vm DNS resolution seems to work correctly. There is a support ticket via Email open. Once I solve it, I can give a update here.

yes i do.. this is likely the same issue then..

None of those seem to be the issue...
Its the POST request to https://my.instance.com/api/v1/appstore/register_cloudron that results in a 424:

status "Failed Dependency"
message "Timeout of 30000ms exceeded"

I have this issue now on at least 2 Cloudron instances that were working correctly for a long time.

Now, when I want to install a new app from the store, It asks me for the Cloudron login. When provided, this request results in a timeout. However when i check in the settings, I see the correctly linked account. Also on the Cloudron-console, everything looks correct. How can i fix that?

Thanks!

Ok, so if i understand correctly, the mount is not automatically remounted after the share was not available for some time?

I am now slowly running into a storage limitation issue with the current settings. Also the performance of the current setting is really poor with 10-20 Mb/s considering that i would have a 10G link available that i cannot use.

@girish if i knew that there is some NFS improve scheduled, i could work around untill then. If not, i would need to cope with the current circumstances somehow. I think there would not even much needed.

I just need the NFS connector to:

• Never write to the root mount in order to prevent full root disk.
• Check mount before backup.
• If during the backup there is a connection issue, try to remount and continue. Try remount for 10 times with a delay of 10s or so...

@robi said in Nextcloud backup crashes:

@girish can you make sure the remount checks for CIFS are applied to NFS as well? At every backup..

Having it be more bulletproof would be great!

@girish do you think there will be a more stable support for NFS in the feature?

I would warmly welcome this and change right back to NFS.

@girish Cloudron is running in a Proxmox cluster. In the same local network there are storage servers via 10Gb/s. I guess ideal would be a NFS mount from a TrueNAS server. This way I could get rid of encryption overhead and use Jumbo frames. If cloudron could handle those NFS mounts stable, I would switch back to this. Other suggestions are very welcome.

@girish Bevor I used Minio for backups, I was mounting a NFS mount. But I went away from using this, because there were instabilities with the mount and if the share was not mounted, the backup was made onto the rootfs and eventually filled up the disk untill the instance crashed.

I just updated the app. It does work now, thx!

Sorry for not responding in an adequate time. Since my backups are still failing, I would try some other storage option. What storage protocol and configuration do you recommend for big backups?

I have the Rank Math Plugin installed on several WP instances on cloudron. Following through the configuration i am running into a 404 to that url:

https://example.com/app/data/wp-content/plugins/seo-by-rank-math/vendor/cmb2/cmb2/js/cmb2.min.js?ver=2.10.1

I tried to add the following to the .htaccess:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule ^app/data/(wp-content/.*)$ /$1 [R=301,L]
</IfModule>

However this somehow did not have any effect.
Has anyone else experienced this problem? How can i fix this?

I have a Nextcloud running on one of my instances, that uses a hd-storage mount of around 2.5 TB size.

The problem is, that instance does not manage to finish the backup. The machine has 32GB memory and 4 cores. The Nextcloud App has a memory limit of 8GB and CPU shares of 50%.

The following is the backup configuration.

The Minio instance is a self hosted app that runs on another Cloudron.

When the backup failed I saw this log:

Nov 19 18:52:17box:tasks update 8098: {"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 Object.backupApp (/home/yellowtent/box/src/backuptask.js:321:12)\n at async backup (/home/yellowtent/box/src/apptask.js:363:22)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
Backuptask crashed
at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)
at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)
at async Object.backupApp (/home/yellowtent/box/src/backuptask.js:321:12)
at async backup (/home/yellowtent/box/src/apptask.js:363:22)

The issue might be related with timeouts, because the Minio is not the fastest instance. Nevertheless, I would expect this to work, since its not really a huge amount of data.

Thanks for any suggestions or information on how to further debug this issue.

@josephcosta nice find indeed!

Thanks for the reply. I just doubled from 15 to 30. Lets see if this helps.

A Nextcloud instance is down every once in a while (around once in a Week) and needs to be restarted manually. I have set the log-level to debug, however I cannot find any suspicous logs in the logviewer of the app.

The VM and also the application has enough RAM and CPU.

How can I trace this issue best?

Thanks for any help.

There is the following error occuring when i run

/home/yellowtent/box/setup/start.sh

mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
2023-09-26T17:40:40 ==> start: Migrating data
Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Duplicate entry 'sftp_rsa_private_key' for key 'blobs.PRIMARY'
    at /home/yellowtent/box/node_modules/db-migrate/lib/commands/on-complete.js:15:14
    at tryCatcher (/home/yellowtent/box/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.successAdapter (/home/yellowtent/box/node_modules/bluebird/js/release/nodeify.js:22:30)
    at Promise._settlePromise (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:601:21)
    at Promise._settlePromiseCtx (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:641:10)
    at _drainQueueStep (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:102:5)
    at Async.drainQueues [as _onImmediate] (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:15:14)
    at process.processImmediate (node:internal/timers:476:21)
    at Packet.asError (/home/yellowtent/box/node_modules/mysql2/lib/packets/packet.js:728:17)
    at Query.execute (/home/yellowtent/box/node_modules/mysql2/lib/commands/command.js:29:26)
    at Connection.handlePacket (/home/yellowtent/box/node_modules/mysql2/lib/connection.js:456:32)
    at PacketParser.onPacket (/home/yellowtent/box/node_modules/mysql2/lib/connection.js:85:12)
    at PacketParser.executeStart (/home/yellowtent/box/node_modules/mysql2/lib/packet_parser.js:75:16)
    at Socket.<anonymous> (/home/yellowtent/box/node_modules/mysql2/lib/connection.js:92:25)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2023-09-26T17:40:41 ==> start: DB migration failed