Regarding your problem, both Dropbox and Google Drive support were removed from the server core. For Dropbox there is a barely working app, for Google Drive there is no replacement atm. If you use a different external storage type, then it could be a different problem though. In that case you should take a look into the logs if you can see something.
@alfred,
I am just talking about local storage ( Harddrive attached to my orangepPi(nextcloud)).
I can see the link of the attached HDD, but i cant open it.
I can open it by right clicking on that folder and selecting open in new tab,
dont understant what wrong is going,
Do i need to do any process before upgrade for attached local storage.
Please guide.
Huh, why this?? I mean generally I totally agree to keep the core slim and clean, but if signifikant features like this are removed, there needs to be an app available to add it again. I mean yes I use Nextcloud to get rid of Google and Dropbox, not to then add it again, but others do. And if there is currently no replacement it will just break their Nextcloud as they used it, or did I missunderstand something?
âŹ: Ah sorry just read the gh issue that it is due to google drive (dropbox the same?) security featureâŚ
Weâre having the same issue. Not sure how the claim can be made that NC 13 is 10x faster with read-writes to Samba shares if no one can access said shares through the interface!
@jospoortvliet@spy0r I upgraded to NC 13 beta 3 this morning. However, Iâm still unable to access SMB file shares. This is CentOS 7.4 with PHP 7.1 (Remi)
And when I finally did gain access, it wasnât any faster than in previous versions of Nextcloud.
Note the qualifier âif you use php-smbclientâ. If you donât, no difference Also, it is in sequential read/write so that means only when reading or writing large files.
then indeed sequential file transfers should be a lot faster and/or have lower cpu usage on the server (if your bandwidth is saturated it canât go faster, obviouslyâŚ)
About the blog post title: Using percentage to indicate performance improvements is somewhere between weird and wrong. See the article What We Talk About When We Talk About Performance and consider just saying âx times fasterâ next time.
Itâs only wrong if it doesnât mean what it says ⌠percentage improvements are fine. 85% faster is less than twice as fast, so âx times fasterâ is a bit difficult to use. â0.85 times fasterâ?