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

martin

snoopen wrote:

Perhaps then I'd suggest protocol should change port but port should not change protocol.

It's there by purpose to combat common problem that people change port to 21, keeping SFTP protocol, because they are not aware that FTPS has nothing to do with SFTP.
snoopen

Oops sorry. You're right that sequence does work. I'm not sure what I was doing yesterday. Maybe I pressed save in between.

Perhaps then I'd suggest protocol should change port but port should not change protocol.

Either way, thank you for your assistance. :D
martin

Re: Can't keep protocol with custom port

Well, 443 is a standard port for HTTPS (WebDAVS).

Anyway, I cannot reproduce your problem. I start with SFTP (the default protocol). I enter port number 443, WebDAV (encrypted) is autoselected. Now I can select SFTP protocol back, keeping the 443 port.
snoopen

Can't keep protocol with custom port

I connect to a few servers that have the port number set to custom values.

The problem I'm having in version 5.7.5 occurs when I select SFTP as the protocol and then set port to be 443. After changing the port, the protocol is automatically changed to WebDAV.

Vice-versa if I try and set port to 443 then change protocol to SFTP. The port changes back to 22.

For the affected sessions I have been able to work around this by deleting the FSProtocol line in the winscp.ini file and ensuring port is set to 443.

This did not seem to occur in previous versions. I think the version update also changed the protocol for my saved sessions to WebDAV when it used to be SFTP, but I can't be sure I didn't quickly edit and save in a rush without noticing the protocol change.

Note: I'm using the portable version of WinSCP from PortableApps.