Skip to content

docs(admin): clarify web server user and file ownership requirements#14911

Merged
skjnldsv merged 1 commit into
masterfrom
fix/clarify-owner-group-requirements
May 19, 2026
Merged

docs(admin): clarify web server user and file ownership requirements#14911
skjnldsv merged 1 commit into
masterfrom
fix/clarify-owner-group-requirements

Conversation

@skjnldsv
Copy link
Copy Markdown
Member

☑️ Resolves

Summary

The installation docs showed chown -R www-data:www-data /var/www/nextcloud/
without explaining that www-data is the Debian/Ubuntu web server user, or that
strict ownership is not actually required — only read/write access by the web server
process user is.

This causes confusion for users on:

  • RHEL/CentOS/Fedora (web server user is apache, not www-data)
  • Docker setups with bind-mounts whose ownership cannot be changed
  • Shared hosting environments
  • Environments like VirtualBox where data lives on a vboxsf-mounted volume

Added a note clarifying:

  1. www-data is Debian/Ubuntu specific; RHEL/CentOS uses apache
  2. The real requirement is read/write access, not literal www-data:www-data ownership
  3. In constrained environments, adding the web server user to the owning group is sufficient

🖼️ Screenshots

No visual layout change — text-only addition to an existing section.

✅ Checklist

  • I have built the documentation locally and reviewed the output
  • Screenshots are included for visual changes (N/A — text only)
  • I have not moved or renamed pages (or added a redirect if I did)
  • I have run codespell or similar and addressed any spelling issues

The chown -R www-data:www-data command implied that ownership must be
www-data:www-data specifically. The actual requirement is that the web
server process user has read/write access to the Nextcloud directories.

Added a note clarifying:
- www-data is the Debian/Ubuntu default; RHEL/CentOS/Fedora uses apache
- Ownership is not strictly required — group membership + group-writable
  permissions are sufficient in environments where chown is not possible
  (shared hosting, Docker bind-mounts, VirtualBox shared folders, etc.)

Fixes #1239

Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
@skjnldsv
Copy link
Copy Markdown
Member Author

/backport to stable34

@skjnldsv skjnldsv disabled auto-merge May 19, 2026 13:10
@skjnldsv skjnldsv merged commit e8705ef into master May 19, 2026
31 of 33 checks passed
@skjnldsv
Copy link
Copy Markdown
Member Author

/backport to stable33

@skjnldsv skjnldsv deleted the fix/clarify-owner-group-requirements branch May 19, 2026 13:10
@skjnldsv
Copy link
Copy Markdown
Member Author

/backport to stable32

@backportbot
Copy link
Copy Markdown

backportbot Bot commented May 19, 2026

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/14911/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 207d59a5

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/14911/stable33

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/14911/stable33."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@github-actions
Copy link
Copy Markdown
Contributor

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

Last updated: Tue, 19 May 2026 14:05:02 GMT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify owner/group requirements for data folder

2 participants