@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.
Ok so quick update here: I was following the mount procedure from the first link and it's looking good! However, I started with a fresh installation instead of moving my files around, but seeing as it worked out, migrating an existing installation should be no problem either.
So what I did:
deployed a new Cloudron with Nextcloud installed on a fresh CPX21 on Hetzner Cloud (kept it at 40GB though, might scale down if performance allows it)
mounted a 5TB Hetzner Storagebox via sshfs into /mnt/cloud and added it as Cloudron volume (/media/cloud)
mounted that volume into the Nextcloud app (uncheck read-only)
change the datadirectory in config/config.php from 'datadirectory' => '/app/data', to 'datadirectory' => '/media/cloud',
cp -r /app/data/admin to the mounted volume and touch .ocdata in /media/cloud
That's pretty much it I reckon, if you log in now you have this extra storage available:
I have both, uploaded a few GB manually and the rest via sync client, no errors so far. A restart won't change the datadirectory, so this should continue working after reboots. Encryption is also enabled and working as intended, still waiting for something that doesn't work properly.
@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)
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.
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.
@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 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.
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.