cannot upload with private key

Do you read the FAQ?

• Yes.
• I am going to read now.

Describe the bug Upload on save does (still) not work, error is:

[error] Error: [<hostname>]: connect EBADF <ip>:<60000>
	at Client.<anonymous> (/Users/<removed>/.vscode/extensions/natizyskunk.sftp-1.13.2/dist/extension.js:61:99994)

To Reproduce Hit save, observe error, see output tab

Expected behavior Save and upload works w/o error

Screenshots –

Desktop (please complete the following information):

• OS: macOS 11.4
• VSCode 1.57.1
• Extension Version 1.13.2

Extension Logs from Startup - required

[07-07 20:23:37] [info] [file-save] /Users/<removed>/Sites/<link/to/my/file>.php
[07-07 20:23:37] [trace] handle upload file for /Users/<removed>/Sites/<link/to/my/file>.php
[07-07 20:23:37] [debug] Custom crypto binding not available
[07-07 20:23:37] [debug] Client: Trying <hostname> on port 60000 ...
[07-07 20:23:37] [debug] Local ident: 'SSH-2.0-ssh2js1.1.0'
[07-07 20:23:37] [debug] Socket error: connect EBADF <ip>:60000
[07-07 20:23:37] [error] Error: [<hostname>]: connect EBADF <ip>:60000
	at Client.<anonymous> (/Users/<removed>/.vscode/extensions/natizyskunk.sftp-1.13.2/dist/extension.js:61:99994)
	at Client.emit (events.js:327:22)
	at Socket.<anonymous> (/Users/<removed>/.vscode/extensions/natizyskunk.sftp-1.13.2/node_modules/ssh2/lib/client.js:724:12)
	at Socket.emit (events.js:315:20)
	at emitErrorNT (internal/streams/destroy.js:106:8)
	at emitErrorCloseNT (internal/streams/destroy.js:74:3)
	at processTicksAndRejections (internal/process/task_queues.js:80:21) download /Users/<removed>/Sites/<link/to/my/file>.php
[07-07 20:23:37] [debug] Socket closed

sftp.json

{
    "name": "<removed>",
    "host": "<removed>",
    "protocol": "sftp",
    "port": 60000,
    "username": "root",
    "remotePath": "/<removed>",
    "privateKeyPath": "/Users/<removed>/.ssh/id_ed25519",
    "uploadOnSave": true
}

Notes:

• I use sftp, custom port.
• I have not set a password.
• I use key file (id_ed25519.pub), key is valid and available.
• VS Code has “full disk access” in macOS settings.
• I can connect in Terminal successfully, it also worked flawlessly with liximomo an last VS Code Version.
• I’m puzzled.

[dexamenos]

Little Snitch is basically an outgoing firewall. It is used to block outgoing traffic.

See here for more details https://obdev.at/products/littlesnitch/index.html

I would assume that it is quite popular among Mac Users.

You can block specific hostnames, ports or IP addresses for every binary. Although my VSCode was set to “allow all traffic” I must have messed up some rules and set some to deny. Maybe also something changed in one of the last VSCode updates, as I have noticed, a couple of helper processes are now used (Little Snitch blocks on a per-process level).

[dexamenos]

@Natizyskunk : you might now officially beat me. 🤪🥊

I have solved the issue and it actually turned out to be on my end. Disabled Litte Snitch and everything works like a charm. 👍

I will still have to look into the details, as the VSCode binary was set to “allow all connection”.

Merci beaucoup for spending your time!