[Bug]: Web updater fails integrity check after long download
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
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
When the download takes very long, the "Verifying integrity" step fails. Maybe the session expires (?)
Steps to reproduce
- Update via Web UI
- Slow down download
- After (rough estimate) 20 minutes, the verify step will fail
- log out
- log back in
- continue update
- verify step succeeds
Expected behavior
No session expiry or instructions on how to recover (maybe s.th. like "Please log in again and continue update")
Nextcloud Server version
29
Operating system
Other
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
PostgreSQL
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?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"cloud.feldmochinger.de"
],
"trusted_proxies": "***REMOVED SENSITIVE VALUE***",
"overwritecondaddr": "^192\\.168\\.101\\.1$",
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"overwrite.cli.url": "https:\/\/cloud.feldmochinger.de",
"dbtype": "pgsql",
"version": "29.0.13.2",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbtableprefix": "oc_",
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"memcache.local": "\\OC\\Memcache\\APCu",
"memcache.locking": "\\OC\\Memcache\\APCu",
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_smtpmode": "sendmail",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_smtphost": "***REMOVED SENSITIVE VALUE***",
"mail_smtpport": "25",
"simpleSignUpLink.shown": false,
"maintenance": false,
"theme": "",
"loglevel": 2,
"default_phone_region": "DE",
"mail_sendmailmode": "pipe",
"maintenance_window_start": 2
}
}
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
updater.log:
2024-05-24T14:20:54+0000 O3JFtchEjc [info] Step 3 is in state "end".
2024-05-24T14:20:54+0000 O3JFtchEjc [info] POST request for step "4"
2024-05-24T14:20:54+0000 O3JFtchEjc [error] POST request failed with other exception
2024-05-24T14:20:54+0000 O3JFtchEjc [error] Exception: Exception
Message: Not authenticated
Code:0
Trace:
#0 {main}
File:/var/www/hosts/cloud/htdocs/updater/index.php
Line:1325
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with updater/index.php around line 1325 and the updater.log entry for the failed POST request for step 4. Reproduce the web update with a deliberately slow download and trace the authentication state through verification. Done means the integrity-check step either remains usable after a long download or clearly tells the user how to recover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100