Nextcloud · Help

Nextcloud updater stops at Write permissions?

An update stops at its write-permission check? Identify the exact path, effective PHP user and mount permissions before changing ownership.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

Investigate Check for write permissions from the perspective of the process actually running the Nextcloud updater. Plausible file modes are insufficient if process identity, ACLs, parent directories or mount state restrict access. First identify the full path in updater.log and the intended PHP account, then inspect the complete access path without modifying it. For packaged installations, establish the supported update mechanism first.

Source basis: Q1 · Q2

Applies to
The original case concerns Nextcloud 32.0.6 on a NAS with a manual installation. Built-in updater steps must not be assumed appropriate for AIO, Snap or managed packages.
How to verify the result
The previously failing write check and the complete upgrade finish successfully; reported version, login and a small file operation match the intended target state.
Your first check

Which effective process user fails on which complete path?

The Nextcloud updater stops at Check for write permissions. It lists files whose permissions initially look reasonable, and changing a few numeric modes has not helped. Investigate access from the perspective of the process that actually runs the update.

Identify the blocked phase

A report concerns Nextcloud 32.0.6 on a NAS with a manually managed installation. Its permission check failed despite mode changes; the initial report does not establish a confirmed cause. Q1 Official documentation separates checking and replacing application files from the subsequent database and app migration. The updater also does not replace a complete backup of user data and the database. Q2

This guide concerns the built-in updater where it is appropriate for the installation. For AIO, Snap or managed container packages, establish the supported update mechanism first.

Find the actual access failure

  1. Identify the complete path. Preserve the relevant section of updater.log. A filename alone is insufficient: is it application code, a mounted directory or an unexpected user-data path?
  2. Establish the effective identity. Which user runs web PHP? Does the command-line updater run under the intended identity? Familiar default account names are not reliable assumptions on NAS systems or inside containers.
  3. Check the entire access path. Ask the administrator to inspect ownership, groups, ACLs, parent directories and mount state without changing them. File-level write permission is insufficient if a parent directory or read-only mount prevents the operation.
  4. Explain unexpected locations. If user files appear unexpectedly inside the installation tree, inspect data-directory settings and mount mappings before recursively changing permissions. Broader write access does not correct an incorrect path arrangement.
  5. Verify a targeted correction. Document the intended owner and required permissions for the affected area. After a limited correction, use the supported updater to repeat the failed check, then observe the normal migration steps that follow.

Return to operation in a controlled way

Before continuing, retain an appropriate backup of configuration, data and database. Once the update finishes, check the reported version, login and a small file operation. Passing the write-permission check alone does not mean the entire upgrade completed.

Preserve a short before-and-after record of the affected path and permissions. This makes future package or NAS updates easier to assess and avoids repeating undocumented broad ownership changes.

Frequently asked questions

Should the web-server user own the entire NAS directory?

Not as a blanket rule. Other services may use the same storage. Derive any change from the actual ownership and permission model.

Can the command line help?

It may expose the sequence and error more clearly where supported by the installation. It does not bypass unsuitable permissions. For assistance, provide the path, process user, installation type, version and redacted log section.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0194 with KAN KAI WORKS.

Support with this issue

We investigate Nextcloud using your error message, versions and a narrowly scoped example.

Describe your case →Related service: Data & improvements

Sources

Sources checked on 5 November 2026. Individual reports do not establish general prevalence.