423 🌐 HTTP

HTTP 423 Locked

The resource is locked, so the change was refused — common with WebDAV files and some APIs that lock records during processing.

Seen on: REST API

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

  1. Close the file elsewhere or wait for the lock to expire
  2. Remove the stale lock (admin)
  3. Retry later for processing locks

Detailed fix by platform

Nextcloud

  1. 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

  1. Holder — Who holds the lock and since when?
  2. Expiry — Does it clear on its own?
  3. 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:

🧠 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.