Artifactory "storage quota exceeded" in CI
Artifactory refused the upload because storage is full. A quota or disk limit was reached, so no new artifacts can be written until space is reclaimed.
What this error means
A deploy fails with "Storage quota exceeded" or "The system has reached its storage limit", and uploads stop across the instance until space frees up.
jf
[Error] server response: 403 Forbidden
Storage quota limit reached. Deployment is blocked until storage is reclaimed.Common causes
The instance reached its storage quota
Accumulated artifacts, snapshots, and caches filled the allotted storage, so Artifactory blocks new deploys.
No retention or cleanup on snapshot repos
Iterative CI builds pile up in snapshot repos without cleanup, exhausting storage over time.
How to fix it
Reclaim space and re-run
- Delete old snapshots and unused artifacts, then run garbage collection.
- Confirm storage is below the quota.
- Re-run the deploy once space is available.
Terminal
jf rt curl -XPOST "/api/system/storage/gc"Add retention on snapshot repos
Configure max unique snapshots or a cleanup policy so CI builds do not accumulate indefinitely.
How to prevent it
- Set retention limits on snapshot and CI repositories.
- Run garbage collection on a schedule.
- Alert before storage nears the quota so deploys never block.
Related guides
Artifactory "413 Request Entity Too Large" upload in CIFix Artifactory "413 Request Entity Too Large" in CI - a reverse proxy or Artifactory upload limit rejected a…
Artifactory "409 Conflict" immutable / existing artifact in CIFix Artifactory "409 Conflict" in CI - a release repo blocks overwriting an existing artifact, so republishin…
JFrog "You are not authorized to deploy" in CIFix Artifactory "You are not authorized to deploy artifacts" in CI - the token authenticated but the deploy p…