- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
Description
⚠️  This issue respects the following points: ⚠️ 
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Summary:
Even when the system passes integrity check, config.php is valid, and occ update:check returns “Everything up to date”, the Settings > Overview page doesn’t display the “Update” or “Update channel” section.
This is confusing for administrators, as it may look like update functionality is broken or misconfigured.
Expected behavior:
Update block should still appear, showing “You are running version X.Y.Z”, and optionally the channel (even if no update is currently available).
Environment:
Nextcloud Hub 10 (31.0.6)
updater.release.channel: stable
All integrity checks pass
Steps to reproduce
- Install or update to Nextcloud Hub 10 (31.0.6)
- Ensure all integrity checks pass (via occ integrity:check-core)
- Ensure updater.release.channel is set in config.php (e.g. 'updater.release.channel' => 'stable')
- Run occ update:check— confirm output: “Everything up to date”
- Navigate to Settings > Administration > Overview
Expected: update section should be visible
Actual: update section is entirely missing
Expected behavior
The “Update” section should always be shown in the Overview, even if:
- there is no update available, or
- the current version is already the latest.
This allows the admin to verify:
- what channel is selected (e.g. stable, beta),
- when the last update check occurred,
- and that the updater is properly configured.
Removing the section gives the impression that updater functionality is broken.
Nextcloud Server version
31
Operating system
RHEL/CentOS
PHP engine version
PHP 8.3
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response