@christiaan Yes, it's mostly harmless. https://github.com/nextcloud/server/issues/13556 is the bug upstream. Looks like they will fix it soonish (there is some recent activity).

We've pushed a package update just now to fix this.

Thanks nebulon. For anybody following this, I did have to install the apps to get sync up and running properly. The automated configuration file didn't work for some reason. At the very least I had to follow these instructions precisely (including making device-specific passwords): https://docs.nextcloud.com/server/18/user_manual/pim/sync_osx.html

@girish The update for Cloudron was installed now, then the location in the Nextcloud app was saved again. Now it is error-free. Thanks for your personal support!

Hi, I am interested in using Object Storage for Nextcloud primary storage as well. Currently, an object storage provider can only be added as external storage. It would be great to be able to configure some s3-compatible Object Storage, which costs much less and can be more durable than Volume, as the primary storage. As I understand it, this is not yet possible in Cloudron. Would it be possible to enable this option?

Just tested again with 3 other people (so four total) and again it worked great, aside from the fact one person couldn't see or hear one other person (odd).

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

All sorted now

@iqweb I've not looked at it yet but also just seen this tutorial https://help.nextcloud.com/t/howto-setup-nextcloud-talk-with-turn-server/30794

Thanks! Makes sense! I'll message support.

For future reference, you have to use resize2fs to grow the ext4 partition when you expand the disk size. This is atleast the case for most public cloud block storage and is a manual operation. Cloudron could potentially do this but I am guessing there is a good reason to not do this automatically, otherwise public cloud folks would have done this already

@nebulon said in Nextcloud Hub/18: The update is already rolled out. We just do it slowly for Nextcloud since in the past, Nextcloud updates caused lots of support requests on our side. I'd rather hurry, there are security advisories out: https://adv-archiv.dfn-cert.de/adv/2020-0324/

@miloskroulik Might be best to take this up in the nextcloud forum. Atleast, I can't find any docs on when the syncing happens and how it can be triggered manually. The --update <username> did end up doing a proper ldap search in my installation (as seen in the /home/yellowtent/platformdata/logs/box.log). I had run ldap:list (or maybe it was ldap:search, i forget) previously and it did not list the user. After the update, it listed the user.

@necrevistonnezr this was the one https://forum.cloudron.io/topic/1971/urgent-security-issue-in-nginx-php-fpm

The Cloudron Nextcloud package is using apache+php instead of nginx, so as far as I understand the issue this does not affect Cloudron instances.

Please also try restarting the internal DNS server (unbound) from the System -> Services page.

@girish Thanks!

@nebulon Hi. Yes, indeed, the instance has 20gb. I deleted files from trash in Nextcloud and got back to normal with 6gb of free space.