All guides

FTPS (explicit TLS)

For partner systems that cannot use SFTP.

FTPS is FTP secured with TLS. GetSFTP supports explicit TLS only (the client connects to port 21 and upgrades with AUTH TLS). Plain FTP and implicit TLS are not supported.

FTPS needs a password

FTPS has no SSH key authentication, so FTPS logins always use a password. An organization admin must allow passwords for your organization and set one for your login. Prefer SFTP with an SSH key when your system supports it.

1. Host: sftp.getsftp.com. Port: 21. Encryption: explicit TLS (AUTH TLS), TLS 1.2 or later.
2. Use passive mode. Active mode is disabled.
3. Allow outbound connections to ports 21 and 50000-50100 on our static IP. The server tells your client which passive port to use for each transfer.
4. If transfers stall after login, your firewall is probably blocking the passive port range.

File times and permissions

FTP clients that set a file's time after an upload (MFMT) get a success reply, and nothing changes. FTP SITE commands, including SITE CHMOD, are turned off: if your client changes permissions on upload, turn that option off.

Files keep the time they were uploaded, and the server has no Unix file permissions. Over SFTP, a client that sets a file's time or permissions after an upload gets a success reply and nothing changes; over FTPS the same holds for the time. Who can read or change files is set by your organization in the portal.

Verify the server on first connect: compare the host key fingerprint your client shows with the one in the portal under Get started, step Connect. If they differ, do not continue and contact [email protected].