Thanks for the insights, @arshsahzad and @girish, I’ll explore these solutions. As for tailscale and cloudflare, I’d have to set them up externally to cloudron on the server, right? Which I’ve always thought was not recommended. Think I’ll try it anyway and get back to you guys. I’ve already setup a vpn on my home server with wireguard so maybe I’ll go with that. Thanks!

@mrkovash cloudron never sends 521. Can you tell us a bit more about your setup? Screenshots? Errors? Where did you have to use the loopback address (this is even more strange) ?

Turns out the disk got full with docker images related to jupiter hub notebooks.

@luckow said in rocket.chat does not want to start anymore: it took 25 times Presumably 25 minutes?

@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).