@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.

Thank you @nebulon for solving this issue off-forums. For future reference: problem was caused by the external storage being unmounted after a reboot. Remounting the storage drive (I use a netcup VPS) and then repairing in the Cloudron dashboard solved the problem. Including the mounting in /etc/fstab solved this issue for following updates/reboots.

@fbartels Indeed! I changed the title accordingly.

@nebulon Could https://git.cloudron.io/cloudron/nextcloud-app/issues/61 be related?

The update to 15 is pushed out now. Please report any issues you encounter if that is the case.

I dont see how this can be supported by nextcloud, unless it would scan the authors inbox. Maybe the nextcloud email addon is able to handle this, but you should probably ask nextcloud support about this.

As a first attempt, you could try to restart the box process with systemctl restart box Also maybe look at the system logs, in case there are any hints for errors.

@yylevas No worries! Glad you found the problem. Breaking stuff is the fastest way to learn!

Lets further handle this in the opened issue tracker item.

Have pushed an update that enables this.

You were right. "unbound" was failed. Turns out IPV6 was disabled which was causing "unbound" to fail and in turn causing the issues with resolving domain names in Nextcloud. This is a vanilla install of Ubuntu 16 LTS so I'm not sure what happened. I enabled IPV6 and rebooted and everything started working. Thanks for the tip.