Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

deivid

After further investigation I found that the default installations of OpenSSH on Windows (both the Chocolatey OpenSSH or the SSH that comes bundled as a Windows feature) will NOT configure the sftp Subsystem.

It would be nice to have that in the instructions:
https://winscp.net/eng/docs/guide_windows_openssh_server
martin

Check you server's sshd_config. It probably has a wrong path to sftp-server.
deivid

Finally got it working, I had to set "SFTP Server" option to "sftp-server", looks like by default it will be trying to start an sftp-server executable on a wrong path.
deivid

Unable to start SSH session to windows Container using Windows built-in SSH Server

I seem unable to have WinSCP to connect to a Windows Container with the default SSH Server configured.

I can manually start an SSH session from PowerShell, so I can confirm SSH server is listening and working.

I can tell from the logs that WinSCP is properly authenticating and even reading the remote shell input.

It then seems to be sending this to the shell:
< 2024-06-16 09:22:01.666 PS C:\Users\localadmin> echo "WinSCP: this is end-of-file:0"

And keeps waiting forever for a response to this command, yet it seems to be receiving it:
< 2024-06-16 09:22:01.792 WinSCP: this is end-of-file:0
. 2024-06-16 09:22:01.792 Waiting for another 1 bytes
. 2024-06-16 09:22:01.792 Looking for incoming data
. 2024-06-16 09:22:01.792 Looking for network events
. 2024-06-16 09:22:01.814 Detected network event

It keeps waiting forever for this one additional byte, terminating finally with the message:
Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended).