Overview
During FTP sessions, CuteFTP may display error codes that originate directly from the remote FTP server. These codes indicate that the server is refusing login credentials, blocking file uploads, rejecting file names, or denying permission due to quota limitations.
This article explains the causes and resolutions for the following common FTP errors:
- 530 – Not Logged In / Password Rejected
- 553 – Permission Denied (Invalid File Name)
- 552 – Disk Quota Exceeded
- 550 – Permission Denied / No Such File or Folder
530 Error – Not Logged In / Password Rejected
Typical Messages:
530 Not logged in.
530 Login authentication failed.
530 Password rejected.
ERROR: Not logged in.
STATUS: Connection closed.
Cause
This error does not come from CuteFTP. It is returned by the remote FTP server when the login attempt fails.
The server is rejecting one or more of the following:
- Host address
- Username
- Password
Common reasons include:
- Incorrect FTP credentials
- Recently changed hosting account settings
- Password reset by the hosting provider
- Using login details meant for a different service (e.g., control panel instead of FTP)
Resolution
-
Double-check host, username, and password.
Your FTP credentials may differ from other access credentials (e.g., email or hosting control panel).
-
Confirm with the FTP administrator or hosting provider.
Globalscape does not provide FTP accounts and cannot access your server information.
-
Update the stored login details in CuteFTP Site Manager:
- Press F4 to open Site Manager
- CuteFTP Home: Select the site → Edit details on the right
- CuteFTP Pro: Right‑click the site → Properties → Edit login fields
-
If the site belongs to your hosting provider:
Check their support documentation or control panel for the correct FTP settings.
553 Error – Permission Denied (Invalid File Name)
Example Message:
553 your file.ext: Permission denied.
ERROR: Access denied.
Cause
The remote FTP server rejected the file name, not the file itself.
Many FTP servers block uploads if the filename contains:
- Spaces
- Special characters
- Symbols
- Unsupported file extensions
In the given example, the upload was blocked due to a space in the file name.
Resolution
-
Rename the file to use only:
- Letters
- Numbers
- No spaces or special characters
-
Follow file‑naming best practices to ensure compatibility.
-
If links on your website reference the file, update those links to match the new file name.
552 Error – Disk Quota Exceeded
Example Message:
150 Opening ASCII mode data connection…
552 Transfer aborted. Disk quota exceeded.
ERROR: Exceeded storage allocation.
Cause
This error originates from the remote FTP server and indicates that your account has exceeded its allocated storage quota.
Two common causes:
- Your FTP account’s assigned disk space is full.
- The file you are uploading is too large and would exceed the quota if completed.
Resolution
- Delete unnecessary files from the remote server to free space.
- Request additional storage from your web hosting provider or FTP administrator.
- Try the upload again once sufficient space is available.
550 Error – Permission Denied / No Such File or Folder
Example Messages:
550 yourfile.txt: No such file.
550 Permission Denied.
550 /pub/yourfile.txt: No such file or folder.
Cause & Resolution
There are two different scenarios for this error:
Example 1 – “No such file or folder” during upload
This is not an actual error and should be ignored.
Before uploading, CuteFTP sends:
- SIZE command → Checks if a file exists
- CWD command → Checks if a folder exists
Both return 550 if the file/folder does not already exist, which is expected.
Upload continues normally with the STOR command.
Resolution
No action required. This is informational only.
Example 2 – Permission Denied
The remote FTP server is blocking the upload due to insufficient permissions associated with your FTP account.
Resolution
Contact the hosting provider or FTP server admin and request corrected permissions or access rights for the account.
Summary
These FTP error codes do not originate from CuteFTP; they are returned directly by the remote FTP server. Each error indicates a different condition:
| Error Code |
Meaning |
Typical Cause |
| 530 |
Login failed |
Incorrect host/username/password |
| 553 |
Permission denied (filename) |
Invalid or unsupported filename |
| 552 |
Disk quota exceeded |
No space left on server |
| 550 |
Permission denied / No such file |
Missing permissions or normal pre‑upload checks |
After identifying the cause, use the resolutions above or contact the hosting provider if account‑level changes are required.