[Bug]: cron.php stops with exception: `InvalidArgumentException: fediverse`
Open
Nobody has claimed this yet.
0. Needs triage
31-feedback
bug
feature: profile
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
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
Executing cron.php yields:
$ php cron.php
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
InvalidArgumentException: fediverse in /www/htdocs/w014bcda/file.serrahneins.de/lib/private/Accounts/AccountManager.php:725
Stack trace:
#0 /www/htdocs/w014bcda/file.serrahneins.de/lib/private/Accounts/AccountManager.php(795): OC\Accounts\AccountManager->sanitizePropertyFediverse(Object(OC\Accounts\AccountProperty))
#1 /www/htdocs/w014bcda/file.serrahneins.de/apps/settings/lib/BackgroundJobs/VerifyUserData.php(237): OC\Accounts\AccountManager->updateAccount(Object(OC\Accounts\Account))
#2 /www/htdocs/w014bcda/file.serrahneins.de/apps/settings/lib/BackgroundJobs/VerifyUserData.php(54): OCA\Settings\BackgroundJobs\VerifyUserData->resetVerificationState()
#3 /www/htdocs/w014bcda/file.serrahneins.de/lib/public/BackgroundJob/Job.php(46): OCA\Settings\BackgroundJobs\VerifyUserData->start(Object(OC\BackgroundJob\JobList))
#4 /www/htdocs/w014bcda/file.serrahneins.de/cron.php(170): OCP\BackgroundJob\Job->execute(Object(OC\BackgroundJob\JobList))
#5 {main}
Steps to reproduce
1.login with bash
2.execute php cron.php
Expected behavior
should not stop with error
Nextcloud Server version
31
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 31 to 32)
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": [
"file.serrahneins.de",
"www.file.serrahneins.de"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "31.0.5.1",
"overwrite.cli.url": "http:\/\/file.serrahneins.de",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"tempdirectory": "\/www\/htdocs\/w014bcda\/file.serrahneins.de\/data\/tmp",
"mail_smtpmode": "sendmail",
"mail_sendmailmode": "pipe",
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"default_phone_region": "DE",
"maintenance_window_start": 100,
"maintenance": false,
"updater.secret": "***REMOVED SENSITIVE VALUE***",
"theme": "",
"loglevel": 2,
"forbidden_filename_basenames": [
"con",
"prn",
"aux",
"nul",
"com0",
"com1",
"com2",
"com3",
"com4",
"com5",
"com6",
"com7",
"com8",
"com9",
"com\u00b9",
"com\u00b2",
"com\u00b3",
"lpt0",
"lpt1",
"lpt2",
"lpt3",
"lpt4",
"lpt5",
"lpt6",
"lpt7",
"lpt8",
"lpt9",
"lpt\u00b9",
"lpt\u00b2",
"lpt\u00b3"
],
"forbidden_filename_characters": [
"<",
">",
":",
"\"",
"|",
"?",
"*",
"\\",
"\/"
],
"forbidden_filename_extensions": [
" ",
".",
".filepart",
".part"
]
}
}
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
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 lib/private/Accounts/AccountManager.php around line 725, then trace the update flow from apps/settings/lib/BackgroundJobs/VerifyUserData.php. Reproduce the failure by running php cron.php and determine why the fediverse account property reaches sanitization as invalid. Done means cron.php completes without this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100