HTTP 423 Locked
The resource is locked, so the change was refused — common with WebDAV files and some APIs that lock records during processing.
The resource that is being accessed is lockedfile is locked Meaning
WebDAV (SharePoint, Nextcloud, ownCloud, IIS WebDAV) returns 423 when another user or a stale lock holds the file. Some APIs use 423 for records being processed or accounts locked after failed logins.
Common causes
- File open/checked out by another user or app
- Stale WebDAV lock after a crash
- Record locked while a background job processes it
- Account locked after too many attempts
⚡ Quick fix
- Close the file elsewhere or wait for the lock to expire
- Remove the stale lock (admin)
- Retry later for processing locks
Detailed fix by platform
Nextcloud
- bash
sudo -u www-data php occ files:scan --all # stale locks: enable maintenance mode and clear the oc_file_locks table, or use Redis-based locking
How to diagnose
- Holder — Who holds the lock and since when?
- Expiry — Does it clear on its own?
- Account — Is it a login lockout instead?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026