vs-deploy
vs-deploy copied to clipboard
mkloubert
No such file or directory
Can anyone shed any light into what this error is all about, and how to resolve it? [FAILED: Error: 553 Can't open that file: No such file or directory]
I have tried deploy with and without file exclusions, mappings, inclusions... all still have this message. The only files that actually upload, without warning, are in the root directory. Every other file/ directory throws that error.
Target type is ftp, Engine is jsftp.
Edit: I'm doing this on macOS Sierra.
Okay, I've discovered that if I manually create the directory structure on remote, uploading goes fine. However, when dealing with nested directories, the directory needed for a file to be uploaded into simply does not get created. I am attempting to do a first publish of a website, and it simply is not possible because of the nested directories.
Are there any thoughts about this? Or should I just do the first deploy with another software?
@telekovar
Sorry for the late answer!
My idea is, that jsftp does not support the creation of a deep directory structure. Have you tried the default engine?
Otherwise you should try to use another software like a FTP client for the first time.
@mkloubert It does look like both engines have the same issue with creating the directories. Works great for any file that already exists, however new files/ directories cannot be deployed.
@telekovar
Maybe a server issue?
When I deploy to my test FTP server (FileZilla), I have no problems ... with both engines.
The single file I have deployed, has a path like subDir1/subDir2/myFile.txt and the server does not have the directory at the beginning (it is empty / contains no files and folders).
If the directory does not exist, I do a single mkd execution, even if the file has a deep directory structure, which currently does not exist.
So, I think the server has to support this. What software do you use?
Thank you for looking into this. I tested with FileZilla, and it has no issues uploading. Keeping you up to date, I switched the engine again, to "ftp", and it is currently working. So, I'm going to remain hopeful it keeps working.