# Frequent Nextcloud 31 (Hub 10) update issues **URL:** \ **Category:** ℹ️ Support\ **Tags:** talk-hpb, beta, update\_problems, nc31, setup\_warning\ **Created:** [January 14, 2025, 8:50pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983 "2025-01-14T20:50:25Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [January 14, 2025, 8:50pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/1 "2025-01-14T20:50:25Z")
Hi community, the next release of [Nextcloud 31 (Hub 10)](https://help.nextcloud.com/tag/nc31) is finally released! - [Nextcloud Hub 10 – your unified, modular digital workspace](https://help.nextcloud.com/t/nextcloud-hub-10-your-unified-modular-digital-workspace/218337) 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. - look at the topics with #nc31 and #setup_warning tags and both together [Topics tagged nc31 & setup\_warning](https://help.nextcloud.com/tags/intersection/nc31/setup_warning/) - [Apps with missing support for NC 31](https://help.nextcloud.com/t/app-support-for-nc-31/217313) ..sometimes issues repeat/reoccur especially if you jump over the previous release - please look at - [Frequent Nextcloud 30 (Hub 9) update issues](https://help.nextcloud.com/t/frequent-nextcloud-30-hub-9-update-issues/201528) and [Topics tagged setup\_warning & nc30](https://help.nextcloud.com/tags/intersection/setup_warning/nc30/) - [Frequent Nextcloud 29 (Hub 8) update issues](https://help.nextcloud.com/t/frequent-nextcloud-29-hub-8-update-issues/189897) and [Topics tagged setup\_warning & nc29](https://help.nextcloud.com/tags/intersection/setup_warning/nc29/) as well. # Github references - [nc31-feedback label](https://github.com/nextcloud/server/labels/31-feedback) - [https://github.com/nextcloud/server/issues/23369](https://github.com/nextcloud/server/issues/23369) # Important changes see [https://docs.nextcloud.com/server/latest/admin\_manual/release\_notes/upgrade\_to\_31.html](https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_31.html) 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_](https://www.php.net/supported-versions) 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 🤝 ```auto # 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:** > [@Upgrade to Nextcloud Hub 10 (31.0.0) Incorrect row format found in your database](https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366): > > I have the Linuxserver Nextcloud and MariaDB docker containers and today Nextcloud updated to Nextcloud Hub 10 (31.0.0). I am getting error messages: 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: (followed by a long list of files like oc\_activity, oc\_accounts\_data, oc\_activity\_mq, oc\_addressbookchanges and so on.) What do I need to do? should only happen in setups that were initially started before NC 24, background: [https://github.com/nextcloud/server/issues/34497](https://github.com/nextcloud/server/issues/34497) - [Falsches Zeilenformat](https://help.nextcloud.com/t/falsches-zeilenformat/214500) - [Nach Update auf 31.0 Falsches Zeilenformat in deiner Datenbank gefunden - #3 by bb77](https://help.nextcloud.com/t/nach-update-auf-31-0-falsches-zeilenformat-in-deiner-datenbank-gefunden/218364/3) - [Initial Test of Nextcloud 31.0.0 by stondino00 · Pull Request #3068 · nextcloud-snap/nextcloud-snap · GitHub](https://github.com/nextcloud-snap/nextcloud-snap/pull/3068#issuecomment-2688038952) * * * ## Talk high performance backend (HPB) check > [@Update auf 31.0.0 beta 2](https://help.nextcloud.com/t/update-auf-31-0-0-beta-2/214732/3): > > Ein nicht vorhandenes HPB wird als Fehler gewertet. ```auto 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. ``` - [https://github.com/nextcloud/spreed/pull/14147](https://github.com/nextcloud/spreed/pull/14147) ### Disable “No High-performance backend configured” warning: ![grafik](https://github.com/user-attachments/assets/110dbaee-a276-4175-8986-7a78828f91a6) disable setup warning in **Administration settings** → **Talk** → _disable warning_ ![grafik](https://github.com/user-attachments/assets/f6a7ef55-4223-4a37-8f24-7b1084ac0dac) * * * ## 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 [https://help.nextcloud.com/tags/intersection/setup\_warning/apcu](https://help.nextcloud.com/tags/intersection/setup_warning/apcu) * * * ### extra file REUSE.toml > [@Strange Update error REUSE.toml](https://help.nextcloud.com/t/strange-update-error-reuse-toml/232361): > > Bare Metal Nextcloud on Debian Server 12 Nextcloud Version 30.0.15 want update to Version 31.0.9 But it stops at: Check for expected files Unknown files detected within the installation folder. This can be fixed by manually removing (or moving) these files. The following extra files have been found: REUSE.toml so i did delete all backups in /var/nextcloud\_data/updater-oc8s2ttpht2t/ But still the same. So i did a root@DebianServerVM2:~# find / -type f -name REUSE.toml /var/www/nextclo… ---
**Author:** ![iamhives](https://help.nextcloud.com/letter_avatar/iamhives/32/5_5575768a8748004e209b776fc1b2916d.png) [@iamhives](https://help.nextcloud.com/u/iamhives)\ **Post date:** [February 21, 2025, 10:54pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/2 "2025-02-21T22:54:55Z")
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 ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [February 22, 2025, 12:59pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/3 "2025-02-22T12:59:42Z")
> [@iamhives](#): > > 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. ---
**Author:** ![iamhives](https://help.nextcloud.com/letter_avatar/iamhives/32/5_5575768a8748004e209b776fc1b2916d.png) [@iamhives](https://help.nextcloud.com/u/iamhives)\ **Post date:** [February 22, 2025, 1:41pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/4 "2025-02-22T13:41:45Z")
How long until php 8.4 becomes the preferred version? ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [February 22, 2025, 2:58pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/5 "2025-02-22T14:58:44Z")
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](https://github.com/nextcloud/server/wiki/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. 😉 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. ---
**Author:** ![nursoda](https://help.nextcloud.com/user_avatar/help.nextcloud.com/nursoda/32/1044_2.png) [@nursoda](https://help.nextcloud.com/u/nursoda)\ **Post date:** [February 22, 2025, 6:16pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/6 "2025-02-22T18:16:55Z")
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. ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [February 23, 2025, 8:07pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/7 "2025-02-23T20:07:43Z")
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](https://docs.nextcloud.com/server/31/admin_manual/installation/system_requirements.html) > [@bb77](#): > > upgrade to the latest version as soon as possible > [@nursoda](#): > > apps that might not be ready for PHP 8.4 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. ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [February 24, 2025, 9:27am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/8 "2025-02-24T09:27:31Z")
> [@tflidd](#): > > 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. Good point, I forgot to mention app compatibility, which can be an issue, especially with third party apps. 🙂 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 😉 ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [February 26, 2025, 7:19pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/9 "2025-02-26T19:19:50Z")
---
**Author:** ![Ben](https://help.nextcloud.com/letter_avatar/ben/32/5_5575768a8748004e209b776fc1b2916d.png) [@Ben](https://help.nextcloud.com/u/Ben)\ **Post date:** [February 27, 2025, 8:17am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/10 "2025-02-27T08:17:12Z")
looks like this is a frequent issue: > [@Upgrade to Nextcloud Hub 10 (31.0.0) Incorrect row format found in your database](https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366): > > I have the Linuxserver Nextcloud and MariaDB docker containers and today Nextcloud updated to Nextcloud Hub 10 (31.0.0). I am getting error messages: 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: (followed by a long list of files like oc\_activity, oc\_accounts\_data, oc\_activity\_mq, oc\_addressbookchanges and so on.) What do I need to do? A user should not be forced to touch the database or even its schema. ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [February 27, 2025, 8:50am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/11 "2025-02-27T08:50:59Z")
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 😉 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. ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [February 27, 2025, 8:52am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/12 "2025-02-27T08:52:33Z")
I just added this info the wiki post a few seconds before you wrote your post. ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [February 27, 2025, 10:43am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/13 "2025-02-27T10:43:34Z")
A post was split to a new topic: [Preview error in NC 31](https://help.nextcloud.com/t/preview-error-in-nc-31/218562) ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [February 28, 2025, 9:14am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/14 "2025-02-28T09:14:48Z")
A post was split to a new topic: [NC31 FIDO2/webauthn stopped working](https://help.nextcloud.com/t/nc31-fido2-webauthn-stopped-working/218664) ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [February 28, 2025, 9:30am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/15 "2025-02-28T09:30:01Z")
A post was split to a new topic: [CSFR issues in NC 30](https://help.nextcloud.com/t/csfr-issues-in-nc-30/218675) ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [February 28, 2025, 3:28pm UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/16 "2025-02-28T15:28:11Z")
A post was merged into an existing topic: [Update nextcloud to 31.0.0 now elasticsearch not working](https://help.nextcloud.com/t/update-nextcloud-to-31-0-0-now-elasticsearch-not-working/218379/9) ---
**Author:** ![3857640045](https://help.nextcloud.com/letter_avatar/3857640045/32/5_5575768a8748004e209b776fc1b2916d.png) [@3857640045](https://help.nextcloud.com/u/3857640045)\ **Post date:** [March 25, 2025, 8:29am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/17 "2025-03-25T08:29:48Z")
I encountered this error in the log when downloading multiple files： “Cannot modify header information - headers already sent by (output started at /var/www/html/3rdparty/deepdiver/zipstreamer/src/ZipStreamer.php:325) at /var/www/html/3rdparty/sabre/http/lib/Sapi.php#68” ![image](https://help.nextcloud.com/uploads/default/original/3X/8/f/8f98ed2bdb1247c007c27246adcb45bbe0a8e643.png) ---
**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\ **Post date:** [March 25, 2025, 8:43am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/18 "2025-03-25T08:43:57Z")
> [@bb77](#): > > it would certainly be nice if Nextcloud could take care of that automatically snap team has added this to the `nextcloud-fixer` for automatic execution, no actions required for snap upon release… testing in progress ---
**Author:** ![ThorStone](https://help.nextcloud.com/letter_avatar/thorstone/32/5_5575768a8748004e209b776fc1b2916d.png) [@ThorStone](https://help.nextcloud.com/u/ThorStone)\ **Post date:** [April 19, 2025, 8:06am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/19 "2025-04-19T08:06:45Z")
There seems to be a problem with that script. On my instance it’s trying to run that over and over but then crashes every time. ```auto root 562980 562907 0 22:53 ? 00:00:00 /bin/sh /snap/nextcloud/47365/fixes/existing-install/maintenance/2_fix-row-format.sh root 562985 562980 0 22:53 ? 00:00:00 /bin/sh /snap/nextcloud/47365/fixes/existing-install/maintenance/2_fix-row-format.sh root 563511 562985 0 22:53 ? 00:00:00 /bin/sh -e /snap/nextcloud/47365/bin/run-mysql nextcloud -Bse ALTER TABLE oc_filecache ROW_FORMAT = DYNAMIC; root 563526 563511 0 22:53 ? 00:00:00 mysql --defaults-file=/var/snap/nextcloud/47365/mysql/root.ini nextcloud -Bse ALTER TABLE oc_filecache ROW_FORMAT = DYNAMIC; ``` How can I troubleshoot this? I cannot find the log for the `2_fix-row-format.sh` script, which seems to be started by the `nextcloud-fixer`. ---
**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\ **Post date:** [April 19, 2025, 8:21am UTC](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983/20 "2025-04-19T08:21:11Z")
@ThorStone thanks for mentioning your issue here too. There’s really no need for redundancy though! > > > \### SOLVED, see my last comment. > > > \#### Describe the bug > > After the recent updat…e (2 days ago), my Nextcloud instance is starting the nextcloud-fixer over and over again. > > It seems to get stuck on these processes: > > \`\`\` > root 562980 562907 0 22:53 ? 00:00:00 /bin/sh /snap/nextcloud/47365/fixes/existing-install/maintenance/2\_fix-row-format.sh > root 562985 562980 0 22:53 ? 00:00:00 /bin/sh /snap/nextcloud/47365/fixes/existing-install/maintenance/2\_fix-row-format.sh > root 563511 562985 0 22:53 ? 00:00:00 /bin/sh -e /snap/nextcloud/47365/bin/run-mysql nextcloud -Bse ALTER TABLE oc\_filecache ROW\_FORMAT = DYNAMIC; > root 563526 563511 0 22:53 ? 00:00:00 mysql --defaults-file=/var/snap/nextcloud/47365/mysql/root.ini nextcloud -Bse ALTER TABLE oc\_filecache ROW\_FORMAT = DYNAMIC; > \`\`\` > > \#### To Reproduce > > Automated snap update. > > \#### Expected behavior > > \`nextcloud-fixer\` finishes and update is complete > > \#### OS/snapd/snap version > What OS and version are you running? > > \`\`\` > Ubuntu Server 22.04.5 LTS (GNU/Linux 5.15.0-1075-raspi aarch64) > \`\`\` > > Please also include the output of the > following commands: > > $ snap list nextcloud > > \`\`\` > Name Version Rev Tracking Publisher Notes > nextcloud 31.0.2snap2 47365 latest/stable nextcloud✓ - > \`\`\` > > and: > > $ snap version > > \`\`\` > snap 2.67.1+22.04 > snapd 2.67.1+22.04 > series 16 > ubuntu 22.04 > kernel 5.15.0-1075-raspi > \`\`\` > > \#### Logs > Please paste in the output from > \[this script\](https://github.com/nextcloud/nextcloud-snap/wiki/Issue-Debugging-Scripts) > to assist in debugging (note that it's pre-formatted). > > Too long to paste here. Attached: > > \[nextcloud\_debug.log\](https://github.com/user-attachments/files/19816947/nextcloud\_debug.log) [Next page](https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983.md?page=2)