FTP publishing with "explicit SSL/TLS" option

Publishing
1

Hi. We used to publish from Sailwave to an FTP server over an unencrypted port 21 connection.

For security reasons the webhosting company I use has now removed plain FTP and requires “FTP with explicit SSL/TLS” - this is a secure connection but uses port 21 to initiate the connection (and then switches to SSL automatically).

Is it possible to allow port 21 to be used for secure connections in Sailwave? Well, I know the answer right now is that the interface doesn’t allow it - but would it be possible to add this functionality (explicit secure connections from port 21)? The only port I can connect to is 21.

If you’re still using the SocketTools library (I think so) then I believe there is a FTP_OPTION_SECURE_EXPLICIT option which I think would handle this.

Thank you for your consideration,

David

PS. I have seen the previous posts about using WINSCP or similar to publish out so I may need to investigate this in the meantime.

1 Like
2

Hi David,

The current version of Sailwave already has the option to use the FTP_OPTION_SECURE_EXPLICIT option by adding 10000 to the port number
so hopefully if you set your port to 10021 this will be port 21 with the FTP_OPTION_SECURE_EXPLICIT option added

Let me know how it goes

Regards

Jon

2 Likes
3

Jon - you absolute star - I’ve just set the port number to 10021 and it published straight away without issue.

Please accept my apologies if this was already mentioned in the documentation/release notes somewhere.

Thank you.