sftp deployment fails on windows about vscode-deploy-reloaded HOT 10 CLOSED

@seatrout You have an error in the configuration file.
wrong: "privatekey":"…"
right: "privateKey":"…"

look it: (a little patience please)

from vscode-deploy-reloaded.

@seatrout

Try set tryKeyboard setting in target to (true).

from vscode-deploy-reloaded.

Nope: same error. But then the sshd daemon on the server is configured only to allow private key logins

from vscode-deploy-reloaded.

Ooops: checking this, the server does allow password authentication. I thought I had stopped that. But the machine is only accessible from inside the network so it should be safe

from vscode-deploy-reloaded.

I'm sorry for these stupid questions but I can't see what's gone wrong
Does the sftp subsystem want an openSSH format key?
Is there a worked example showing how to translate an absolute Windows file path into something this extension understands?
Is there any way to log a more informative error message so we know why the authentication fails?

from vscode-deploy-reloaded.

Use a path like c:/ssh/camerazero_id_rsa for private key on windows ... relative paths should have a leading . like ./ssh/camerazero_id_rsa ... those paths are mapped to your .vscode or your .vscode-deploy-reloaded sub folder inside your home directory

from vscode-deploy-reloaded.

No: still doesn't work. With the key id_rsa placed in the ssh subfolder of
.vscode-deploy-reloaded in my home dir (next to the logs subfolder)
and the relevant line
"privatekey":"./ssh/id_rsa"
in my workplace configuration, I get the same error message.

Connecting with an ssh program using the same key from the same computer works perfectly well ...
Should I be restarting the editor between edits to the configuration?

from vscode-deploy-reloaded.

I think this has to be a bug introduced into vscode itself somehow. I have tried other extensions and they won't work, but sftp from the command line in the terminal of vscode works perfectly well. And there are complaints here of this functionality breaking with the upgrade to vscode 1.20.

I may try deleting and reinstalling all of the vscode config, but that seems a bit drastic

from vscode-deploy-reloaded.

@zamkevich @seatrout

Now the error makes sense!

My eyes are too old for such typos :D

from vscode-deploy-reloaded.

Thank you, both for finding my mistake, and taking the trouble to animate the solution. It's all working now. I will in future trust the intellisense rather than simply typing!
A

from vscode-deploy-reloaded.