FTP reply code 552 is a permanent rejection indicating the file operation cannot be completed because a storage limit has been exceeded. Unlike 452 (temporary storage issue), 552 means the server considers this a permanent condition — the specific file is too large for the allowed allocation, or the hard quota limit has been reached and will not be automatically reset. This typically occurs during uploads when the file exceeds the user's hard quota, the individual file size exceeds a server-configured maximum, or the append operation would push the file past its size limit.
The user's storage allocation has been permanently exceeded. Unlike soft quotas (which return 452 and may reset), hard quotas return 552 and require administrator intervention or file deletion to resolve.
The server has a per-file size limit and the uploaded file exceeds it. This limit is separate from the user's total quota and applies to individual files.
The underlying filesystem has a limit on allocation blocks for the user or group, and the transfer would exceed it. This is common on systems using filesystem-level quotas.
If available, check your current storage usage through a control panel or by listing files with sizes. Compare your usage against your quota.
Remove unnecessary files from the FTP server to free up quota. Use LIST to identify large files, then DELE to remove them.
Contact the server administrator to increase your storage allocation or file size limit.
If the file exceeds a size limit, try compressing it before upload. Use gzip, zip, or a similar compression tool to reduce the file size.
The server does not have enough disk space to complete the file operation.
The file or directory operation failed. The path does not exist, or access is denied.
The filename or path is not allowed by the server's naming rules or access policy.