Repository Locked
The requested URL returned error: 423 - remote: operator reason - the repository is locked by the instance operator.
Repository Locked
Symptom
A clone, fetch or push over HTTPS fails with the reason your instance operator wrote, in place of <operator reason>:
remote: <operator reason>
fatal: unable to access 'https://<INSTANCE>.git.eu/<USERNAME>/<REPO>.git/': The requested URL returned error: 423
Over SSH, only the reason line appears:
<operator reason>
Cause
The instance operator locked the repository, for example during a review or a move. While it is locked, every git operation on it is refused, over HTTPS and SSH, for every user. HTTP status 423 means Locked.
Diagnose
Read the reason line: it is the operator's own text and usually says why and for how long. The status 423 on HTTPS confirms the lock.
Fix
Option A - Wait for the unlock (recommended)
Nothing is wrong on your side, and your local commits are safe. Push again once the operator lifts the lock.
Option B - Contact the operator or the owner
If the reason gives no end date, ask the repository owner or the instance operator.
Verify
git ls-remote origin
It lists the branches and tags again.
Prevent
- Nothing to do on your side: the lock is an operator decision.