Error 550 Can't create directory: No such file or directory
pawzy opened this issue · 8 comments
I am getting the "Error 550 Can't create directory: No such file or directory" error upon committing. The log says that MKDIR failed creating a directory. I have checked the permissions on ftp and as I have made one initial commit to ftp and everything worked I don't think it has anything to do with ftp permissions.
Me too
my error logs
`MKDIR failed.
MKDIRs failed.
Commit failed.
{ Error: 550 Create directory operation failed.
at Ftp.parse (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/jsftp/lib/jsftp.js:223:11)
at Ftp.parseResponse (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/jsftp/lib/jsftp.js:146:8)
at Stream.pipeline.on.data (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/jsftp/lib/jsftp.js:112:10)
at emitOne (events.js:115:13)
at Stream.emit (events.js:210:7)
at ResponseParser.reemit (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/duplexer/index.js:70:25)
at emitOne (events.js:115:13)
at ResponseParser.emit (events.js:210:7)
at readableAddChunk (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/readable-stream/lib/_stream_readable.js:195:16)
at ResponseParser.Readable.push (/home/mtuchi/Workspace/C4T-Ed/node_modules/mtuchi_ftpsync/node_modules/readable-stream/lib/_stream_readable.js:162:10) code: 550 }
,
Any fix for this ? @evanplaice
Good question. What does your config look like. Are there any file permission issues.
Currently, this tool depends on some outdated JSFTP features. It would be best to workaround those first. My attention is currently devoted to other projects. If you'd like to work on this I'll provide guidance/support. Otherwise, it's going to be on the back burner for a bit.
My config file look like this
{ "local": "assets/storage/", "remote": "downloads", "host": "10.0.0.1", "port": 21, "user": "***", "pass": "****", "connections": "2", "ignore": [ ".htaccess" ] }
I have a micro controller that i can access on that ip address 10.0.0.1
Try starting the relative directories with ./
{ "local": "./assets/storage/", "remote": "./downloads", "host": "10.0.0.1", "port": 21, "user": "", "pass": "*", "connections": "2", "ignore": [ ".htaccess" ] }
Do the directories have read, write, and list access enabled?
Still getting the same error.
The file permissions on the remote are
For downloads
For a folder inside downloads
Try changing permissions on downloads to 666 (rw for user, group, all). It's possible that node is running as a user other than the one you're logged in as. In which case it won't be able to write to downloads.
The downloads permission are fixed to 755 i can not change that
Do you think that might be the issue ?