Desktop client 3.4.4, Nextcloud 23.0.3 and 22.2.6 are out, bringing a series of bug fixes and improvements

Originally published at: https://nextcloud.com/blog/nextcloud-23-0-3-and-22-2-6-are-out-bringing-a-series-of-bug-fixes-and-improvements/

Update your server!

Nextcloud 23.0.3 and 22.2.6 are released! As always, minor releases include stability and security improvements that are designed to be a safe and quick upgrade. We also published a minor bugfix release of the desktop client and a test version of the upcoming 3.5 client release!

What’s new?

Among the interesting changes are an option to dis-allow the creation of local storage connections from the web interface. This is designed for situations where the sysadmin managing the system graphically should have less ‘power’ than the admin on the back-end administering through the CLI. Local storage access could be a security issue. This can now be configured in config.php.

Another notable change is that it is now possible to write the audit log to syslog and systemdlog. This has been documented. Besides these slightly larger changes, dozens of smaller fixes and improvements make user and admin life better in this set of releases.

You can find the full changelog of fixes and improvements for 23.0.3 and 22.2.6 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!


There’s a option for a beta channel now!

Fresh Desktop Clients!

The desktop client team also released a minor version, 3.4.4, with a few small fixes:

  • Do not remove files from a Group folder and its nested folders when it is renamed or removed while not allowed.
  • Bugfix/prevent overflow with mtime
  • Old submodule url does not work anylonger

For those of you up for some testing, desktop client 3.5RC1 is also ready for some attention! You can get it here.

One feature that comes with this new release is the ability to choose the Beta channel for releases to help test upcoming RC’s! Our team also brought this feature back to the 3.4 series, it is already in 3.4.3 and 3.4.4 so you can just set your client in the settings to the beta channel to test the RC out!

Get updating!

End of public support for Nextcloud 21

Nextcloud 21 is not being maintained, so start preparing your move to 22 or 23 if you haven’t yet, or check out or Nextcloud Enterprise offerings with up to 5 years long term support. As always we strongly recommend you update to ensure you have a secure and reliable content collaboration platform that respects your digital sovereignty!

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 generally 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 a system administrator.

9 Likes

Hey guys.

Really chuffed for the announcement, but the changelog link is kinda messed up.
Points to…
https://nextcloud.com/blog/nextcloud-23-0-3-and-22-2-6-are-out-bringing-a-series-of-bug-fixes-and-improvements/nextcloud.com/changelog

Also, the actual changelog page is showing version 23.0.4. But the download links shown for it are broken. (As it’s not released yet)

The upgrade to 23.0.3 was smooth though.

1 Like

Thanks for pointing out the broken link @LogsCon. It’s fixed now :slight_smile:

thankyou! updated fine here 23.0.2->23.0.3 so far so good!

whoops, fixed. Made a mess though, first thinking the 23.0.3 was wrong and it should be 23.0.4 :sob:
But I think all is now :sun_with_face: :sunflower:

1 Like

It seems server 23.0.4 is not out yet.
The server download URL returns a 404.

1 Like

the release is 23.0.3, the .4 was a mistake in the changelog generation that confused, well, everyone including me :wink:

1 Like

I installed the 3.5.0 RC1 desktop client on my Debian Notebook (compiled from source) and it seems to run fine. No issues so far.

I’m encountering the following error upgrading to 22.2.6

$ ./occ upgrade          
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Updating database schema
Updated database
An unhandled exception has been thrown:
Error: Call to undefined function GuzzleHttp\Psr7\modify_request() in /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Auth/AuthHandler.php:56
Stack trace:
#0 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php(35): OpenStack\Common\Auth\AuthHandler->__invoke()
#1 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Transport/Middleware.php(22): GuzzleHttp\PrepareBodyMiddleware->__invoke()
#2 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php(75): OpenStack\Common\Transport\Middleware::OpenStack\Common\Transport\{closure}()
#3 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(331): GuzzleHttp\HandlerStack->__invoke()
#4 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(168): GuzzleHttp\Client->transfer()
#5 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(187): GuzzleHttp\Client->requestAsync()
#6 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Api/OperatorTrait.php(115): GuzzleHttp\Client->request()
#7 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Api/OperatorTrait.php(123): OpenStack\Common\Resource\OperatorResource->sendRequest()
#8 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Resource/OperatorResource.php(55): OpenStack\Common\Resource\OperatorResource->execute()
#9 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/ObjectStore/v1/Models/Container.php(142): OpenStack\Common\Resource\OperatorResource->executeWithState()
#10 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/SwiftFactory.php(266): OpenStack\ObjectStore\v1\Models\Container->getMetadata()
#11 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/SwiftFactory.php(247): OC\Files\ObjectStore\SwiftFactory->createContainer()
#12 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/Swift.php(62): OC\Files\ObjectStore\SwiftFactory->getContainer()
#13 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/Swift.php(105): OC\Files\ObjectStore\Swift->getContainer()
#14 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/ObjectStoreStorage.php(312): OC\Files\ObjectStore\Swift->readObject()
#15 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Common.php(196): OC\Files\ObjectStore\ObjectStoreStorage->fopen()
#16 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Wrapper.php(247): OC\Files\Storage\Common->file_get_contents()
#17 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Availability.php(264): OC\Files\Storage\Wrapper\Wrapper->file_get_contents()
#18 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Wrapper.php(247): OC\Files\Storage\Wrapper\Availability->file_get_contents()
#19 /var/www/labfoto.it/nextcloud/lib/private/Files/View.php(1171): OC\Files\Storage\Wrapper\Wrapper->file_get_contents()
#20 /var/www/labfoto.it/nextcloud/lib/private/Files/View.php(601): OC\Files\View->basicOperation()
#21 /var/www/labfoto.it/nextcloud/lib/private/Files/Node/File.php(56): OC\Files\View->file_get_contents()
#22 /var/www/labfoto.it/nextcloud/lib/private/Files/SimpleFS/SimpleFile.php(90): OC\Files\Node\File->getContent()
#23 /var/www/labfoto.it/nextcloud/lib/private/App/AppStore/Fetcher/Fetcher.php(154): OC\Files\SimpleFS\SimpleFile->getContent()
#24 /var/www/labfoto.it/nextcloud/lib/private/Installer.php(432): OC\App\AppStore\Fetcher\Fetcher->get()
#25 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(427): OC\Installer->isUpdateAvailable()
#26 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(273): OC\Updater->upgradeAppStoreApps()
#27 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(132): OC\Updater->doUpgrade()
#28 /var/www/labfoto.it/nextcloud/core/Command/Upgrade.php(235): OC\Updater->upgrade()
#29 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Command/Command.php(255): OC\Core\Command\Upgrade->execute()
#30 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run()
#31 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#32 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#33 /var/www/labfoto.it/nextcloud/lib/private/Console/Application.php(209): Symfony\Component\Console\Application->run()
#34 /var/www/labfoto.it/nextcloud/console.php(99): OC\Console\Application->run()
#35 /var/www/labfoto.it/nextcloud/occ(11): require_once('...')
#36 {main}%                           

@lrkwz

Please open a new thread in the support section and use the issue template. This thread is a news item and not the appropriate place to ask for technical support. Also we would need more info to be able to help. That’s where the issue template comes into play… :wink: If I had to guess, I would say it’s probably a third party app that is causing the issue…

ok, thank you and sorry. Thread is Error upgrading to 22.2.6

I have an uncertainty I was wanting to clear up, with respect to an upgrade from NC 23.0.2 to NC 23.0.3 here.

If anyone is familiar with the behaviour of NC’s “updater.phar” CLI utility, I would greatly appreciate your input.

Please look at the OPcache warnings problems.
OPcache is created per PHP version on the server. The cache is by default not user based.
So one can set these values to extremes and stil get warnings.
Why is OPcache needed next to Redis that is user based? This config is in the manual.

1 Like

Same problem here.
The provider support for my webserver sais (german):
dieses Problem tauchte mit der aktuellen Version von Nextcloud auf, wir haben die “Fehlermeldung” Intern geprüft und das gleiche Ergebnis erhalten wie Sie.

Grundsätzlich haben weitere Prüfungen ergeben das diese Meldung bis auf das sie angezeigt wird und das als störend empfunden werden kann, keinerlei Auswirkungen auf die Funktionsweise der Nextcloud hat.

Aber ziemlich sicher auf die Performance. :wink:

But most likely on the performance. :wink:

If you want to have full control, web hosting packages are rather suboptimal and often limited in terms of tuning options. But basically the hosting provider is right: Warnings are not error messages and can be ignored with Nextcloud still working. Whether you need or want to have the feature or the optimization that a particular warning message suggests, is of course another story…

Good to hear!!

When the server is used by multiple clients, this warning should be given by all installed applications that use the same PHP version. So it does not concern NC only.
The warning states it is a ‘configuration error’. But that is not the case. It is default behavior of OPcache. This type of cache is on server level, not per user in default installations. That is why you can ‘upgrade’ all vars, untill you have reached max server memory and alle files.
The OPcache situation that is evaluated by NC script can only be archieved as successfull when the server PHP version only serves one NC installation and perhaps a simple website. Those are my findings.
In my opinion this is not a configuration error, but just ‘information’ that should not lead to a missing V in the results. There could be just this info below that. It is not an error, nor a security problem.

Maybe there are some implications that even you or your hosting company doesn’t know about, that are important enough for the Nextcloud devs to implemet this warning. And for this purpose, they used the already integrated messaging system and do not want to program a hole new system. You can always argue about the wording and of course you can always make things better. In the end, it comes down to priorities and the amount of work involved. Feel free to open an issue or a pull request on GitHub, with your suggestions…

Maybe, but we’re not perfect either of course. Maybe it is a little over the top. But if you, as admin, are sure that it is OK, then I guess you can deal with a single red issue getting reported, I hope.

And of course - a well argued pull request to improve things (like, downgrade to yellow warning, or perhaps some detection method of how bad things are) would be super welcome - @Hendrik might know enough to do that!

1 Like

We host our own server for multiple clients. And our server is fine and up-to-date. I know after investigation that these warnings are not relevant. But clients get confused since they always got a green V after this configuration control.
I’d suggest a config option Y/N for this control item. There are just two small blocks of code that need an If … before executing.

The Opcache check is done in /settings/lib/CheckSetupControler.php
Line 506 says: // Recommend to raise value, if more than 90% of max value is reached
Disable the If block below that line to disable this warning.
After this there is a memory check If block that is OK.
Below that block is the " if (
empty($status[‘interned_strings_usage’][‘free_memory’]) || "
That needs also to be disabled.
I’ve put /* … */ around those checks.

Perhaps NC can find a nice option to make these checks only done when a result can be expected. In our situation even 32G memory gave these warnings after some time.
And, in fact this Opcache problem is not a NC problem, but with the design of Opcache behavior.