Skip to content
File transfer9 min readOct 15, 2026

FTP 550 Error: Fix Permission Denied and Failed to Open File

An FTP 550 reply means the server did not perform the requested file action. The same code can represent a missing file, denied access, invalid path or server-side restriction.

FTP 550Access deniedFile pathWrite permission
Remote files and folders in Varkuna FTP

What does FTP error 550 mean?

The standard meaning of 550 is that the requested action was not taken because the file is unavailable. The server text may add “File not found,” “Access denied,” “Permission denied” or “Failed to open file.”

It normally appears after login during RETR, STOR, DELE, RNFR, RNTO or a directory operation. It is different from a 530 login failure and from a 425 data-connection failure.

Which operation failed?

OperationPossible causesFirst check
DownloadFile missing or no read accessName, letter case and remote directory
UploadNo directory write access or quota exhaustedDestination, free space and account permission
DeleteDelete policy, ownership or file lockFile owner and server rule
RenameMissing source, invalid target or file-system boundaryRNFR/RNTO paths and target name
Change directoryDirectory missing or no traversal permissionFull path and parent-directory access

Checks in the FTP client

  1. 1
    Refresh the listing

    Another process may have moved or removed the file. Retrieve the current remote directory contents.

  2. 2
    Check letter case

    On a Linux server, File.txt and file.txt are normally different names.

  3. 3
    Confirm the current directory

    The FTP account root may differ from the real file-system root on the server.

  4. 4
    Test a simple name

    Use a small file and a short safe name to isolate size limits and naming filters.

  5. 5
    Read the connection log

    The command immediately before the 550 reply identifies the denied operation.

Why can read, write and delete permissions differ?

Being able to read a file does not mean the account can create a new one in the same directory. Create, delete and rename operations usually depend on parent-directory permission, and the FTP service may apply separate operation rules.

On hosting systems, the web server and FTP user can run with different owners or groups. Correct ownership and directory permissions for that model instead of masking the problem with 777.

Other causes beyond permissions

Quota or full disk

An upload can be denied when account or storage limits are reached.

Invalid file name

The operating system or server may block selected characters, extensions or reserved names.

Read-only location

System directories, backup storage or a disk remounted read-only cannot be modified.

File lock

A file held by another process may not be deleted or renamed.

Virtual-directory rule

The FTP path may map to storage with a separate set of access controls.

Server administrator checklist

FTP logs

Review the 550 detail together with the command, user and target path.

Effective identity

Confirm which file-system identity the FTP service uses for the operation.

Path permissions

Check traversal through every parent and the required permission at the destination.

Quota and storage

Inspect free space, quota, inodes and any read-only mount state.

550 does not identify one cause

Do not reset the password or open every permission based only on the code. The failed command and server message provide the useful distinction.

550 Failed to open file: download versus upload

Start with the command immediately before the reply. A 550 after RETR concerns retrieving the named remote file. Verify the current directory, exact letter case, file existence and read permission. A 550 after STOR concerns storing data at the destination; check the parent directory and any existing target.

An FTP-visible path is not necessarily the operating-system path. A hosting account might see /public_html while the administrator sees a longer path beneath an account root. Use the path returned in that FTP session rather than pasting a shell path into the client.

If a new test file uploads but overwriting an existing file fails, compare the existing file owner and write permission. If upload completes and rename fails, inspect RNFR/RNTO and the parent-directory policy. Temporary upload-and-rename workflows require more than permission to stream file contents.

Observed resultNext investigation
RETR fails for one fileExact name, remote location and read access
STOR fails for every new fileParent write/traversal permission, FTP authorization and storage limits
New upload works; overwrite failsExisting target ownership, write access and overwrite policy
Transfer works; RNTO failsRename restrictions, target name and parent-directory access
The reply text matters

Storage and naming failures can also use codes such as 452, 552 or 553. Follow the actual reply and server log instead of assuming every failed upload is an access-permission problem.

Continue

Put the guide into practice.

Review the related Varkuna product or open its detailed user guide.