18.0.4, 17.0.6 and 16.0.10 are here! Plus Beta 5 for Nextcloud 19!

Originally published at: https://nextcloud.com/blog/18-0-4-17-0-6-and-16-0-10-are-here-plus-beta-5-for-nextcloud-19/

19

It is that time again: updates for the stable series of Nextcloud are available now.

As always, these include stability and security improvements that are designed to be a safe and quick upgrade.

An important improvement is that admins now can disable user flows since they can have quite some impact on the performance of a system and you might not want to give users the ability to define their own flows while still making use of the administrator level ones. Can be enabled by running:
occ config:app:set workflowengine user_scope_disabled --value yes

You can find the full changelog of fixes and improvements for 18.0.4, 17.0.6 and 16.0.10 on our website.

Note: running web facing software without regular updates is risky. Please stay up to date with Nextcloud releases of both the server and its apps, for the safety of your data! Customers can always count on our upgrade support if needed!

Youā€™re probably happy to learn that keeping your apps updated with Nextcloud 18 has become easier: a simple update all button takes care of it.

Nextcloud Hub ā€“ the most successful release

We always recommend you to get the latest and greatest! Our updater statistics shows that Nextcloud Hub is the most deployed release, with 55% of the total user base of Nextcloud. Nextcloud 17 use is down to 20% while Nextcloud 16 is on only about 10% of servers!

If you havenā€™t updated to Nextcloud 18 yet and youā€™re wondering whatā€™s that awesome about it, check out all the awesome features that came with it! Nextcloud Hub introduces many new features and improvements. Among those is that we now ship, by default, Nextcloud Talk, Groupware and ONLYOFFICE. If you are upgrading, you will move from the Gallery app to the new Photos, but Talk, Groupware and ONLYOFFICE will not be installed automatically as we donā€™t want to surprise admins. However, we do recommend to install them yourself!

If you need some time to plan an upgrade to 18, we recommend to update your existing stable release in the mean time to benefit from the about 37 changes in 17 and over 2 dozen in 16. Note that if you are still on 15, this release is unmaintained and you should upgrade as soon as possible.

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.

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, and the job safety of you as system administrator.

Nextcloud 19 is coming and itā€™s time for testing!

As you might already know we hit feature freeze a few weeks ago and now itā€™s Betaā€™s time!

We made beta 1,2,3 and 4 available the previous weeks while many fixes and improvements were made.

Now we are calling for testing for Beta 5!

We are working hard on stabilizing Nextcloud 19 for a release and it is time to get involved, if you havenā€™t yet! Our fifth beta has appeared on our servers and you can use our famously easy updater to get it on your server and give it a try, or grab it from our download server.

Nextcloud 19 beta 5 (zip)

We want to make sure that upgrades and day to day usage are smooth and as bug-free as possible. Any other feedback, of course, is welcome! Next week we will release Beta 6 which will be followed by the first release candidate hopefully on May 7.

Nextcloud 19 needs testing, bug reporting, bug fixing and some polishing to be perfect. The best time to get involved is now! Here is a list of pending PRā€™s you can help us with!

Share your opinion and inspire others to liberate their data!

We appreciate your feedback ā€“ it is a great way to contribute and weā€™d love to hear your thoughts on your favourite features and functionalities of the stable releases!\
Help us spread the word about Nextcloud and write a review in one of the following platforms (or all of them if you prefer ). Whatā€™s the best thing about Nextcloud so far?

Thanks a lot!

5 Likes

Hey.
Your Website https://nextcloud.com/changelog/#latest17 shows Version 17.0.5 as the last changed Version (In 17th tree).

thereā€™s no changelog for 18.0.4 either.

2 Likes

Yes, the last change log is for version 18.0.3 . What changes are in this version?

Hello,
For 18.0.0.4 and 19 beta 4, I have the same error :

* ## Create backup

Parsing response failed. <html> <head><title>504 Gateway Time-out</title></head> <body bgcolor="white"> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> 

Nextcloud 19 is install on localhost and nextcloud 18 on a public server. Both work with Nginx and MariaDB .

Edit : It works with command line :
sudo -u www-data php /var/www/nextcloud/updater/updater.phar

Nextcloud Hub the most successful release ?
I place NC 18.0.0 as bad as NC 14.0.0 !
So much bad bugs :bug:
With 18.0.4 Photos is nearly great but 18.0.0 was painful

1 Like

Update via web went smooth as always and Iā€™m happy that I have the gallery-preview again. :slight_smile: The performance, again, improved a bit. Real happy so far.

I found one smaller issue in the photos app, maybe one of the others users can make a quick crosscheck:

2 Likes

Yes, I tested it quickly, the same error occurs to me :thinking:

1 Like

ā€¦now I am getting a Windows popup telling me 18.0.4 is availableā€¦still awaitng for the changelog.

With this said, I am very appreciative (and I am sure I am speaking for someone else, too) of Developersā€™ hard work on pushing this through.

Never had issues upgrading since starting with Nextcloud 13.

Upgrading from 17.0.5 today. However upon checking I was offered to upgrade to 17.0.6 first to my surprise which I did. This went well and web-updater completed. Then I checked again for an update and 18.0.4 appeared. When starting this the updater made a backup successfully and ticked all the other boxes. Then Iā€™d proceed only to end up with a white screen.

Perhaps updates were happening too short after each other. Is there something running after upgrade which needs time to complete before attempting another upgrade?

Anyway, now working on restoring to 17.0.6 and making another backup of all the latest data to ensure all is secured before trying again to upgrade to 18.0.4.

Edit:
Just expanding for educational purposes and future reference on getting through this update
After successful restore, I tried again with web-updater with same result. Download done, all boxes ticked and then blank screen. End of upgrade.

Went through the terminal and entered:

sudo -u www-data php occ maintenance:mode --on
sudo -u www-data php occ upgrade

That (re)started the upgrade process. Appeared to go well with a whole lot of updates and checking until:

Checking for update of app spreed in appstore
Update app spreed from appstore
Repair error: Repair step ā€˜OCA\Talk\Migration\FixNamespaceInDatabaseTablesā€™ is unknown
PHP Fatal error: Cannot declare class OCA\Talk\Migration\Version8000Date20200331144101, because the name is already in use in /var/www/nextcloud/apps/spreed/lib/Migration/Version8000Date20200331144101.php on line 54

I deleted this specific file risking loss of data. Iā€™m just having a ā€˜familyā€™ instance so I proceeded.

After deletion I ran again:

sudo -u www-data php occ upgrade
It continued with updating the other apps and finished in ā€˜Update Successfulā€™.

After that just:

sudo -u www-data php occ maintenance:mode --off

And back to the browser to check my instance. All good and upgrade successful and no loss of any data.

Edit2:
Do have an integrity issue now with spreed app. That was kind of expected. Will have to extract the original files somehow and restore the folder I deleted them from. Found them here: spreed/lib/Migration at main Ā· nextcloud/spreed Ā· GitHub

1 Like

Iā€™m getting this docker error;
Pulling nextcloud (nextcloud:18.0.4)... 18.0.4: Pulling from library/nextcloud ERROR: no matching manifest for linux/amd64 in the manifest list entries

Looks like the linux/amd64 OS is missing on the docker hub. Running Intel Nuc with:
NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04"

Hi @marinela,

I just noticed the blog post states disabling flows for users works with

occ config:app:set workflowengine userscopedisabled --value yes

but after that didnā€™t work for me I checked the code and found that it should be

occ config:app:set workflowengine user_scope_disabled --value yes

ā€¦which works like a charm. Probably the underscores just went missing?

Cheers,
Simon

Iā€™m using the nextcloud:fpm-alpine image.

Calling docker-compose pull && docker-compose up -d is not updating NextCloud 18.0.3 to 18.0.4.

Might be due to: https://github.com/nextcloud/docker/issues/1089

If maintainers do

  • a quick

  • out-of-cycle update

  • without changelog and

    • that it is distributed to everybody (instead of this slow-rolling-release cycle they are usually doing)

It is a good indicator for that this release is fixing (ā€œonlyā€) some critical security issue. Otherwise, theyā€™d breathe in and out before, plan it, release it in steps and proudly make announcements, I guess.

Now it seems that this update breaks some installations, which is of course bad, but its probably better than instances and servers taken over or destroyed by people who figured out an exploit to something.

Thanks, maintainers and contributors!

1 Like

Mmhmm. Unfortunately collabora is vital for me so will be moving back to 18.0.3.

I have NC18 in nginx and collabora in docker since long. It works also after update. And by the way update was very smoth. Why did you have to remove all files in var/www? Maybe the fault is yours and not NC18 update.

How is your set-up and how is collabora installed?

I use the collabora docker. Iā€™ve already reinstalled the docker instance with no success.

Here is the error - https://pastebin.com/gtcHqWgp

I am no programmer so cannot interpret this. I would go back to 18.0.3, update all apps and try an update again. If it goes wrong I would try upgrade from the terminal.

Yes, Iā€™m not going to continue to derail the topic. I had to manually reinstall the files as the web upgrade failed midway through. Thankfully I have a full backup.

All the same, the rest of nextcloud is fully function. Itā€™s specifically collabora with the issue. A full app reinstallation did not fix it, nor did reinstalling the container.

Since I use postgresql, curious on if thatā€™s the issue. I will indeed try a fresh installation of 18.0.4 to see if it was an upgrade issue.

Did a manual upgrade from my backup instead of the web upgrade. Fixed the problem - have removed my previous posts to avoid misinformation.

I need to stop jumping the gun on these things.