Final release of 35.0.1

šŸŽ Releases
1

Nextcloud 35.0.1 is out! The first maintenance release for Nextcloud 35 is now available on our download servers! :sparkles:

This update brings a few fixes and improvements, so upgrading is recommended!
As usual, if you run into any issues, please report them on the appropriate GitHub repository! :wrench:
The update will also be gradually rolled out via the updater over the next days.

Downloads

Changelog

Nextcloud 35.0.1

server

activity

app_api

circles

files_pdfviewer

logreader

notifications

text

twofactor_nextcloud_notification

viewer

2

I just upgraded from 34.0.4 to 35.0.1. Sadly as always when you open the admin overview after an nextcloud update a new error shows up. Why is this database replica error not fixed when people reporting it for over a week?

3

I have no idea, but perhaps this mostly cosmetic issue wasnā€™t their absolute top priority. :man_shrugging:

However, I have some good news: it was fixed a few hours ago: fix(database): skip the replica rule when no replication is configured by mauro2306 Ā· Pull Request #1158 Ā· nextcloud/serverinfo Ā· GitHub.

For now, Iā€™d say just ignore the message and wait for the next release. I mean, itā€™s not like itā€™s causing any actual issues, after all. :wink:

4

After the update I get the error
Some tables have many sequential scans and no index scans, suggesting a missing index.
1 table(s) have > 1M sequential scans without any index scans.

  • oc_circles_membership
    Add appropriate indexes to the affected tables (pg_stat_user_tables shows the full scan statistics).
5

Every time a new version of Nextcloud is released, whether an incremental or major update, there are all manner of database issues. Iā€™ve given up with it. This shouldnā€™t happen, particularly with a docker image. I use Nextcloud primarily for cloud storage and Card and Cal DAV syncing. Iā€™ve moved to Synology Drive and Synology Calendars and Contacts on my NAS and have none of this database shenanigans.

6

Hello!
Tested to upgrade my lab environment. I get this error, how can that be solved?

sudo -u www-data php occ upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Updating ā€¦
Exception: Database error when running migration 25000Date20260923155555 for app spreed
An index with name ā€œtta_throom_attendeeā€ was already defined on table ā€œoc_talk_thread_attendeesā€.
Update failed
Maintenance mode is kept active

7

This update brings a few fixes and improvements

And falsely claims it is Nextcloud Hub 26 Spring, which it is not:

Screenshot 2026-09-25 at 10.38.43 AM
Screenshot 2026-09-25 at 10.38.43 AM3000Ɨ1408 180 KB

Screenshot 2026-09-25 at 11.42.50 AM
Screenshot 2026-09-25 at 11.42.50 AM1920Ɨ882 102 KB

The quality control of NC is nosediving.

8

Cc @Andy @susnux

9

I had a similiar issue on a test instance.

The following helped. I reconstructed the steps from my Bash history, so I hope I didnā€™t miss anything and the order is roughly correct :wink:

1. Remove the spreed and mail apps

Iā€™m not sure whether removing mail is actually required, but there were also messages related to Mail on my instance, so I removed it as well:

occ app:remove spreed
occ app:remove mail

2. Disable maintenance mode

occ maintenance:mode --off

3. Complete the upgrade

occ upgrade

4. Remove oc_talk_thread_attendees index from the database

As root:

mariadb

Then:

USE ncdb;
ALTER TABLE oc_talk_thread_attendees DROP INDEX tta_throom_attendee;

Exit MariaDB:

exit;

5. Install the apps again

occ app:install spreed
occ app:install mail

6. Update the database

occ db:add-missing-indices
occ db:add-missing-columns
occ db:add-missing-primary-keys

See also: [Bug]: Getting a Database error after Manually Updating to Nextcloud 35.0.0 Ā· Issue #64505 Ā· nextcloud/server Ā· GitHub

Hope this helps.

10

I donā€™t think the QC is falling.

Nextcloud has always been slightly too keen to rush out new versions without enough checks.

The answer is to consider beta releases as scribble, RC releases as alpha, and release versions as beta. Only upgrade to the third version of each release, because the second is an RC.

11

Fix to ship with next release: [stable35] Bump Hub 26 Spring-> Hub 26 Summer by AndyScherzinger Ā· Pull Request #64758 Ā· nextcloud/server Ā· GitHub

12

Thx, worked! I have my lab environment up and running again! You made my day and thx for such a quick response!

13

Upgrade from 35.0.0 to 35.0.1 using docker and is working like a charm.

Thanks!

14

Yeah, you might be right. Time to get friendly with 'updatechecker' => false,