Cloudron Forum

@girish That did the trick. Thanks!

@imc67 said in Updating FreeScout failed: @girish said in Updating FreeScout failed: @imc67 there is a bug here . Can you apply this one liner and then set the memory limit https://git.cloudron.io/cloudron/box/-/commit/750f313c6a36d8d961892df4a41cb7c41faa1f1b ? You have systemctl restart box after you change that line in /home/yellowtent/box/src/apps.js. Will try this in a few hours @girish this solved the bug, thanks!

@drpaneas Just give that redis more memory. The "e1ca318a" is the app id. If you put in the search in the apps view, you will know which app's redis needs a bit more memory. It was reported earlier that pixelfed's redis needs more memory after the update. I guess this is because of update to Redis 5.

@johnbolt You should try a forced refresh (ctrl + shift + R on most browsers), to avoid cache issues

@girish ah so that’s because I was messing with dind for GitLab runner... whoops. Thanks for taking a look!

@imc67 I made https://git.cloudron.io/cloudron/box/-/issues/717 for keeping mail backups separately from the box backups.

@valkalon Cloudron support is still the best

Solution : In my case, /home/yellowtent was owned by root, gpg was trying to create "~/.gpg". My fix : "chown yellowtent:yellowtent /home/yellowtent/"

There we go, it is updating now. Thanks so much.

Right, we don't recommend upgrading since we trying to keep our testing simple. Security updates are enabled for the base packages that we use. We don't really use many base packages - nginx, collectd. Rest are all containerized (mysql/mongo/redis/email etc) and updated via our docker updates. Docker, nodejs itself are all installed from binaries and not via apt.

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

Thanks all! I just installed it on 1 of my Cloudron servers (at DO) to see and experience if and how it works.

@girish All these years and it’s still a pain >_< Edit: I’m referring to Linux distros ofc, not Cloudron.

The app does some reason in unresponsive on first start after an update. I had to restart the app after the app and it starts up fine. For the next update, I will see if this happens again. If that's the case, I will fix up the package to restart the app. I couldn't find anything in the release notes

Thank you @nebulon The update has not happened it. Shows the same error yet. Will patiently wait however if nothing is needed to be done at this point. Thanks!

@mishkalidas When there is an update, you will see an update button in the UI. This is the same for apps - when there is an update, you will see an update indicator in the app grid. There is no other supported update mechanism. Let me know if I misunderstood your question.

@amg It seems there are multiple issues here: Restore via CLI not working. Can you tell me more what the error is? Where are you seeing 'Already Setup'? Is this when installing Cloudron? (But the post starts with 'after update' to 3.4) Please give us more information to help you out.

It seems that the Lychee-Laravel version is more rich in features, possibly a candidate for next update?