Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error 'no such file' during upload on save #915

Open
davidesnc opened this issue Apr 26, 2021 · 64 comments
Open

error 'no such file' during upload on save #915

davidesnc opened this issue Apr 26, 2021 · 64 comments

Comments

@davidesnc
Copy link

I have an error during the upload when saving file
this is the log on view->option->sftp
could you help me ?
thanks in advance

[04-26 14:48:02] [error] Error: No such file
at SFTPStream._transform (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:412:27)
at SFTPStream.Transform._read (internal/streams/transform.js:205:10)
at SFTPStream._read (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:183:15)
at SFTPStream.Transform._write (internal/streams/transform.js:193:12)
at writeOrBuffer (internal/streams/writable.js:358:12)
at SFTPStream.Writable.write (internal/streams/writable.js:303:10)
at Channel.ondata (internal/streams/readable.js:719:22)
at Channel.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Channel.Readable.push (internal/streams/readable.js:223:10)
at SSH2Stream. (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2/lib/Channel.js:167:15)
at SSH2Stream.emit (events.js:315:20)
at parsePacket (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:3288:10)
at SSH2Stream._transform (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:694:13)
at SSH2Stream.Transform._read (internal/streams/transform.js:205:10)
at SSH2Stream._read (/Users/davide/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:253:15)
at SSH2Stream.Transform._write (internal/streams/transform.js:193:12)
at writeOrBuffer (internal/streams/writable.js:358:12)
at SSH2Stream.Writable.write (internal/streams/writable.js:303:10)
at Socket.ondata (internal/streams/readable.js:719:22)
at Socket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Socket.Readable.push (internal/streams/readable.js:223:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23) when local ➞ remote /opt/data/iseo/progetti/v364/server/uti/internal_obfuscate.php

@mbinette
Copy link

I am getting the same issue. I've used this extension for over a year and it only stopped over the weekend. Worked perfectly on Friday, 4/23/2021, but failed first thing this morning. Possibly a VSCode update? I'm using Insiders Edition and haven't tried the regular edition. @davidesnc , are you on Insiders or regular edition of VSCode?

@Darktex
Copy link

Darktex commented Apr 26, 2021

+1 on insiders. Does seem like it does upload, so it's just a false positive.

@mbinette
Copy link

Not a false positive. I agree that some of the times it still writes the files but not others. If you Sync Local -> Remote on a directory for instance some files get wiped out on the remote or end up blank or cut short. My entire build fails after a Sync because of missing file contents on the remote.

@davidesnc
Copy link
Author

I am getting the same issue. I've used this extension for over a year and it only stopped over the weekend. Worked perfectly on Friday, 4/23/2021, but failed first thing this morning. Possibly a VSCode update? I'm using Insiders Edition and haven't tried the regular edition. @davidesnc , are you on Insiders or regular edition of VSCode?

I'm using insider version too.
I agree that probably was an update of vscode to create the issue.
I'm searching for an alternative, may be do you have some suggestions ?

@mbinette
Copy link

I opened a bug report on VS Code but there have been a few hundred commits since last Friday. I wasn't able to find anything specific that is an obvious reason for this. I'm going to try installing the non Insiders edition to see if it still works and to check which Nodejs version is being used. The errors are in calls to stream which is internal to Nodejs. Otherwise, I might need to switch to using the Microsoft "Remote - SSH" extension which I didn't want to do since my remote doesn't use git.

@mbinette
Copy link

As expected, VS Code, non Insiders, works fine. It is also on Node 12.18.3 where Insiders is on 14.16.0. I'm not sure when Insiders updated but it might be a Node issue.

@davidesnc
Copy link
Author

@mbinette
thanks for your investigation job.

@Webbeh
Copy link

Webbeh commented Apr 27, 2021

Hi. Just confirming that I get the same issue on Insiders. Didn't try normal edition.

@davidesnc
Copy link
Author

a stupid workaround, but it works for me.
~/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js
row 412 and follow....
/* //davidescnc
var err = new Error(msg
|| STATUS_CODE_STR[code]
|| 'Unknown status');
err.code = code;
err.lang = lang;
cb(err);
*/ //davidesnc
cb();

@madwebskills
Copy link

Just another "me too", but to add that switching to "FTP" protocol instead of "SFTP" still works (but very slow for some reason). Not ideal, but helped in a pinch.

@Webbeh
Copy link

Webbeh commented May 5, 2021

a stupid workaround, but it works for me.
~/.vscode-insiders/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js
row 412 and follow....
/* //davidescnc
var err = new Error(msg
|| STATUS_CODE_STR[code]
|| 'Unknown status');
err.code = code;
err.lang = lang;
cb(err);
*/ //davidesnc
cb();

Cleaner approach to this would actually be to edit the line n°386 this from

if (code === false)
  return;

to this

if (code === false || code === STATUS_CODE.NO_SUCH_FILE)
  return;

This way, you don't lose other error warnings, just the "no such file" one. Still, quite bad to have to resort to this kind of workaround...

@bika-c
Copy link

bika-c commented May 5, 2021

Same issue here. Just got updated today normal edition 1.56.0. So I guess they didn't fix the bug in the insider version and now the normal edition has the same problem. Regardless of the error, the files are still synced.

@aesculus
Copy link

aesculus commented May 6, 2021

Cleaner approach to this would actually be to edit the line n°386 this from

if (code === false)
  return;

to this

if (code === false || code === STATUS_CODE.NO_SUCH_FILE)
  return;

This way, you don't lose other error warnings, just the "no such file" one. Still, quite bad to have to resort to this kind of workaround...

This did not work for me. It stuck reporting it was uploading.

I did just implement @davidesnc hack. That works fine on the surface.

@feijoa-pine
Copy link

feijoa-pine commented May 6, 2021

Hello, please overlook my fault if you find because this is the first time to post comment here github.

I was getting same issue with probability normal edition v1.12.9.
So, I added a patch code to c:\Users<username>.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js line: 388 like below reference to workarounds which are introduced by davidesnc and Webbeh above.

if (code === STATUS_CODE.OK) {
to this
if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {

And, restart VSCode.

It seems working well for the present.

@bika-c
Copy link

bika-c commented May 6, 2021

code === STATUS_CODE.NO_SUCH_FILE

Thanks! Hoping the vscode could officially fix this any time soon

@Prodian0013
Copy link

another workaround is to downgrade to 1.55 https://code.visualstudio.com/updates/v1_55

@joshuachough
Copy link

joshuachough commented May 6, 2021

Another "me too". also getting this on normal version 1.56.0. however, the upload function does seem to be uploading correctly despite the "no such file" error toast

@rendiliaw
Copy link

Hello, please overlook my fault if you find because this is the first time to post comment here github.

I was getting same issue with probability normal edition v1.12.9.
So, I added a patch code to c:\Users.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js line: 388 like below reference to workarounds which are introduced by davidesnc and Webbeh above.

if (code === STATUS_CODE.OK) {
to this
if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {

And, restart VSCode.

It seems working well for the present.

It's almost work perfectly, but doesn't work when you sync from local -> remote

@Gorvey
Copy link

Gorvey commented May 6, 2021

well, i downgrade vscode to 1.55 and reinstall this ext fix this problem

@kineticvenergy
Copy link

I'm also getting this error. I've noticed that it will successfully transfer some files and others will be transferred with zero bytes (resulting in an error). I've rolled back to 1.55 and turned off auto updates for now. Fingers crossed it gets resolved soon.

@Webbeh
Copy link

Webbeh commented May 6, 2021

This did not work for me. It stuck reporting it was uploading.

Oops, just saw that myself, it stuck reporting the upload of the first file you uploaded in that session.

Do it in line 388 instead :
if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {
instead of
if (code === STATUS_CODE.OK)

Of course, revert line 386 back.

Result :
image

@Webbeh
Copy link

Webbeh commented May 6, 2021

It's almost work perfectly, but doesn't work when you sync from local -> remote

You may have another issue. Try using the fix in my previous message. If it still doesn't work, use #915 (comment)

@Mickeywaugh
Copy link

Sure update Issued this bug. I reinstalled version 1.55.2, and sftp extensions works well again.

@rendiliaw
Copy link

It's almost work perfectly, but doesn't work when you sync from local -> remote

You may have another issue. Try using the fix in my previous message. If it still doesn't work, use #915 (comment)

Actually, I've already done everything. It's fine when it's come to save file by file. But, when you trying to perform local sync to remote, it become infinite loading... or maybe it just me

@rendiliaw
Copy link

The final solution I do, is downgrade to 55

@rick3rt
Copy link

rick3rt commented May 6, 2021

It's almost work perfectly, but doesn't work when you sync from local -> remote

Since upload local -> remote also still works, you can apply this patch to avoid seeing the error.
In file ...\.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js
change line 416

cb(err);

to

cb();

That way you can still upload files, dont have to downgrade, and just dont see the annoying error.

@Webbeh
Copy link

Webbeh commented May 6, 2021

It's almost work perfectly, but doesn't work when you sync from local -> remote

Since upload local -> remote also still works, you can apply this patch to avoid seeing the error.
In file ...\.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js
change line 416

cb(err);

to

cb();

That way you can still upload files, dont have to downgrade, and just dont see the annoying error.

This does the same as my solution, except it discards all errors.

@rick3rt
Copy link

rick3rt commented May 6, 2021

@Webbeh I see that this discards all errrors, but your fix didnt solve the erorr on upload local -> remote for me. The error vscode throws me is 'Handle is invalid'. The error code is 4, corresponding to FAILURE.

I reverted my previous patch on line 416, and made line 388:

if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE || code === STATUS_CODE.FAILURE) {

However, this indeed still discards a lot of errors

@Jany-M
Copy link

Jany-M commented May 6, 2021

Do it in line 388 instead :
if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {
instead of
if (code === STATUS_CODE.OK)

That didnt work for me, local -> remote still not uploading and getting popup error.

But this did!

@Webbeh
Copy link

Webbeh commented May 12, 2021

You all need to start mentioning which OS you're using VSCode on...

@TheFivery
Copy link

You all need to start mentioning which OS you're using VSCode on...

My apologies. I'm using Pop OS 20.10 and VS Code Insiders 1.57.0. And thank you for developing an extension that I use daily. I know it must be frustrating to fix bugs that vscode has caused.

@mbinette
Copy link

Should this issue be logged with the ssh2-streams or ssh2 projects? It seems like this extension only broke because those libraries are returning something different than expected.

@netdjw
Copy link

netdjw commented May 12, 2021

You all need to start mentioning which OS you're using VSCode on...

Sorry, I'm using Windows 10 Home 20H2 (build: 19042.964)

VS Code:
Version: 1.56.1 (user setup)
Commit: e713fe9b05fc24facbec8f34fb1017133858842b
Date: 2021-05-06T10:08:05.141Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Windows_NT x64 10.0.19042

I use VSCode from WSL 2.

In WSL I use Ubuntu 20.04.

@ylynfatt
Copy link

ylynfatt commented May 12, 2021

I'm getting the same issue but the files do seem to upload successfully despite the error message. I am using:

Version: 1.56.1
Commit: e713fe9b05fc24facbec8f34fb1017133858842b
Date: 2021-05-06T10:08:24.325Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Darwin x64 20.4.0 (macOS Big Sur 11.3.1)

@rendiliaw
Copy link

Version: 1.55.2 (system setup)
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:35:57.887Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 6.1.7601

Still hold at 1.55
Once you upgrade to 1.56, it's gonna be the end road

@heyaco
Copy link

heyaco commented May 13, 2021

Where the patch at?

@StrasGus
Copy link

Hello, please overlook my fault if you find because this is the first time to post comment here github.

I was getting same issue with probability normal edition v1.12.9.
So, I added a patch code to c:\Users.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js line: 388 like below reference to workarounds which are introduced by davidesnc and Webbeh above.

if (code === STATUS_CODE.OK) {
to this
if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {

And, restart VSCode.

It seems working well for the present.

It work fine for me ! Thanks.

@jewettg
Copy link

jewettg commented May 13, 2021

@hscsolutions1
Copy link

Same here:
vscode 1.56.0
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Windows_NT x64 10.0.19042

@Webbeh
Copy link

Webbeh commented May 16, 2021

For everyone implementing any of those fixes : please roll them back and use the fix in #919 (comment)

It will work better for everyone, no matter your OS.

And stop waiting for an update to this plugin, it's most likely not gonna happen :(

@ZihaoZheng98
Copy link

yeah,this is a false negative = =

@mattizhu
Copy link

Can confirm, I can upload/download from my remote path just fine but gives me a "No such file" error regardless. Rolling back to the previous version works fine with no error messages.

@Webbeh
Copy link

Webbeh commented May 16, 2021

@ZihaoZheng98 @mattizhu there's a fix 3 posts before this one.

@TheZoker
Copy link

For me changing the protocol from "protocol": "sftp", to "protocol": "ftp", also did the trick

@rwildcard
Copy link

Hey I found the fix...
https://github.com/Natizyskunk/ssh2-streams/commit/e1db386ff9b0fc145c67dc13ada3e969d59cc51f#diff-11c2413775403ed66594f387ae0a38ec06ed746902424f86c7cbbbc7e395f4ca
ssh2-streams may get updated one day but its only 2 lines of code to be added to the sftp
image
If you are here you probably will know how to find your sftp file but you can find the path in an earlier entry.
This helps because it shows you the lines of code needed to be changed.

@faitno
Copy link

faitno commented May 18, 2021

I have error too:

[05-18 18:49:19] [error] Error: No such file
	at SFTPStream._transform (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:412:27)
	at SFTPStream.Transform._read (internal/streams/transform.js:205:10)
	at SFTPStream._read (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:183:15)
	at SFTPStream.Transform._write (internal/streams/transform.js:193:12)
	at writeOrBuffer (internal/streams/writable.js:358:12)
	at SFTPStream.Writable.write (internal/streams/writable.js:303:10)
	at Channel.ondata (internal/streams/readable.js:719:22)
	at Channel.emit (events.js:315:20)
	at addChunk (internal/streams/readable.js:309:12)
	at readableAddChunk (internal/streams/readable.js:284:9)
	at Channel.Readable.push (internal/streams/readable.js:223:10)
	at SSH2Stream.<anonymous> (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2/lib/Channel.js:167:15)
	at SSH2Stream.emit (events.js:315:20)
	at parsePacket (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:3288:10)
	at SSH2Stream._transform (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:694:13)
	at SSH2Stream.Transform._read (internal/streams/transform.js:205:10)
	at SSH2Stream._read (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:253:15)
	at SSH2Stream.Transform._write (internal/streams/transform.js:193:12)
	at writeOrBuffer (internal/streams/writable.js:358:12)
	at SSH2Stream.Writable.write (internal/streams/writable.js:303:10)
	at Socket.ondata (internal/streams/readable.js:719:22)
	at Socket.emit (events.js:315:20)
	at addChunk (internal/streams/readable.js:309:12)
	at readableAddChunk (internal/streams/readable.js:284:9)
	at Socket.Readable.push (internal/streams/readable.js:223:10)
	at TCP.onStreamRead (internal/stream_base_commons.js:188:23) when local ➞ remote /**//**.php

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-14T00:18:25.979Z (4 days ago)
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Darwin x64 19.6.0

check any solution listing above - not work for me

@rendiliaw
Copy link

I have error too:

[05-18 18:49:19] [error] Error: No such file
	at SFTPStream._transform (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:412:27)
	at SFTPStream.Transform._read (internal/streams/transform.js:205:10)
	at SFTPStream._read (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js:183:15)
	at SFTPStream.Transform._write (internal/streams/transform.js:193:12)
	at writeOrBuffer (internal/streams/writable.js:358:12)
	at SFTPStream.Writable.write (internal/streams/writable.js:303:10)
	at Channel.ondata (internal/streams/readable.js:719:22)
	at Channel.emit (events.js:315:20)
	at addChunk (internal/streams/readable.js:309:12)
	at readableAddChunk (internal/streams/readable.js:284:9)
	at Channel.Readable.push (internal/streams/readable.js:223:10)
	at SSH2Stream.<anonymous> (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2/lib/Channel.js:167:15)
	at SSH2Stream.emit (events.js:315:20)
	at parsePacket (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:3288:10)
	at SSH2Stream._transform (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:694:13)
	at SSH2Stream.Transform._read (internal/streams/transform.js:205:10)
	at SSH2Stream._read (/**//.vscode-oss/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/ssh.js:253:15)
	at SSH2Stream.Transform._write (internal/streams/transform.js:193:12)
	at writeOrBuffer (internal/streams/writable.js:358:12)
	at SSH2Stream.Writable.write (internal/streams/writable.js:303:10)
	at Socket.ondata (internal/streams/readable.js:719:22)
	at Socket.emit (events.js:315:20)
	at addChunk (internal/streams/readable.js:309:12)
	at readableAddChunk (internal/streams/readable.js:284:9)
	at Socket.Readable.push (internal/streams/readable.js:223:10)
	at TCP.onStreamRead (internal/stream_base_commons.js:188:23) when local ➞ remote /**//**.php

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-14T00:18:25.979Z (4 days ago)
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Darwin x64 19.6.0

check any solution listing above - not work for me

Have you ever tried solution from @rwildcard ?
It's work for me

@Natizyskunk
Copy link

Just follow thoses steps to make it working again without any issues (temporary fix) : #919 (comment)

@ashish-khokhar
Copy link

another workaround is to downgrade to 1.55 https://code.visualstudio.com/updates/v1_55

I actually like to do this instead, thanks for the version number and link.

@floeffler-dimabay
Copy link

Same issue for me. 1.56 -> no such File Message.
Just upgraded to 1.57. Same issue here.

Version: 1.57.0
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T17:22:31.215Z (1 day ago)
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 19.6.0

@Rom4eg
Copy link

Rom4eg commented Jul 1, 2021

Same problem

Version: 1.57.1
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:26:56.255Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Linux x64 5.4.0-77-generic

@Natizyskunk
Copy link

Natizyskunk commented Jul 6, 2021

You can try my version, i've fixed a lot of bugs, maybe this will fix yours 🙂
https://github.com/Natizyskunk/vscode-sftp/releases

@baberuth22
Copy link

baberuth22 commented Aug 24, 2021

Amazing. Thank you @Natizyskunk!

@dmnyk
Copy link

dmnyk commented Aug 27, 2021

Just use my version (v1.13.0) that implement the new ssh2 v1.1.0 version that fix every problem 🙂 https://github.com/Natizyskunk/vscode-sftp/releases

Thanks for the efforts @Natizyskunk . Your version of the extension solved my issue.

@antoni-codes
Copy link

Just use my version (v1.13.0) that implement the new ssh2 v1.1.0 version that fix every problem 🙂 https://github.com/Natizyskunk/vscode-sftp/releases

This help me. Thanks!!

@SevaShpun
Copy link

Hello, please overlook my fault if you find because this is the first time to post comment here github.

I was getting same issue with probability normal edition v1.12.9. So, I added a patch code to c:\Users.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js line: 388 like below reference to workarounds which are introduced by davidesnc and Webbeh above.

if (code === STATUS_CODE.OK) { to this if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) {

And, restart VSCode.

It seems working well for the present.

Work! Thank's! 👯

@brunostuder
Copy link

brunostuder commented Jan 18, 2022

SOLUTION FOR "NO SUCH FILE" WHEN USING SFTP PROTOCOL

There's the solution that will solve the problem!

If you get "No such file" error on SFTP (both branch) it can be because when using "protocol": "sftp" you're supposed to enter the absolute (like really absolute path), not like with FTP where the absolute path start at the "user root"

There's example not working:

{
"name": "Infomaniak",
"host": "example.ftp.infomaniak.com",
"protocol": "sftp",
"username": "user",
"remotePath": "/sites/cbdetc.bms-web.ch/Prestashop", <--- Don't do that if you use "SFTP Protocol"
"interactiveAuth": true,
"password": "mypass",
"uploadOnSave": true,
"connectTimeout":1000000000,
"ignore": [".vscode", ".git", ".DS_Store", "cache", "var", "vendor", "src", "_Cache", "admin1260", "app", "bin", "tools", "translations","localization", "webservice", "yaml", "img"]
}

There's a working exemple:

{
"name": "CBDetc Infomaniak",
"host": "example.ftp.infomaniak.com",
"protocol": "sftp",
"username": "myuser",
"remotePath": "/home/clients/gfoiaun0q4cb7t0anxfasdgfnax/sites/cbdetc.bms-web.ch/Prestashop", <--- There's the solution
"interactiveAuth": true,
"password": "mypass!",
"uploadOnSave": true,
"connectTimeout":1000000000,
"ignore": [".vscode", ".git", ".DS_Store", "cache", "var", "vendor", "src", "_Cache", "admin1260", "app", "bin", "tools", "translations","localization", "webservice", "yaml", "img"]
}

Hope it will help some of you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests