nextcloud / nextcloud/groupfolders
[Bug]: Auto-expiry of shared folder inside group folder leads to Files app not working anymore for user
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 343
- Forks
- 106
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 34
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 (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- Nextcloud Server is running on 64bit capable CPU, PHP and OS.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
We have a group folder ("DirA") to which User A has access using the group folder permissions. On a subdirectory (let's call it "DirA/B"), User A doesn't have access as the group folder permissions on that subdirectory don't allow access. However, we then give access to the subdirectory of this non-shared folder via the nextcloud sharing option for internal users, so to say to "DirA/B/X".
The bug is that when the nextcloud sharing expires on the directory X, the whole files app stops working and instead only returns an "internal server error" all the time, until someone reshared directory X with the User. If the share is manually removed, the bug doesn't occur. Only on auto-expiration based on the date, there's this issue.
Steps to reproduce
- Setup a group folder, give advanced permissions to a User A
- Set up a subdirectory of the group folder, to which using the advanced permissions, User A has no rights
- Create another subdirectory in this directory that is hidden to User A and use the sharing panel to enter the User A name and share
- Set an expiration date
- At expiry, the user will have problems using the files app until the folder is shared in the sharing panel again.
Expected behavior
Auto-expiry of shares should not lead to Files app not working anymore
Installation method
Community Docker image
Operating system
Debian/Ubuntu
PHP engine version
No response
Web server
No response
Database engine version
No response
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": {
"htaccess.RewriteBase": "\/",
"memcache.local": "\\OC\\Memcache\\APCu",
"apps_paths": [
{
"path": "\/var\/www\/html\/apps",
"url": "\/apps",
"writable": false
},
{
"path": "\/var\/www\/html\/custom_apps",
"url": "\/custom_apps",
"writable": true
}
],
"memcache.distributed": "\\OC\\Memcache\\Redis",
"memcache.locking": "\\OC\\Memcache\\Redis",
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"password": "***REMOVED SENSITIVE VALUE***",
"port": 6379
},
"trusted_proxies": "***REMOVED SENSITIVE VALUE***",
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"localhost",
"nowhereland.phelas.com",
"nextcloud-app"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "24.0.5.1",
"overwrite.cli.url": "https:\/\/nowhereland.phelas.com",
"overwriteprotocol": "https",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"data-fingerprint": "3737cb51804a03a7f06c823eb9ba0d10",
"maintenance": false,
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_smtpmode": "smtp",
"mail_sendmailmode": "smtp",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_smtpauth": 1,
"mail_smtpauthtype": "LOGIN",
"mail_smtphost": "***REMOVED SENSITIVE VALUE***",
"mail_smtpport": "465",
"mail_smtpname": "***REMOVED SENSITIVE VALUE***",
"mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
"mail_smtpsecure": "ssl",
"session_lifetime": 14400,
"theme": "",
"loglevel": "1",
"default_phone_region": "DE",
"twofactor_enforced": "true",
"twofactor_enforced_groups": [
"LiquairStore"
],
"twofactor_enforced_excluded_groups": [],
"enable_previews": false,
"allow_local_remote_servers": "true",
"log_type": "file",
"forwarded_for_headers": [
"HTTP_X_FORWARDED",
"HTTP_FORWARDED_FOR"
]
}
}
List of activated Apps
Enabled:
- accessibility: 1.10.0
- activity: 2.16.0
- admin_audit: 1.14.0
- appointments: 1.12.8
- apporder: 0.15.0
- bruteforcesettings: 2.4.0
- calendar: 3.5.0
- circles: 24.0.1
- cloud_federation_api: 1.7.0
- comments: 1.14.0
- contacts: 4.2.1
- contactsinteraction: 1.5.0
- dashboard: 7.4.0
- dav: 1.22.0
- external: 4.0.0
- federatedfilesharing: 1.14.0
- federation: 1.14.0
- files: 1.19.0
- files_accesscontrol: 1.14.1
- files_automatedtagging: 1.14.0
- files_downloadactivity: 1.13.0
- files_external: 1.16.1
- files_pdfviewer: 2.5.0
- files_rightclick: 1.3.0
- files_sharing: 1.16.2
- files_trashbin: 1.14.0
- files_versions: 1.17.0
- files_videoplayer: 1.13.0
- firstrunwizard: 2.13.0
- forms: 2.5.1
- groupfolders: 12.0.1
- logreader: 2.9.0
- lookup_server_connector: 1.12.0
- mail: 1.13.8
- nextcloud_announcements: 1.13.0
- notes: 4.5.1
- notifications: 2.12.1
- oauth2: 1.12.0
- onlyoffice: 7.5.4
- password_policy: 1.14.0
- polls: 3.8.1
- privacy: 1.8.0
- provisioning_api: 1.14.0
- ransomware_protection: 1.13.0
- recommendations: 1.3.0
- serverinfo: 1.14.0
- settings: 1.6.0
- sharebymail: 1.14.0
- survey_client: 1.12.0
- systemtags: 1.14.0
- tasks: 0.14.4
- text: 3.5.1
- theming: 1.15.0
- twofactor_backupcodes: 1.13.0
- twofactor_nextcloud_notification: 3.4.0
- twofactor_totp: 6.4.0
- twofactor_webauthn: 0.3.2
- updatenotification: 1.14.0
- viewer: 1.8.0
- weather_status: 1.4.0
- workflowengine: 2.6.0
Disabled:
- encryption
- integration_whiteboard: 0.0.14
- photos: 1.1.0
- support: 1.4.0
- twofactor_admin: 3.2.0
- unsplash: 1.2.5
- user_ldap
- user_status: 1.0.1
Nextcloud Signing status
No errors have been found.
Nextcloud Logs
No response
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 by reproducing the group-folder permission setup and the internal share's scheduled expiry described in the issue, then compare it with manual share removal. Inspect the server behavior when the expiry occurs, since no logs or source entry points are provided. Done means the Files app continues working after automatic expiry while the share is removed as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100