i have the same Problem at home i use Cloudron 4.4.4 there int runs fine, but yesterday i installed a new clorudron installation v. 4.4.5 and ther i have problems with collabora. when i open a word file from nextcloud the first time it opens, but when i close the file and 30s later i open it again collabora doesnt load, it stays at 1% loading and i cant opan any other file.

@iamthefij Can you reproduce the setup in our demo - https://my.demo.cloudron.io (username and password is 'cloudron') ?

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

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

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

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

I host it at home But I can recommend using VPS from hetzner and if you want more storage you can use https://www.hetzner.com/storage/storage-box

Ok - here's how I got it working. This was worked out by checking out various posts on the Nextcloud and also an excellent, simple tutorial on my vps host's tutorial site, Hetzner. This is a detailed how-to to enable voice/video/screensharing support in Nextcloud Talk installed in Nextcloud on Cloudron that is available from outside the local network by installing coturn turn/stun server. Prequisites: Nextcloud and Nextcloud Talk installed on Cloudron 'A' record setup on your DNS registrar's admin panel pointing to your cloudron server's public ip address with a name record chosen by you e.g. 'turn' All the below commands should be run as root or with sudo. Install coturn and persistent iptables: apt-get install coturn iptables-persistent Temporarily stop coturn: systemctl stop coturn Open ports for use with coturn (default ports in this example) iptables -I INPUT -p tcp --dport 5349 -j ACCEPT iptables -I INPUT -p udp --dport 5349 -j ACCEPT iptables-save > /etc/iptables/rules.v4 Enable coturn daemon Open the file /etc/default/coturn and remove the # in front of TURNSERVER_ENABLED=1 (i.e. uncomment it) Make a backup of the original turnserver.conf file: mv /etc/turnserver.conf /etc/turnserver.conf.orig Create new /etc/turnserver.conf using nano or vim or whatever editor you choose as below referring to the comments for changes to be made for your installation: #the port that you opened using iptables tls-listening-port=5349 fingerprint lt-cred-mech use-auth-secret # this is created by running the sed command in the detailed instrucions static-auth-secret=replace-this-secret # the domain that you create an A record for realm=aaa.bbb.ccc total-quota=100 stale-nonce=600 # the host domain certs that were created by cloudron on installation cert=/home/yellowtent/boxdata/certs/xxx.yyy.host.cert pkey=/home/yellowtent/boxdata/certs/xxx.yyy.host.key # this will be created using openssl dh-file=/home/yellowtent/boxdata/certs/dhparam.pem cipher-list="ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384" no-sslv3 no-tlsv1 no-tlsv1_1 no-stdout-log # this can be watched using tail -f for troubleshooting log-file=/var/tmp/turn.log # once everything is confirmed working you can comment out the above line & uncomment the following #log-file=/dev/null no-loopback-peers no-multicast-peers proc-user=turnserver proc-group=turnserver Create DiffieHellman (dhparam.pem) key exchange file for better TLS security. (this can take sometime - be patient) openssl dhparam -out /home/yellowtent/boxdata/certs/dhparam.pem 4096 Start coturn systemctl status coturn In Nextcloud, login as an admin & go to the settings page & scroll down to the Talk settings. Add a new TURN server using the domain name you created an A record that appears in your turnserver.conf file after realm= followed by a colon with the tls-listening-port number that you opened - e.g. aaa.bbb.ccc:5349 and for secret enter the static-auth-secret in your turnserver.conf. Choose UDP and TCP. It should then check that it is working and a checkmark will temporarily appear confirming it works. You can also optionally enter the same server:port combination for adding your own STUN server. You can go ahead & test a voice & or video chat between 2 clients. To troubleshoot you can tail the latest log file while attempting a chat e.g. tail -f /var/tmp/turn_2019-08-23.log

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

Changed As it is the default configuration for Roundcube it is working like intended and we could leave it like this? I don't think its a rare use case but maybe it could be added to the documentation (which I always found very helpful).

@girish Thanks for your response!

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.

As @msbt mentions, the proper solution is to have the preview generator fixed, not to create band-aids for that on the platform level. @necrevistonnezr maybe you can comment on that github issue to raise awareness, afterall it is basically just a missing feature of the application, not Cloudron as such.

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

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.

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