@carlostph One thing is that what might be causing the upload to stall is the CPU (because of gzip). Can you also check tar cvf - /home/yellowtent/appsdata/<mastodon-app-id/ and pipe that to s3cmd ?

@girish Sure thing!

I will mark this as solved. Will make a feature thread.

Since we have added an OpenID connect and thus some OAuth2 compatibility, I will mark this as solved finally.

Well spotted, this has changed indeed. I have fixed it to 24h always https://git.cloudron.io/cloudron/box/-/commit/a2c16e9442d9135b8ba392e9c0b2797307c6155c

Fix for this was the same as https://forum.cloudron.io/topic/8944/redash-restore-failure

@girish I tried it just with other Browser, it works. That was an stored browser data issue, sorry and thank you. Lukas

This is fixed in 7.4.1, was a regression.

This was a bug in 7.4.0 and is now fixed in 7.4.1. We updated node to v18 (from v16). There was a subtle but impact change hidden... In node 16, the requestTimeout was 0. This meant unlimited time. In node 18, the requestTImeout is now 5 mins. This meant that large restores were failing if the upload didn't finish within 5 mins.

@romfeo said in Cloudron after rescaling a server: app's (Wordpress) See https://docs.cloudron.io/apps/#memory-limit and https://docs.cloudron.io/apps/#cpu-shares Also adjust the memory limits in https://my.domain.coop/#/services And for WordPress specifically see: https://docs.cloudron.io/apps/wordpress-developer/#memory-limits and https://docs.cloudron.io/apps/wordpress-developer/#php-settings

@girish Great, thank you for the information

@jasonsq if you can send us a mail at support@cloudron.io, we can help figure what is going on.

@j_vmess your domain works just fine for me here. Maybe it's a browser cache issue? Have you tried another browser or after clearing the browser cache? I removed your domain from the original post, since it was showing the setup screen.

@Fabix thanks. Strange stuff... I will put it in our docs that we only support Robot.

@Recliner2042 It needs to write to DNS . You can read more at https://letsencrypt.org/docs/challenge-types/ (dns-01).

Hi @Thedurancode, the way apps are designed on Cloudron it is not possible to change any of the actual application code (and therefore you get the file permission errors). Instead you will either need to wait until Nextcloud 26 is generally available (you can check this post to check for the latest release) or you would need to fork the app code and perform the update there. The latter is easy to do if you are familar with Cloudron app development, but not really recommended for beginners (ihmo).

@girish oh, ok then sorry for this!

@roofboard said in Chat woot cannot uninstall after breaking the backup system.: Mar 30 20:19:30 box:services Backing up postgresql Mar 30 20:29:30 box:services pipeRequestToFile: timeout - connect or post-connect idle timeout It seems somehow postgresql was not having a happy time. Maybe give it a bit more memory (Services -> PostgreSQL -> increase memory limit). The reboot probably just freed up some memory.

Also, in Cloudron 7.3.x, all the addons/services are still using the old base image (3.2.0) but the apps have all been updated now to use the new base image (4.0.0) . In 7.4, all the addon docker images are updated to 4.0.0. You will see some space savings after the update.

@girish ok got it. Thank you.