Troubleshooting
API 401
Section titled “API 401”- Header must be
access-token, notAuthorization. - Token deleted or past
expires_at. - OIDC exchange: wrong issuer, audience, or subject. Compare JWT claims to the trust rule.
Git Authentication failed
Section titled “Git Authentication failed”- Password must be the access token.
- Token needs
GIT_HTTP_READ(clone) andGIT_HTTP_WRITE(push). - Confirm the path:
/r/<username>/<repo>.giton hostamendable.io.
Git Repository not found / 404
Section titled “Git Repository not found / 404”- Wrong username or repo name.
- Token scope is
SELECTED_REPOand this repo is not on the list.
Create repo 422
Section titled “Create repo 422”- Active quota (free: 5) or total quota (free: 25).
storage_bucket_idis notACTIVEor not yours.
Create repo 409
Section titled “Create repo 409”Name already used by you.
Webhook never fires
Section titled “Webhook never fires”- Events list does not include
push(orcreate/delete). - URL is HTTP, localhost, or a private IP. Production rejects those.
- Check deliveries:
amendable webhook deliveries ID --json.
Webhook 401 in your receiver
Section titled “Webhook 401 in your receiver”You hashed parsed JSON instead of the raw body, or you expected a sha256= prefix. Amendable sends hex only.
BYO Verify AccessDenied
Section titled “BYO Verify AccessDenied”Trust policy sub / aud / issuer host mismatch. Copy from GET /v1/storage-buckets/oidc-setup. sub is account:<uuid>.
BYO Git 500, error log empty, bucket still ACTIVE
Section titled “BYO Git 500, error log empty, bucket still ACTIVE”Layer object missing or unreadable. Verify only probes the canary key. Do not delete {prefix}layers/*.tar.gz. A warm node may still clone from cache.
whoami username unknown
Section titled “whoami username unknown”The API has no /v1/me. The CLI infers username from GET /v1/repositories. Create a repo, or set username in the config file / AMENDABLE_USERNAME.