-
Notifications
You must be signed in to change notification settings - Fork 277
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
SFTP error upload no such file after update VS code 1.56.0 #919
Comments
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. |
Well, just now I went to the remote server to have a look. |
For now, you can change protocol from sftp to ftp, and port from 22 to 21. Just until get update :) |
well, your right I will wait for the update |
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. |
Same problem here. |
Thanks for your remind, this issue is annoying... |
Same here! |
Same problem here and cannot switch to ftp only mode and cannot downgrade le vscode version cause of infrastructure requirements. EDIT: can confirm that the file is successfully uploaded even if the error appears |
Meet the same problem |
This could be problem with SSH executable path. Same error happens when you use Proxy command in ssh config and try connecting through terminal directly. Doing like so: Works. Is there a setting for SSH executable path?! |
Having the same issue. The extension is reporting error but the file is successfully uploaded to remote server:
liximomo.sftp version v1.12.9 Version: 1.56.0 (user setup) |
Yeah, same for me. Hopefully it's gonna be fixed soon :-) |
I have the same problem. MacBook Pro 16" |
me too |
The same problem |
Yeah this is annoying. And I'm not hoping for an update with 311 issues listed and the last commit 2 years ago... Is this extension abandoned? |
VSCode was recently bumped to node v14. I looked deeper into other packages (ssh2, ssh2-streams) and it lead me to ssh2-sftp-client package. In the overview it says that the node itself had some changes with streams that causes these errors. Node v15.3 had additional changes (or a rollback) that fixes the issue. In any way, this extension uses ssh2 and probably that's where the code should be updated and errors handled to work with node v14. I tried updating ssh2 package on this extension, but it didn't seem to help either. Most likely we'll have to wait until VSCode node is bumped to v15. |
I downgraded but here are some pointers on how to fix it temporarily: |
same here. got this error after VSCode upgrade. |
good question - anybody knows the answer if that's still maintained or should I start looking for alternative? |
It will be very sad to find out that the plugin has been abandoned :( I did not find a worthy alternative |
After creating .ssh/config file: [05-06 21:39:31] [warn] Can't set modified time to the file because Failure |
This warning disappears after adding this property to the configuration: "profiles": {} |
Sadly this repo looks like it is not maintained any more. |
@lighthousebulb Yeah... read @Natizyskunk's post. |
It seems it's time to switch to rsync or use https://marketplace.visualstudio.com/items?itemName=mkloubert.vscode-deploy-reloaded |
For Windows users using WSL (I tested it only with WSL2, but expecting the same results on WSL1):
|
Updating the SSH2 package has fixed the issue for me, |
@shivam-geek solution works for me. (Windows 10) |
I'll be damned it worked. thank you. I still do wish someone would either revive this repo or give me an equally solid alternative so I won't need work-arounds in the future. I almost went back to Atom over this. |
Hy Everyone Please just change SSH2 version to 1.1.0 in package.json and run npm i
|
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 a lot! |
The problem is still existing on VSCode 1.58. Why is this issue been closed? 🙁 |
@lackneets,
|
No problem 😀 |
@Natizyskunk are you planning to maintain the new fork? |
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. |
Work perfectly :) thx mate |
it works |
I made a new build of This build makes And it adds "Ctrl+Alt+U" keyboard shortcut to the You can download the build and install with:
I also wrote not a small post how to rebuild vsix extension. |
Ok! I'll do this! |
Thx a lot ! :) |
If someone still facing this problem in 2024 and come here from search, here is my case and solution. Problem: Solution: |
Issue Type: Bug
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
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: