550 Not found when logging in

Right after creating a service or a new user, the first FTP login can fail with a 550 Not found error.

Why it happens

On login, many FTP clients immediately ask the server about the user's home directory. Object storage backends have no real directories - a "directory" only exists once something is stored under its path - so a brand-new user whose home directory has never received a file gets not found.

This is the empty-directory quirk of object storage; see Cloud storage limitations for the family it belongs to.

The fix

Upload any file - the home directory springs into existence and the error never comes back.

Alternatively, create the directory on the backend first:

• S3 and Google Cloud Storage consoles can create empty folders directly.
• Azure cannot - upload a file into the new directory to create it.

Still having issues? Contact support and we can help you directly.