The server has no room to store the result.
When to use it
Disk full, or a storage quota reached.
Common causes and fixes
The server can’t store what the request needs. Usual causes: the disk or volume is full, the user’s storage quota is exhausted (Nextcloud and ownCloud return 507 for that), or the file system ran out of inodes even though df shows free space. Check with df -h and df -i on the server, and look for runaway log files or forgotten temporary uploads.
Fix the space problem, not the client: rotate and compress logs with logrotate, remove unused Docker images with docker system prune, clean temporary upload folders, or raise the quota. Retrying won’t help until space is freed. Many apps report a full disk as a generic 500 instead, so check disk usage whenever writes start failing, and alert well before 100%.
Server error (5xx)
5xx codes are server errors: the request may be fine, but the server or something behind it failed. These are worth alerting on.
What it looks like
HTTP/1.1 507 Insufficient StorageHow to send it
| Node.js / Express | res.status(507).end() |
|---|---|
| Python / Flask | return '', 507 |
| nginx | return 507; |
How to check it
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/