Troubleshoot WebDAV lock and permission errors
Distinguish WebDAV 403 permission refusals, 412 precondition conflicts, and 423 content locks, then retry only after fixing the reported cause.
Last reviewed
WebDAV clients often collapse different server responses into “permission denied” or “file locked.” Preserve the HTTP status and body before changing credentials: Dosya uses 403 for authorization/policy refusals, 412 for a failed state precondition, 423 for protected content, and 429 for a rate or usage limit.

Dosya advertises class-2 WebDAV locking for client compatibility. A normal LOCK receives an opaque token with a one-hour timeout, but that token is not a persistent Dosya content lock. Real 423 responses come from file/folder protection, an ancestor lock, a sealed Vault destination, or a locked WordPress backup.
Steps
- Stop automatic retries and record the verb, source path, destination path, HTTP status, response text, time, and client version. Remove authorization headers and
dos_…secrets before saving a log. - For 403, read the body: key scope, WebDAV protocol selection, key/role IP or active-hour conditions, workspace pin, membership, role’s WebDAV gate, action permission, smart-view target, extension policy, and folder anchor each have different remedies.
- For 412 Precondition Failed, refresh the target and compare it with the local item.
If-Matchrefuses an overwrite after the ETag changed;If-None-Match: *orOverwrite: Frefuses replacing a name that now exists. - For 423 Locked, inspect the target and every destination ancestor in Dosya. Unlock through the relevant file, folder, Vault, or backup control; repeatedly issuing WebDAV UNLOCK cannot bypass a product lock.
- For 429, pause concurrent work and honor
Retry-After. Dosya applies a 1,200 requests/minute IP gate, a 600 requests/minute user gate, and any explicit key or role usage limits. - Retry one non-destructive operation after the cause changes, then refresh the containing folder. If the same status remains, keep the captured evidence and escalate without broadening unrelated permissions.

A read-only key returns 403 before a write. MOVE requires full scope plus rename permission when the name changes, upload permission when the parent changes, and delete permission when overwriting an existing destination. A locked source or destination returns 423. A changed concurrent destination can return 409 with a retry message rather than 412.
Avoid deleting and recreating the mount as the first response: that can clear useful status details and does not change a server-side role, lock, key scope, or content precondition.
Expected result
The client retry occurs only after the status-specific cause is corrected: 403 after permission or policy repair, 412 after reconciling changed state, 423 after an authorized unlock, or 429 after backoff. No access boundary is widened merely to silence the message.
Related guides
Was this helpful?
Loading helpfulness results…
Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.
Questions and replies
Ask about the steps in this guide. Questions are reviewed before publication.
Keep account details, credentials and private files out of public questions. Use private support for those.
Loading questions…
Sign in to your Dosya account to ask a question.