Skip to content

SFTP error upload no such file after update VS code 1.56.0 #919

Closed

Description

@Andika7

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
Item Value
CPUs Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)
GPU Status 2d_canvas: enabled
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
Load (avg) undefined
Memory (System) 11.87GB (5.66GB free)
Process Argv --crash-reporter-id 1ad20214-094e-4571-829c-44d1a08acd9f
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt602cf:30294773
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291489
pythontb:30283811
pythonvspyt551:30291414
vspre833cf:30267465
pythonptprofiler:30281270
vscnewfiletext:30294816
vshan820:30294714
pythondataviewer:30285071
vscus158:30286553
vscgsv2ct:30294353

Activity

  1. houguang commented on May 6, 2021

    @houguang

    image

  2. Evllis commented on May 6, 2021

    @Evllis

    image

    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

  3. Evllis commented on May 6, 2021

    @Evllis

    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.

  4. yayaw commented on May 6, 2021

    @yayaw

    image

  5. Evllis commented on May 6, 2021

    @Evllis

    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.

  6. SebastianSava commented on May 6, 2021

    @SebastianSava

    For now, you can change protocol from sftp to ftp, and port from 22 to 21. Just until get update :)

  7. Andika7 commented on May 6, 2021

    @Andika7
    Author

    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.

    well, your right I will wait for the update

  8. reopened this on May 6, 2021
  9. Gforky commented on May 6, 2021

    @Gforky

    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.

  10. alteco-usa commented on May 6, 2021

    @alteco-usa

    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

  11. PolarAir commented on May 6, 2021

    @PolarAir

    Same problem here.
    The files have been uploaded successfully. Just 'set modify time' seems bugged

  12. Gforky commented on May 6, 2021

    @Gforky

    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

    Thanks for your remind, this issue is annoying...

  13. PlayGrowBot commented on May 6, 2021

    @PlayGrowBot

    Same here!
    File upload well with 1 popup error!

  14. mastercrys commented on May 6, 2021

    @mastercrys

    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

  15. 96 remaining items

  16. nlp4whp commented on Jul 12, 2021

    @nlp4whp

    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!

  17. lackneets commented on Jul 13, 2021

    @lackneets

    The problem is still existing on VSCode 1.58. Why is this issue been closed? 🙁

  18. Natizyskunk commented on Jul 13, 2021

    @Natizyskunk

    @lackneets,
    As i've stated above :

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

  19. Natizyskunk commented on Jul 13, 2021

    @Natizyskunk

    @nlp4whp,

    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!

    No problem 😀

  20. IlanVivanco commented on Jul 13, 2021

    @IlanVivanco

    @Natizyskunk are you planning to maintain the new fork?

  21. Natizyskunk commented on Jul 13, 2021

    @Natizyskunk

    @IlanVivanco,

    @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.

  22. nazadounet commented on Aug 18, 2021

    @nazadounet

    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

    Work perfectly :) thx mate

  23. CCYYZZNN commented on Sep 2, 2021

    @CCYYZZNN

    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

    it works

  24. PaPa31 commented on Nov 10, 2021

    @PaPa31

    I made a new build of sftp.vsix file.

    This build makes Upload Changed Files command visible.

    And it adds "Ctrl+Alt+U" keyboard shortcut to the Upload Changed Files command.

    You can download the build and install with:

    • open Command Palette (press F1)
    • enter Extensions: Install from VSIX command
    • press Enter
    • locate sftp-workaround-upload-bug.vsix
    • press Install

    I also wrote not a small post how to rebuild vsix extension.

  25. Natizyskunk commented on Nov 12, 2021

    @Natizyskunk

    @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 :)

  26. PaPa31 commented on Nov 12, 2021

    @PaPa31

    @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 :)

    Because your version doesn't work!

    I mean the 'Upload Changed Files' command doesn't work.

    UNDERSTAND!!!!

  27. Natizyskunk commented on Nov 12, 2021

    @Natizyskunk

    @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 !

  28. PaPa31 commented on Nov 12, 2021

    @PaPa31

    Natizyskunk

    Ok! I'll do this!

  29. Natizyskunk commented on Nov 12, 2021

    @Natizyskunk

    @PaPa31,

    Thx a lot ! :)

  30. Yalme commented on Jul 3, 2024

    @Yalme

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions