Skip to content

Federated shares with users of the same instance can deadlock PHP-FPM – create internal shares insteadΒ #66675

Description

@henrikvt

Tip

Help move this idea forward

  • Use the πŸ‘ reaction to show support for this feature.
  • Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
  • Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

Users can create federated shares with other users on the same instance. Nextcloud then talks to itself over HTTPS for every access to such a share. This can take down the whole instance.

There are two ways users end up with these "self-federated" shares:

  1. Share dialog: The owner enters user@cloud.example.org (the cloud ID of a local user) instead of just user. The current check only prevents a federated share with the same user, not with other local users.
  2. Public link: A logged-in user opens a public link from the same instance and uses "Add to your Nextcloud". This creates a federated share to the own instance.

What happened on our instance (Nextcloud 34.0.2, Apache + PHP-FPM, pm.max_children = 5 at the time):

  • Five self-federated shares existed. When users browsed folders inside them (e.g. folders with many images), each request occupied a PHP-FPM worker, which then made an HTTPS request to the same instance and waited for a free worker.
  • Once all workers were busy, they waited for each other: a deadlock. The instance stopped responding entirely for about a day, until PHP-FPM was restarted.
  • The PHP-FPM log showed server reached pm.max_children setting, Apache logged AH01075: Error dispatching request ... (polling) for every request, and nextcloud.log showed error while discovering ocm provider and files_lock: Failed to get remote lock from DAV: Gateway Timeout for paths inside the self-federated shares.

More workers make this less likely, but do not prevent it. Self-federated shares also have no benefit over internal shares: the data is on the same server either way.

Describe the solution you'd like

1. Share dialog: create an internal share instead

When the recipient of a federated share is a cloud ID that resolves to the own instance, Nextcloud should create a regular internal share with the local user instead, with the same permissions. The owner intended to share with exactly this user, so this is safe.

Detection should consider all names of the instance (trusted_domains, overwrite.cli.url) and normalize scheme, trailing slashes and subpaths. Our instance alone is reachable under three hostnames.

2. Public link: link-bound internal shares

For links, simply converting into an internal share would be wrong: the owner would lose the ability to revoke access by deleting the link. I'd suggest a model similar to OneDrive/SharePoint:

  • When a logged-in user of the same instance opens a public link, offer "Add to my files" instead of "Add to your Nextcloud".
  • This creates an internal share that is bound to the link share. Its permissions never exceed those of the link.
  • In the sharing sidebar, the owner sees which users have added the link this way.
  • When the link is deleted or expires, all shares bound to it are removed as well.

This keeps the semantics of a link ("whoever has the link has access, until I revoke it") while avoiding the round trip over HTTPS.

3. For existing installations

An occ command that lists existing self-federated shares (share_external entries whose remote points to the own instance) and optionally converts them, plus a setup check warning about them.

Describe alternatives you've considered

  • Disabling federated sharing: not possible for us, we also use federation with other servers.
  • Disabling only "Add to your Nextcloud" for public links: closes the second path, not the first.
  • Lowering davstorage.request_timeout and setting request_terminate_timeout in PHP-FPM: limits the damage, but does not fix the cause. This is what we did for now.
  • Converting the shares manually in the database: error-prone, since several tables are involved.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    0. Needs triagePending check for reproducibility or if it fits our roadmapenhancement

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions