SFTP repository unusable on Windows 11: "getsockname failed: Not a socket"
Environment:
- plakar v1.1.4
- Windows 11 (amd64)
- SFTP integration installed via
plakar pkg add sftp
Description
Opening an SFTP repository fails consistently with the following error:
failed to open the repository at sftp://user@myhost.example.com:/data/mind: failed to start ssh master: exit status 0xffffffff: getsockname failed: Not a socket
However, from the same PowerShell session, SSH and SFTP connect perfectly (key-based auth, no password prompt):
PS C:\Users\user> ssh user@myhost.example.com
# → connection OK
PS C:\Users\user> sftp user@myhost.example.com
Connected to myhost.example.com.
# → connection OK
Command used
plakar at "@srvplakar" backup fs://C:\Users\user
What I've tried, without success
- Reinstalling the integration (
plakar pkg rm sftp then plakar pkg add sftp)
- Adding
ControlMaster no / ControlPath none to ~/.ssh/config
The getsockname failed: Not a socket error seems related to SSH multiplexing (ControlMaster), which is known not to work on Windows. Is this expected behavior, or a limitation of the Windows support for SFTP?
Thanks in advance.
SFTP repository unusable on Windows 11: "getsockname failed: Not a socket"
Environment:
plakar pkg add sftpDescription
Opening an SFTP repository fails consistently with the following error:
However, from the same PowerShell session, SSH and SFTP connect perfectly (key-based auth, no password prompt):
Command used
What I've tried, without success
plakar pkg rm sftpthenplakar pkg add sftp)ControlMaster no/ControlPath noneto~/.ssh/configThe
getsockname failed: Not a socketerror seems related to SSH multiplexing (ControlMaster), which is known not to work on Windows. Is this expected behavior, or a limitation of the Windows support for SFTP?Thanks in advance.