Cloudron Forum

in config.yaml, you can adjust the timeouts security: api: jwt: sign: expiresIn: 300d # npm token expiration web: sign: expiresIn: 300d # webUI token expiration

I changed the mail server here. The DNS was updated and no SSL errors.

Good idea. For the moment, you can of course just run the autoscaler in another VM directly .

something is off . afaict, wallabag package has not seen a major version bump in ages . what makes you think that manual update was required? is your cloudron version up to date?

We have a https://git.cloudron.io/playground/ for such repos. TBF, it doesn't matter where your repo is hosted . Your link is equally sharable but you can also use ours if you think yours is more transient.

Did this get sorted out?

fixed for next release https://git.cloudron.io/platform/cloudron-cli/-/commit/09f359f34f23a3acb22067872fd570f23f2db834

Is this happening midway and has there already been some data restored at /home/yellowtent/boxdata/mail/... or is this the first file which fails there? Also what are the permissions and owner for /home/yellowtent/boxdata/ ?

@d19dotca said in Wordpress not getting updated when app updated?: That happens for me too but I believe that’s intentional as the developer edition is meant to provide more control to the admins. just wanted to confirm this is indeed the case. when the WP developer package is updated, it only affects the version of new/fresh installations and does not affect the existing WP installation . I have put in a note to make future changelogs clearer about this.

You are on the right track, the app would inspect the host header to know from which domain the request came in from and then handle it accordingly. On Cloudron you have to set the multiDomain flag in the manifest also https://docs.cloudron.io/packaging/manifest/#multidomain

@baris oh! I did not expect this to get tracktion that fast. A very welcome supprise Thanks for your awesome work!

Need to check this out, but def cool addition if it can do what’s promised, so much tedium avoided !

I've had different timeouts across different browsers so they lose connection on things like Cloudron web-terminal sessions, which then reload losing the work, unless using screen etc. Sometimes there is also aggressive memory management for tabs that wants to unload things that look idle or use a bunch of RAM. Check the performance settings of the browsers to see if it's set.

@nebulon said in Error logs from NextCloud: investigate what the Cloudron Nextcloud package misses from the Nextcloud AIO bundle, to somehow get the highperformance backend for Nextcloud Talk optionally to work Might this help for the Nextcloud Talk High Performance Backend bit? It's just that bit from AIO bundle https://github.com/nextcloud-snap/nextcloud-snap/wiki/How-to-configure-talk-HPB-with-Docker But I guess for Cloudron it could possibly be simplified further due to the fact Cloudron already has a TURN server (and maybe some of the other parts too? ) @leemuljadi until we've got a solution on Cloudron (which I hope gets some dev attention soon) check out https://github.com/sunweaver/nextcloud-high-performance-backend-setup (via @andreasdueren's post in the Nextcloud Talk high performance backend App Wishlst thread) which seems like the simplest method of getting a Talk HPB set-up in the meantime.