FTP reply code 452 means the server cannot complete the requested action because there is not enough storage space. This typically occurs during file uploads (STOR, APPE) when the server's disk partition is full or the user's quota has been reached. Unlike 552 (permanent size-related rejection), 452 is temporary — the condition may change if files are deleted or quotas are reset. The server may also return 452 if the temporary space needed for file processing (such as antivirus scanning before moving the file to its final location) is insufficient.
The partition where the FTP files are stored has reached capacity. No new files can be written until space is freed. This affects all users on the server, not just the current session.
The FTP user has reached their configured storage quota. The user needs to delete files to free space, or an administrator needs to increase the quota.
The server writes uploaded files to a temporary directory first (for scanning or atomic move operations). If the temp partition is full, uploads fail even if the destination has space.
If you have server access, check the disk usage on the FTP storage partition. Free space by removing old files, logs, or temporary data.
df -h /var/ftp
Use DELE to remove old or unnecessary files from your FTP directory to free up quota space. Use LIST to see file sizes and identify large files to remove.
If you need more space than your quota allows, contact the server administrator to request a quota increase.
Try uploading a very small test file (a few bytes). If this succeeds, the disk is not completely full but your specific file exceeds the remaining space.
The server encountered an internal error while processing the command. The client should retry later.
The file operation was rejected because it exceeds the storage limit or allocation.
The file or directory operation failed. The path does not exist, or access is denied.