507 Insufficient Storage
The server cannot store what it needs to complete the request, typically because its disk or the user's quota is full.
What 507 Insufficient Storage means
Defined by WebDAV in RFC 4918, and also used by some file and storage services. The condition is meant to be temporary.
Common causes
- The server's disk is full.
- The user's storage quota is used up.
- An upload that would exceed the space available.
How to fix 507 Insufficient Storage
- As a user, delete files or upgrade your storage plan.
- As an admin, check disk usage (df -h), clear old logs and temp files, and add disk space or alerts.
Example response
HTTP/1.1 507 Insufficient Storage
Content-Type: text/plain; charset=utf-8
507 Insufficient StorageHow to check for a 507 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 507) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 507:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 507 {
fmt.Println(res.Status)
}Specification
507 Insufficient Storage is defined in RFC 4918, section 11.5.
Related status codes
- 413
The request body is bigger than the server is willing to accept, usually because an upload is over the size limit.
- 500
Something went wrong on the server and it could not complete the request. It is a generic error and not your fault.
- 503
The server cannot handle the request right now, usually because it is overloaded or down for maintenance. Try again later.