I'll do a little bit more experimenting and report back, I just noticed that a plugin I installed has reviews saying that it bricked people's NC installs.
It's been said in this forum and the Nextcloud forums: Use plugins as little as possible. It just doesn't work reliably, in particular with 3rd party plugins.
I used to love it when systems allowed modifications (like Firefox, Nextcloud etc.) - now I avoid it like the plague, because such mods are suddenly no longer supported or break the system. Either a system offers more or less everything you need out of the box, or I don't want to use it in the first place.
@fbartels Thanks for the tip! I also had that as a first guess and have already increased the memory for redis a few weeks ago. Unfortunately, since then no improvement. Also I have increased the memory for mysql, unfortunately also without success.
I maybe found the reason. We put all users in specific groups. Only users in this group can share by username with other users in this particular group. Now I created a group Kontakt and put all users in it. All users can now share files with others. I hope this opens no security hole and maybe there is a switch for this feature, but it works.
Feedback would be nice.
I must admit; I have a tons of apps enabled (93 of them)
but yes my nextcloud also complain
There are some warnings regarding your setup.
The PHP OPcache module is not properly configured. See the documentation ↗ for more information.
The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply opcache.interned_strings_buffer to your PHP configuration with a value higher than 8.
@Sam_uk such data migration is always a bit tricky. You might be able to first install a fresh Nextcloud without the Cloudron user management and then import a backup from the other instance. Only do this in a test app instance first though.
@LoudLemur looks like the DNS record was pointing to a Cloudron which didn't have any app installed on that (sub)domain. If a Cloudron server as such just gets deleted, then the DNS records are not automatically cleaned up, since there is nothing running anymore to do that.
@msbt no worries, I'm glad I for once can share my own solution to this great community 😉
Most of the time it's the other way araound 😆
Anyway, you have a point that Nextcloud's server-side encryption probably isn't worth it and therefore I'm also experimenting with Seafile, which has the possibility of client-side encrypted libraries. And in my (short) experience so far it is much much faster.
But unfortunately Seafile isn't currently available on Cloudron.
@girish & @mehdi - thanks for your advice! It gave me the idea to Tailscale. I installed it on the Cloudron server and was able to successfully mount a shared folder from my Synology using cifs. However, even though the data persists between reboots, I don't see the data on the Synology, even when I'm logged in as the root user. I'm not quite the linux expert, but I noticed that when I changed Nextcloud's appdata folder to point to the mount, it created it as a "root" user. On the Synology, I created a Cloudron user that has the necessary permissions and I mounted the shared folder with the Cloudron user, password, and domain. So, I'm thinking this has something to do with user IDs not matching up or something like that.
I'm nervous about moving forward since I can't actually see the data on my Synology. Would you or anyone else have any advice?
By the way, this is how I mounted it:
sudo mount -t cifs -o credentials=/etc/nas-credentials,vers=3.0 //nas/Cloudron /mnt/nas
In fstab, the command is:
//nas/Cloudron cifs -o credentials=/etc/nas-credentials,vers=3.0,_netdev,auto 0 0
the issue could start with a lot of concurrent users and a lot of small changes to file, due to SMB not working at FS lvl but at file level/block of data.
IF hetzner would offer NFS, that could be a solution or better even if there would be support for iscsi.
@nebulon Oh thanks, going to test this for one user without any specific nextcloud app installed and see how it goes, should be enough along with reconfiguring his nextcloud local client to the new URL 🙂