@amg-web I mean the recovery mode, which you can enable for the app in the "Repair" section on the app configure view in the Cloudron dashboard.

@girish I ended up migrating back to my home server a lot faster than I thought and so this is no longer an issue but when I forgot I went from a machine with 32GB of RAM to a VPS with 2 so this was likely it. When I first installed Cloudron is was randomly shutting down and failing to restore becuase it was running out of RAM.

I found a couple of similar issues - https://github.com/ONLYOFFICE/DocumentServer/issues/33 and https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/96

Can you check the below:

Are the certs for the onlyoffice installation valid? Give the onlyoffice app more memory.

@necrevistonnezr
I use both for on prem storage and for wasabi storage

@necrevistonnezr It is, I skimed the start of that thread, and as it was unrelated, I just assumed it was not about my issue.

@timconsidine

@privsec : are these problems stem-ing from the encruption plugin ? Rather than Nextcloud itself.
I have used NextCloud for 5+ years and I struggle to remember any problems at all.

It is certainly possible. I really don't want data stored unencrypted but it is looking like that is the only option.
All my data is stored on Wasabi, and they do have data stored at rest, but they store the encryption keys in meta data (from what I recall)

@necrevistonnezr

Rarely problems, and if any, I was able to solve them via the occ tool - thought I stayed away from encryption as my server is at home with nextcloud on an encrypted home folder so I don't need e2e encryption on top of that.
Also, activate only the really necessary addons.

Ill have to look into the OCC tool, hopefully all my data isn't lost.

@jagan I think in your case, the issue was with the google external storage primarily. I think there is a general issue with plugins where whenever nextcloud updates they are slow to catch up and something fails.

@robi Looks like non-cloudron users hit the same issue - https://github.com/nextcloud/server/issues/13556#issuecomment-848314122

The root cause is that the nextcloud package is configured to log to the console (stdout / stderr) instead of a file. Nextcloud tries to open the stdout/stderr and this fails. Ideally, nextcloud can show a graceful error message that logs cannot be viewed from inside the app because it is logging to the console. Workaround is to use the cloudron logs viewer to view the logs - which IMO is the correct place to view logs (for all apps and not just nextcloud). After all, if the app is not working, one cannot view the logs within itself.

@murgero Thank you
Before seeing this, I decided to be a 'windows user' and reboot the cloudron server.
I guess same effect, but will definitely do your more limited kick next time.
And yes it is working again.
Many thanks

@nebulon Yep, thank you, confirmed it reset itself.
Took >24 hours for recalculation but it is sorted 👍

@necrevistonnezr right I was hoping for a --skip-plugins or equivalent but couldn't find one (the WP cli tool has something like that for skipping loading of themes and plugins).

Thanks All! I'll have to dig into this a bit further, but this gives me a good start.

@dylightful this may have to be fixe upstream then. Generally we have seen various issues with the Nextcloud encryption and additional addons together. I would recommend to not use the encryption with Nextcloud, since if anything goes wrong there, it is very hard or impossible to recover the data.

On focal, this seems to libmagickcore-6.q16-6-extra. I have added it for the next nextcloud package update.

@cloudron-n said in Obvious noob questions (apologies):

does Cloudron keep NextCloud up to date?

This is part of the magic that makes Cloudron such a great platform. Nextcloud is integrated

This page describes how it works
https://docs.cloudron.io/updates/

On Nextcloud, the data directory is /app/data. In hindsight, this was a mistake and it should ideally be /app/data/datadirectory or something. We tried to fix this long ago, but it was complicated since nextcloud complains if you change the data directory, so we left it as-is.

Because of the above quirk, there are two htaccess files. One for the data directory itself (.htaccess) and one for the code directory (htaccess).

When we eventually move the data directory to be a subdirectory, the .htaccess will move with it.

@bluxomat
When creating an instance check the option as shown in the image below.

755cffb2-90b6-44aa-9ab9-568d51deca0a-image.png

That way, when you log in with the admin user, the user quota option will appear

Did someone saw stable20 LDAP: make actually use of batch read known groups within the changelog? Nextcloud has LDAP group support but we were never able to use Cloudrons user groups. Any chance this could change now?

EDIT: Hm okay maybe I'm on the wrong path. I always assumed you can map LDAP groups to groups within Nextcloud (to determine folder/access rights) but this seems not to be the case. Correct me if I'm wrong.

@nebulon

The bug has been fixed in the current updated 20.0.8 version of cloudron!

Thanks for a delightful experience.

Edit: This thread can be marked solved I think.