Frequent Nextcloud 31 (Hub 10) update issues

Hi community, the next release of Nextcloud 31 (Hub 10) is finally released!

it’s time to bundle frequent issues into a WIKI post (everybody is welcome to add content) to help users to find solutions for frequent issues after update to NC30. This should avoid flooding forum with similar topics and help others identify and solve known issues.

…sometimes issues repeat/reoccur especially if you jump over the previous release - please look at

as well.

Github references

Important changes

see Upgrade to Nextcloud 31 — Nextcloud latest Administration Manual latest documentation for details

supported PHP versions

  • PHP 8.1 is now deprecated but still supported. php81
  • PHP 8.4 is now supported, but 8.3 is recommended. php84

Development for PHP 8.1 stopped already but it will receive security patches until 31 Dec 2025 if you are still using such end-of-life PHP it’s time to act!


Issues


New database check incorrect row format:

setup checks shows folling warnings setup_warning :handshake:

# english
Incorrect row format found in your database. ROW_FORMAT=Dynamic offers the best database performances for Nextcloud. Please update row format on the following list:
# Deutsch
Falsches Zeilenformat in deiner Datenbank gefunden. ROW_FORMAT=Dynamic bietet die beste Datenbankleistung für Nextcloud. Bitte aktualisiere das Zeilenformat in der folgenden Liste:

Issue with small script to fix it:

should only happen in setups that were initially started before NC 24, background: Add setup warning in case row_format=compressed is still used · Issue #34497 · nextcloud/server · GitHub


Talk high performance backend (HPB) check

No High-performance backend configured - Running Nextcloud Talk without the High-performance backend only scales for very small calls (max. 2-3 participants). Please set up the High-performance backend to ensure calls with multiple participants work seamlessly. 

Disable “No High-performance backend configured” warning:

grafik

disable setup warning in Administration settingsTalkdisable warning

grafik


new APCu setup check

We have a new setup warning to check if the memory reserved for APCu is high enough. If you see this warning, you should increase the memory reserved for APCu. You can do this by increasing the value of the apc.shm_size directive in your php.ini file. It is generally advised to review this value and increase it if necessary depending on your instance size.

setup_warning apcu Topics tagged setup_warning & apcu

3 Likes

Not to be pedantic but what does ‘php 8.4 supported, 8.3 recommended’ mean? If I update to php 8.4 should I expect more problems than remaining on 8.3? IMO if php 8.4 is supported it should be as reliable and as thoroughly tested as 8.3

This is simply not possible because PHP 8.4 has been out for less time than 8.3, and preventive regression testing can never catch all the bugs and issues that may occur in real-world usage scenarios.

But yes, if they say that PHP 8.4 is supported, you can generally assume that it will work fine for most common usage scenarios. However, the risk of running into less obvious bugs and/or issues that only occur under certain specific circumstances is still higher because it hasn’t been tested for as long and in fewer real-world environments.

How long until php 8.4 becomes the preferred version?

I’m don’t know, but the following table might help you estimate when it might become the recommended version: Nextcloud Releases and PHP Versions.

However, it may be worth reconsidering whether you really need to upgrade to the latest version as soon as possible.

If it’s just the urge to always run the latest version of everything, I would suggest resisting that temptation and sticking with the officially recommended versions. :wink:

If there are specific reasons for upgrading, I recommend testing it on a separate test instance before upgrading your production system, which by the way is always a good practice to minimize risk, regardless of whether the version you’re upgrading to is “only” supported or recommended by the developers.

Mind that there are apps that might not be ready for PHP 8.4. Although any app that is released for NC31 should support PHP 8.4, its manifest may state differently.

1 Like

I wouldn’t give too much thought about this, they even recommend Ubuntu 22.04 over 24.04: System requirements — Nextcloud latest Administration Manual latest documentation

Those two points are more important. If the new version is released, you have tested the new version with all the apps in your environment, it does not really make a difference if you are on php 8.3 or 8.4.

If there are no huge problems, they’ll probably recommend it for the next version since php itself moves quite fast and Nextcloud tries to keep up with officially supported versions.

1 Like

Good point, I forgot to mention app compatibility, which can be an issue, especially with third party apps. :slight_smile:

Also, if you do run into issues, it’s relatively easy to revert back to the previous version of PHP, but this will of course cause downtime.

On the other hand, if everything is working fine as it is, there is really no need to upgrade to the latest PHP version as soon as possible, especially if the version currently installed is still the one recommended by the Nextcloud developers :wink:

looks like this is a frequent issue:

A user should not be forced to touch the database or even its schema.

1 Like

Users don’t have to do this, the server admin has to, and that’s exactly what you are if you’re running your own server :wink:

But yes, it would certainly be nice if Nextcloud could take care of that automatically. On the other hand, there may be good reasons why it doesn’t do that, I can’t really judge as I’m not a developer.

1 Like

I just added this info the wiki post a few seconds before you wrote your post.

5 Likes

A post was split to a new topic: Preview error in NC 31

A post was split to a new topic: NC31 FIDO2/webauthn stopped working

A post was split to a new topic: CSFR issues in NC 30

A post was merged into an existing topic: Update nextcloud to 31.0.0 now elasticsearch not working