You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SFTP error upload no such file after update VS code 1.56.0 #919
while upload a file from local to remote, it show an error no such file and connection time out 10000. but the file is uploading without problem, just showing an error. This happen because I am update VS code version to 1.56.0.
Extension version: 1.12.9
VS Code version: Code 1.56.0 (cfa2e218100323074ac1948c885448fdf4de2a7f, 2021-05-04T22:09:06.405Z)
OS version: Windows_NT x64 10.0.19041
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)
Well, just now I went to the remote server to have a look.
Although it was said that there was an error prompt of no such file, the remote file has been updated, which does not affect the use.
Reacted by Mateusz Grynczel, Pawnesh Rai, Geoff Jackson, Saumya Majumder, Sébastien Mascha and chamindu94
Well, just now I went to the remote server to have a look.
Although it was said that there was an error prompt of no such file, the remote file has been updated, which does not affect the use.
Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.
Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.
Be careful with it, some times, when you update file, is can come empty. And if update folder, some files can be empty, some files may contain text from other files.
I downgraded my VSCode to previous version
Reacted by gfork, Vincent, ybbbbt, José Luis Massón, Aleksandr Gumroian, JamzumSum, Cleverson Vieira , Olivier Bitsch, 米大熊, tomokei5634 and 4 more
Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.
Be careful with it, some times, when you update file, is can come empty. And if update folder, some files can be empty, some files may contain text from other files.
I downgraded my VSCode to previous version
Updating the SSH2 package has fixed the issue for me,
just need to change the ssh2 version 1.1.0 in the package.json "extensions/liximomo.sftp-1.12.9/package.json,
and run npm install, https://www.npmjs.com/package/ssh2
@shivam-geek solution works for me. (Windows 10)
in ~.vscode\extensions\liximomo.sftp-1.12.9\package.json change "ssh2": "^x.x.x" to "ssh2": "^1.1.0"
then run in .vscode\extensions\liximomo.sftp-1.12.9> npm install
Then just make a pull request and i'll hapilly merged it :)
I see that you wrote a post on how to rebuild the extension so I suppose you're easily able to do that and it would be cool if you can do it.
You can follow the pull request template available here.
If someone still facing this problem in 2024 and come here from search, here is my case and solution.
Problem:
Natizyskunk sftp fork work fine while I'm connecting by ftp, but starting to show "no such file" error when I trying switch to sftp. At the same time, connection with same exact credential via ssh client or console work just fine. So, it's definitely plugin problem.
Solution:
Just remove leading slash in the "remotePath" parameter. So, if it was this: "remotePath": "/folder/subfolder/"
you must try this: "remotePath": "folder/subfolder/"
It solves error for me.
Reacted by Alexis Rippstein, Ashtowake, skydogtech and Raihan Ali
Activity
houguang commentedon May 6, 2021
Evllis commentedon May 6, 2021
The same problem
Version: 1.56.0 (user setup)
Commit: cfa2e218100323074ac1948c885448fdf4de2a7f
Date: 2021-05-04T22:09:06.405Z
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.19041
Evllis commentedon May 6, 2021
After looking at the questions from other users, it was suggested that vscode should be downgraded to 1.55 to solve the problem.
But I don't want to be demoted and wait for another way.
yayaw commentedon May 6, 2021
Evllis commentedon May 6, 2021
Well, just now I went to the remote server to have a look.
Although it was said that there was an error prompt of no such file, the remote file has been updated, which does not affect the use.
SebastianSava commentedon May 6, 2021
For now, you can change protocol from sftp to ftp, and port from 22 to 21. Just until get update :)
Andika7 commentedon May 6, 2021
well, your right I will wait for the update
Gforky commentedon May 6, 2021
Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.
alteco-usa commentedon May 6, 2021
Be careful with it, some times, when you update file, is can come empty. And if update folder, some files can be empty, some files may contain text from other files.
I downgraded my VSCode to previous version
PolarAir commentedon May 6, 2021
Same problem here.
The files have been uploaded successfully. Just 'set modify time' seems bugged
Gforky commentedon May 6, 2021
Thanks for your remind, this issue is annoying...
PlayGrowBot commentedon May 6, 2021
Same here!
File upload well with 1 popup error!
mastercrys commentedon May 6, 2021
Same problem here and cannot switch to ftp only mode and cannot downgrade le vscode version cause of infrastructure requirements.
Please fix asap
EDIT: can confirm that the file is successfully uploaded even if the error appears
96 remaining items
nlp4whp commentedon Jul 12, 2021
thanks a lot!
lackneets commentedon Jul 13, 2021
The problem is still existing on VSCode 1.58. Why is this issue been closed? 🙁
Natizyskunk commentedon Jul 13, 2021
@lackneets,
As i've stated above :
Natizyskunk commentedon Jul 13, 2021
@nlp4whp,
No problem 😀
IlanVivanco commentedon Jul 13, 2021
@Natizyskunk are you planning to maintain the new fork?
Natizyskunk commentedon Jul 13, 2021
@IlanVivanco,
Yes for sure, i'll try my best to keep it up to date and to fix most of the problems people will come across.
nazadounet commentedon Aug 18, 2021
Work perfectly :) thx mate
CCYYZZNN commentedon Sep 2, 2021
it works
PaPa31 commentedon Nov 10, 2021
I made a new build of
sftp.vsixfile.This build makes
Upload Changed Filescommand visible.And it adds "Ctrl+Alt+U" keyboard shortcut to the
Upload Changed Filescommand.You can download the build and install with:
F1)Extensions: Install from VSIXcommandEntersftp-workaround-upload-bug.vsixInstallI also wrote not a small post how to rebuild vsix extension.
Natizyskunk commentedon Nov 12, 2021
@PaPa31,
Why not just use my version. I've take over this extension and I'm actively mainting it and adding new features.
You can find it here.
Cheers :)
PaPa31 commentedon Nov 12, 2021
Because your version doesn't work!
I mean the 'Upload Changed Files' command doesn't work.
UNDERSTAND!!!!
Natizyskunk commentedon Nov 12, 2021
@PaPa31,
Then just make a pull request and i'll hapilly merged it :)
I see that you wrote a post on how to rebuild the extension so I suppose you're easily able to do that and it would be cool if you can do it.
You can follow the pull request template available here.
Thanks in advance !
PaPa31 commentedon Nov 12, 2021
Natizyskunk
Ok! I'll do this!
Natizyskunk commentedon Nov 12, 2021
@PaPa31,
Thx a lot ! :)
Yalme commentedon Jul 3, 2024
If someone still facing this problem in 2024 and come here from search, here is my case and solution.
Problem:
Natizyskunk sftp fork work fine while I'm connecting by ftp, but starting to show "no such file" error when I trying switch to sftp. At the same time, connection with same exact credential via ssh client or console work just fine. So, it's definitely plugin problem.
Solution:
Just remove leading slash in the "remotePath" parameter. So, if it was this:
"remotePath": "/folder/subfolder/"you must try this:
"remotePath": "folder/subfolder/"It solves error for me.