Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-extended-search domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Maintenance releases 24.0.6 and 23.0.10 are out, plus Hub 3 RC3! - Nextcloud

Maintenance releases 24.0.6 and 23.0.10 are out, plus Hub 3 RC3!

Nextcloud 24.0.6 and 23.0.10 are ready for update

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

You can find the full changelog of fixes and improvements for these releases on our website.
Note: There will be no more releases of Nextcloud Hub 22. Upgrade to Nextcloud Enterprise to continue to get security and stability updates or move to Nextcloud Hub II 23 or 24. Don’t forget that 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.

RC3 of Hub 3

In other news, we’ve published the third RC of our upcoming release, Nextcloud Hub 3. Things are really coming together already, so if you want to make sure the upcoming release works well for your system – now’s the time to test and report problems you experience! As always, we’re very keen to hear about upgrade issues as there are always more ways Nextcloud is used in than what we realistically can test!

You can get involved on our forums.

To learn more about our release, check out the big release announcement we did last weekend!

Ready to move to Nextcloud Hub 24?

Nextcloud Hub 24 received its 6th maintenance release and we highly recommend that you upgrade to benefit from the latest features. Check out the release announcement here.

🙋 User migration

🔒 Smart file locking

🚀 4x lower db load

❤️ Reactions & media tab in Talk

🤩 Reply to calls & messages in Desktop client

💌 Undo send & schedule emails

End of public support for Nextcloud 22

Nextcloud Hub 22 is no longer maintained. We will continue to release security and bug fix updates only for Nextcloud Enterprise 22. If you are a home user, move to Hub 23 or 24 as soon as possible. If you use Nextcloud in a commercial setting, check out our Nextcloud Enterprise as that is likely more suited for you. As always we strongly recommend you update to ensure you have a secure and reliable content collaboration platform that respects your digital sovereignty!
This is, of course, also true for apps: Keeping them updated has security benefits, besides the new features and other bug fixes.

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.

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.