Skip to content

[Bug]: Nextcloud 35 failing database checks #1185

Closed

Description

@neponn

⚠️ This issue respects the following points: ⚠️

  • This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
  • This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
  • I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
  • I agree to follow Nextcloud's Code of Conduct.
  • I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.

Bug description

Since upgrading to Nextcloud 35.0.1 (from 34.0.4), I'm getting a bunch of database checks failing. A few have to do with config of my MySQL database, which are actionable. However, there are a bunch related to performance, which point at database design, that I can't see how to action. If anything, the messages imply the Nextcloud table schema is not optimal.

The bug here is that the messages don't seem to be actionable. It would be strange for the correct interpretation of these messages to be that the Nextcloud table schema needs to be improved.

Steps to reproduce

  1. Upgrade Nextcloud to 35.0.1
  2. Observe admin overview page
  3. Follow link to "show the findings" on database checks failing

Note: I am using the Linuxserver Nextcloud docker image.

Expected behavior

Actionable messages that will improve performance are welcome. Messages that can't be actioned are baffling for the end user.

Nextcloud Server version

35

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.4

Web server

Nginx

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

No response

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

{
    "system": {
        "memcache.local": "\\OC\\Memcache\\APCu",
        "filelocking.enabled": true,
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 6379,
            "timeout": 0
        },
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_proxies": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "cloud.eponn.net"
        ],
        "overwrite.cli.url": "**REMOVED SENSITIVE VALUE***",
        "overwritehost": "**REMOVED SENSITIVE VALUE***",
        "overwriteprotocol": "https",
        "dbtype": "mysql",
        "version": "35.0.1.1",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "mysql.utf8mb4": true,
        "installed": true,
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "smtp",
        "mail_smtpauthtype": "LOGIN",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "maintenance": false,
        "logtimezone": "Australia\/Hobart",
        "loglevel": 0,
        "trashbin_retention_obligation": "30,90",
        "theme": "",
        "default_phone_region": "AU",
        "default_language": "en",
        "default_locale": "en_AU",
        "default_timezone": "Australia\/Hobart",
        "defaultapp": "files",
        "upgrade.disable-web": true,
        "maintenance_window_start": 1
    }
}

List of activated Apps

Enabled:
  - activity: 8.0.0
  - admin_audit: 2.0.0-dev.0
  - appstore: 2.0.0-dev.0
  - cloud_federation_api: 2.0.0-dev.0
  - comments: 2.0.0-dev.0
  - contactsinteraction: 2.0.0-dev.0
  - dashboard: 8.0.0-dev.0
  - dav: 2.0.0-dev.1
  - federatedfilesharing: 2.0.0-dev.1
  - federation: 2.0.0-dev.0
  - files: 3.0.0-dev.0
  - files_downloadlimit: 5.3.0
  - files_lock: 35.0.0
  - files_pdfviewer: 8.0.0
  - files_reminders: 2.0.0-dev.0
  - files_sharing: 2.0.0-dev.1
  - files_trashbin: 2.0.0-dev.0
  - files_versions: 2.0.0-dev.0
  - firstrunwizard: 8.0.0
  - logreader: 8.0.0
  - lookup_server_connector: 2.0.0-dev.0
  - nextcloud_announcements: 7.0.0
  - notifications: 8.0.0
  - notify_push: 1.4.1
  - oauth2: 2.0.0-dev.0
  - office: 1.1.0
  - password_policy: 7.0.0
  - photos: 8.0.0
  - privacy: 7.0.0
  - profile: 2.0.0-dev.0
  - provisioning_api: 2.0.0-dev.0
  - recommendations: 8.0.0
  - related_resources: 6.0.0
  - serverinfo: 7.0.0
  - settings: 2.0.0-dev.0
  - sharebymail: 2.0.0-dev.0
  - sharing: 1.0.4
  - support: 7.0.0
  - survey_client: 7.0.0
  - suspicious_login: 13.0.0
  - systemtags: 2.0.0-dev.0
  - text: 9.0.0
  - theming: 3.0.0-dev.0
  - twofactor_backupcodes: 2.0.0-dev.0
  - twofactor_nextcloud_notification: 9.0.0
  - twofactor_totp: 17.1.0
  - user_status: 2.0.0-dev.0
  - viewer: 8.0.0
  - weather_status: 2.0.0-dev.0
  - webhook_listeners: 2.0.0-dev.0
  - workflowengine: 3.0.0-dev.0
Disabled:
  - app_api: 35.0.0 (installed 32.0.0)
  - bruteforcesettings: 8.0.0 (installed 2.2.0)
  - circles: 35.0.0 (installed 30.0.0)
  - encryption: 3.0.0-dev.0
  - files_external: 2.0.0-dev.0
  - files_rightclick: 1.6.0 (installed 1.6.0)
  - testing: 1.23.0
  - updatenotification: 2.0.0-dev.0 (installed 1.17.0)
  - user_ldap: 2.0.0-dev.0

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

Additional info

These are the messages that don't seem to be actionable.

Image

Activity

  1. added theissue type on Oct 6, 2026
  2. kesselb commented on Oct 6, 2026

    @kesselb
    Collaborator

    Thanks for the report 👍

    Closing as duplicate of #1155 and #1166.

    Here's what will actually change for 35.0.2: #1167. I assume this will address also the checks you are seeing.

  3. neponn commented on Oct 6, 2026

    @neponn
    Author

    Thanks and apologies for the duplicate issue. Looking forward to the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions