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

Command 'sshfs.*' not found #1

Closed
jack-guy opened this issue May 9, 2018 · 30 comments
Closed

Command 'sshfs.*' not found #1

jack-guy opened this issue May 9, 2018 · 30 comments
Labels
bug Something isn't working waiting Waiting for confirmation, more information, ...

Comments

@jack-guy
Copy link

jack-guy commented May 9, 2018

Hi, thanks for making this extension! I'm really excited to try it out!

Unfortunately, any sshfs: whatever command I run gives me an error in the latest version of VS Code (1.23):

command 'sshfs.new' not found

Are the commands correctly registered in the extensions API?

@jack-guy jack-guy changed the title command 'sshfs.*' not found Command 'sshfs.*' not found May 9, 2018
@thijndehaas
Copy link

thijndehaas commented May 10, 2018

Same problem here..
command 'sshfs.connect' not found

@SchoofsKelvin SchoofsKelvin added the bug Something isn't working label May 10, 2018
SchoofsKelvin added a commit that referenced this issue May 10, 2018
@SchoofsKelvin
Copy link
Owner

SchoofsKelvin commented May 10, 2018

I didn't properly specify the activationEvents in the package.json, resulting in the extension (and thus the commands) not being loaded for command executions. I've published the fix (in version 1.3.2) to the marketplace.

@weswithley
Copy link

weswithley commented Jun 19, 2018

Same problem +1.
command 'sshfs.connect' not found,

Vscode-sshfs extension version : 1.7.1
VS code version : 1.24.1

Thanks.

@SchoofsKelvin
Copy link
Owner

Interesting, the activationEvent contains that command, and the command gets properly registered.

What causes the error to appear, and how often does this happen?

@SchoofsKelvin SchoofsKelvin reopened this Jun 22, 2018
@weswithley
Copy link

weswithley commented Jun 24, 2018

Hi,

my steps flow as below :

  1. go preference with VS Code and set my host up.
  2. command + shift + p & choose " connect a SSH FS as workspace folder".
  3. and VS code just shows that error message to me.

it always happened with every time i use it.
or maybe something wrong with my setting?

my setting as below :

"sshfs.configs": [ { 
  "root": "~/root", 
  "host": "xx.xx.xx.xx", 
  "port": 22, 
  "username": "root", 
  "password": "password"
} ]

Thanks for help. ^^

@SchoofsKelvin
Copy link
Owner

I've been able to reproduce it (only) once, and reloading the window fixed it. Even though vscode's logs showed it had started the extension, it seemed like it didn't.

Which version of the extension are you using?

@SchoofsKelvin SchoofsKelvin added the waiting Waiting for confirmation, more information, ... label Jul 6, 2018
@weswithley
Copy link

weswithley commented Jul 12, 2018

Hi, SchoofsKelvin,

I changed the version of Vscode-sshfs from 1.7.1 to 1.9.2,
and the _command 'sshfs.connect' not found_ doesn't show up anymore,
looks like the problem resolved,
maybe this issue could be closed?

btw,
pity that i still can't connect to my office server by Vscode-sshfs,
but using the ssh [email protected] connection with command-line is fine,
i think maybe that's my server setting problems,
so, i would go ask to my partners in these few days,
if any further infos,
i would let you know asap.

Thanks for your great help.

@SchoofsKelvin
Copy link
Owner

Since this bug doesn't seem to show up anymore, I'll close this issue.

pity that i still can't connect to my office server by Vscode-sshfs,
but using the ssh [email protected] connection with command-line is fine,

Feel free to open a new issue for that. It might (also) be an issue with the config, and/or the fact that I don't make use of ~/.ssh/config yet.

@aaaaaadrian
Copy link

I am having this issue as well. I am running VSCode 1.25.1 and SSH FS 1.9.2 and it can't find any of the extensions to actually run. So my config looks good, but it won't even attempt to connect because .connect isn't found.

I have uninstalled, restarted, reinstalled, etc. Nothing has worked yet.

@baterson
Copy link

baterson commented Aug 24, 2018

I have the same issue. Extension was working fine one day, next day it stops with errors:
command 'sshfs.<command_name>' not found .
VSCode Version 1.26.1 (1.26.1) .
SSH FS 1.9.2 .

@hudson940
Copy link

I have the same issue. 'sshfs.*' not fount. I'm using vs-code ver: 1.26.1 and sshfs ver: 1.9.2

@zswanson
Copy link

zswanson commented Sep 8, 2018

Similar, exists on sshfs 1.9.2 and vs-code version 1.27.1 (user setup version) and running in Windows 10.

@marcospolanco
Copy link

Same problem with SSHFS version 2.5, VS-CODE 1.28.1 and SSFS 1.10.0 on Mac.

@AchmadFathoni
Copy link

Also happen on SSHFS 1.10.0, VSCODE 1.28.1, Ubuntu 16.04

@SchoofsKelvin
Copy link
Owner

Does the problem keep occurring after restarting vscode (or your pc) ?

@SchoofsKelvin SchoofsKelvin reopened this Oct 19, 2018
@aaaaaadrian
Copy link

aaaaaadrian commented Oct 19, 2018

Deleting my config and entering it new corrected the issue for me

*edit: I am on 1.28.2 (user setup) on Windows 7. Just an FYI

@SchoofsKelvin
Copy link
Owner

Closing due to lack of activity

@dwarburt
Copy link

dwarburt commented Nov 1, 2018

I'm getting this now on Fedora 29, vscode 1.28.2, kelvin.vscode-sshfs-1.11.1. Restarting and reloading don't help, nor does deleting and recreating the configuration. I'll try to debug it a bit.

Edit 1: My problem was that I had tried to fill out the settings directly instead of generating it and left out the name.

Edit 2: The reason I got it wrong was because I was following along with the JSON object in the default settings, which doesn't have a name.

@ncot-tech
Copy link

Edit 1: My problem was that I had tried to fill out the settings directly instead of generating it and left out the name.

Edit 2: The reason I got it wrong was because I was following along with the JSON object in the default settings, which doesn't have a name.

Same for me, the example config isn't quite correct. Using the VS Code ctrl-shift-P method works OK.

I'm using it on my Chromebook with the experimental Linux environment btw.

@kwinz
Copy link

kwinz commented Nov 7, 2018

Version 1.28.2 Using this plugin for the first time. Got this error. A bit frustrating.
Restarting Visual Studio Code resolved it.

@SchoofsKelvin
Copy link
Owner

All configurations need the name field, along with either putty and/or a combination of host, username, ...

The documentation might not be the best right now, but within one configuration object, assume all the fields above are still present (unless overwritten in lines that came afterwards)

@rehovey
Copy link

rehovey commented Nov 15, 2018

On Mac High Sierra VS Code 1.29 SSHFS v1.11.1 (latest in Marketplace) - I had to ensure I was using the 'name' property and restart VS Code but it is working for me.

@fennecinspace
Copy link

+1

@kshkaran2k
Copy link

I am also getting command 'sshfs.new' not found error.
I have configured to access my code present in AWS EC2 instance. I have restarted the code also after the installation of the extension.

I am using Windows 7, VS Code Version: 1.26.1, Architecture: x64 with SSH-FS version 1,11,2 (directly download and installed from VS Code).

@skworden
Copy link

skworden commented Dec 12, 2018

+1 using vs code version 1.29.1 and windows 10. It was working until I updated vs code.

****EDIT

got it to work again.

using the quick commands (CTRL + SHIFT + P etc ) didn't work. I had to go to

File -> preferences -> extensions ->ssh fs configuration -> edit in settins.json

and edit it manually. Here is a working config file

"sshfs.configs": [
        {
            "label": "Some friendly name",//This is the name that shows under available connections
            "root": "/www",
            "host": "11.111.111.111",
            "port": 22,
            "username": "my_username",
            "privateKeyPath": "myPPKFile", //you could remove this an use password
            "putty": false, //This has to be here
            "name":"Anything"//this has to be here.  it is the name that shows in you file structure after you connect 
        },
    ]

After you edit the config you must restart / reload VS Code. After you restart / reload vs code you will see your connections in the "ssh file systems" area in your file explorer section.

@skworden
Copy link

I am also getting command 'sshfs.new' not found error.
I have configured to access my code present in AWS EC2 instance. I have restarted the code also after the installation of the extension.

I am using Windows 7, VS Code Version: 1.26.1, Architecture: x64 with SSH-FS version 1,11,2 (directly download and installed from VS Code).

Make sure you have the keys "putty" and "name" in your config or it will not work.

@bluecamel
Copy link

Thanks so much, @lifedup. It works now.

@SchoofsKelvin
Copy link
Owner

I am also getting command 'sshfs.new' not found error.
I have configured to access my code present in AWS EC2 instance. I have restarted the code also after the installation of the extension.
I am using Windows 7, VS Code Version: 1.26.1, Architecture: x64 with SSH-FS version 1,11,2 (directly download and installed from VS Code).

Make sure you have the keys "putty" and "name" in your config or it will not work.

Thanks to this, I was able to figure out what caused this bug. It should be fixed now (2fca495) under version 1.12.2 of the extension. The extension will now ignore nameless configurations, and give then a random name in the background.

@lopugit
Copy link

lopugit commented May 6, 2019

@SchoofsKelvin I'm still getting this error on this branch https://github.com/SchoofsKelvin/vscode-sshfs/tree/feature/search and on

Version: 1.34.0-insider (user setup)
Commit: 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Date: 2019-05-01T00:22:05.899Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 6.1.7601

@SchoofsKelvin
Copy link
Owner

@lopugit Does this error only happen when using the search branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working waiting Waiting for confirmation, more information, ...
Projects
None yet
Development

No branches or pull requests