--- title: "507 Insufficient Storage — what it means and how to fix it" description: "The server cannot store what the request needs it to store — it is out of space or over quota. What causes an HTTP 507, what to try as a visitor, and what to check if it is your own site." url: https://atoneplace.net/error/507/ site: "At One Place" --- # HTTP 507 — Insufficient Storage **HTTP 507: Insufficient Storage** The server cannot store what the request needs it to store — it is out of space or over quota. ## What 507 actually means A WebDAV code that has been widely borrowed for any storage-exhaustion failure. The request was valid and would have succeeded, but the server has nowhere to put the result: the disk is full, the account is over its quota, or the storage backend rejected the write. Unlike most 5xx codes it has a clear and mundane fix, and the fix belongs to whoever runs the server. ## Common causes - The server's disk or volume is full - A per-user or per-account storage quota exceeded - A database or object storage backend out of space - Log files or temporary files filling the partition - Inodes exhausted even though free bytes remain ## If you're just trying to view the page 1. Free up space in your account if the service shows a quota — delete old files or empty the trash 2. If it is not your quota, wait and report it; the operator has to add space ## If it's your site 1. Check free space with `df -h`, and free inodes with `df -i` — an inode-exhausted filesystem reports space available but cannot create files 2. Look for runaway logs, orphaned temp files and old backups before expanding the volume 3. Add monitoring and alerting on disk usage at a threshold that leaves time to act 4. Return a clear message distinguishing "your quota" from "our disk"; they are very different for the user ## Reference - **Status code:** 507 - **Reason phrase:** Insufficient Storage - **Category:** 5xx — Server Error - **Cacheable by default:** No - **Defined in:** RFC 4918 §11.5 ## Common questions ### What does HTTP 507 mean? The server cannot store what the request needs it to store — it is out of space or over quota. A WebDAV code that has been widely borrowed for any storage-exhaustion failure. The request was valid and would have succeeded, but the server has nowhere to put the result: the disk is full, the account is over its quota, or the storage backend rejected the write. ### How do I fix a 507 error? Free up space in your account if the service shows a quota — delete old files or empty the trash ### Is 507 a client error or a server error? 507 is in the 5xx range, which means server error. The request was acceptable but the server could not fulfil it, so retrying later can succeed. ## Related pages - [500 Internal Server Error](https://atoneplace.net/error/500/) - [502 Bad Gateway](https://atoneplace.net/error/502/) - [503 Service Unavailable](https://atoneplace.net/error/503/) - [504 Gateway Timeout](https://atoneplace.net/error/504/) - [524 A Timeout Occurred](https://atoneplace.net/error/524/) - [521 Web Server Is Down](https://atoneplace.net/error/521/) - [522 Connection Timed Out](https://atoneplace.net/error/522/) - [520 Web Server Returned an Unknown Error](https://atoneplace.net/error/520/) - [525 SSL Handshake Failed](https://atoneplace.net/error/525/) - [526 Invalid SSL Certificate](https://atoneplace.net/error/526/) - [530 Origin DNS Error](https://atoneplace.net/error/530/) - [501 Not Implemented](https://atoneplace.net/error/501/) ## Sources - Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA (https://www.iana.org/assignments/http-status-codes/) - RFC 9110: HTTP Semantics — IETF (https://www.rfc-editor.org/rfc/rfc9110.html)