Nextcloud 13.0.5 and 12.0.10 secure and stabilize your server

Originally published at:

Today we make available maintenance releases for Nextcloud 13 and 12, improving the stability, security and reliability of your server. We restrict minor updates to bug fixes and minor, non-intrusive improvements because both home and enterprise users need to know that these upgrades are safe and reliable. Customers can rely on the stand-by upgrade support from Nextcloud GmbH if needed.

There have been recent app updates including Nextcloud Talk for Android and iOS, Nextcloud Deck, our Anti-virus app and dozens more. We urge you to keep your apps updated as well!

Checkboxes in Deck
Dragging an attachment

If you want to learn more about Nextcloud or get involved in our community, join the Nextcloud Conference 2018 in Berlin during the last week of August! See the announcement of our travel support program for more details. We recently announced our first keynote speaker, Linus Neumann, hacker and spokesperson for the German Chaos Communication Club.

Enterprise users looking to accelerate their deployment and get the most out of Nextcloud are welcome at our Enterprise Day on Monday, August 27 at the Park Inn hotel and conference center in Berlin.

Improvements in this release

Nextcloud 13.0.5 introduces 30 changes, most of which deal with corner cases that could cause problems in special circumstances. For example, Nextcloud now allows users to set a avatar if LDAP provides invalid image data. We also improved logging in various areas. Some other updates improve robustness, decreasing the chance of locking issues or retrying rename actions in a different way when samba servers respond with invalid arguments.

A number of improvements fixes UI or textual issues, like highlighting in the upload drop zone or grammar errors on the Settings page. And last but not least, a few minor feature improvements let admins disable encryption or fetching of avatars.

While few of these will be crippling issues for a majority of users, combined it results in a more reliable, consistent experience that comes with a maturing product.

You can find a full overview of changes in our changelog.

Time to upgrade to 13!

Nextcloud 12.0.10 comes with only 3 changes. As this release becomes used less we urge users to plan an update to Nextcloud 13. This also in light of the upcoming Nextcloud 14 release, which will mark the end of maintenance releases for Nextcloud 12. If you are still on Nextcloud 12 and want to keep your data secure, request access to the Long Term Support service of Nextcloud GmbH for further security and stability updates.

Stay safe: keep your server up-to-date!

Minor Nextcloud releases are security and functionality bug fixes, not rewrites of major systems that risk user data! We also do extensive testing, both in our code base and by upgrading a series of real-world systems to the test versions. This ensures that upgrades to minor releases are painless and reliable. As the updates not only fix feature issues but also security problems, it is a bad idea to not upgrade!

This is, of course, also true for apps: keeping them updated has security benefits, besides the new features and other bug fixes.

Of course, if you are maintaining a mission-critical Nextcloud system for your enterprise, it is highly recommended that you get yourself some insurance (and job security… who gets blamed if the file handling system isn’t working as expected?). A hotline to the core Nextcloud developers is the best guarantee for reliable service for your users. timeout. Cannot upgrade!!

It got fixed

update ran in 3rd attempt…

I’ve updated 2 servers in the last five minutes without any trouble.

Thanks for the works.

Same here. This happened when upgrading from 13.0.4 in stable. Before I upgrade two beta instances from 13.0.5RC2 without problems.
Edit: manual download via wget also failed. Is the server overloaded?

Same here when downloading file from on Centos 7. Were able to download ok on the third try.

Next time i will wait a few days before i do the update!


Thanks for maintanance mode!

Now i am unable to continue my work…

1 Like

Same here with raspian. But then I update the OS and tried again. Now it works. I saw there wa an update of certificates in apache…

I think the update script has not yet touched your installation (except for enabling maintenance mode). Can‘t you just disable the maintenance mode to be able to continue your work?

Press “Retry Update” and it should work. If your server is in maintanance mode, disable it from console with occ command.

Zero issues updating with a large user base… Running the “Tech and Me” VM on Ubuntu 18.04 LTS. Thanks for the hard work all the developers put into this.

After re-enabling the nextcould (setting ‘maintenance’ => false, in config/config.php a continuation of the upgrae process with proper result was possible. It also failed with me in first try, but reactivation and second try solved it.

Now it works perfectly! :grinning:

Using web updater.

First I ran into an issue where the updater was unable to delete the theme folder and contents. So I manually removed and continued updated.

Afterwards I ran into this error:

I did solve the issue by reverting my server to a backup (~ 3 weeks ago) and ran the updater successfully.

What caused these errors and why did reverting my server to a backup resolve the updater issues?

Four instances updated via web updater without bigger problems.
One update hung at backup (RPI3 with SDCard)
Doing the maintanance trick in config.php, reloaded page, continued update, finished after 5 minutes.

Same here: five servers updated successfully. Three failed on doing the backup (as far as I remember :-[ ) but after hitting ‘Retry update’ (on top of the page) they walk through without any complaints.

The webupdater wont work for me. Is it better to wait or manually Update?

In the updater that is shipped with 13.0.5 this will not happen anymore, because the maintenance mode is enabled after the backup of code, download and successful extraction happened. So in the worst case some stray files are in the updater folder, that will be cleaned up later in a background job.

See for more details