FTP is the File Transfer Protocol, a long-standing way to move files to a web server; FTPS is the same protocol wrapped in TLS so the connection is encrypted. RankGear offers both as publishing transports wherever the target server supports them.
| Term | FTP and FTPS |
|---|---|
| Category | APIs, Reliability and Publishing |
| Also known as | FTP, FTPS |
| Where it appears | Deployment protocol selector |
What it means in RankGear
When RankGear pushes generated files to your site, it needs a transport to carry them. FTP and FTPS are two of the choices in the deployment protocol selector. Plain FTP sends credentials and file contents in the clear, which is fine on a trusted local network but risky over the open internet. FTPS adds a TLS layer on top of the same commands, so logins and payloads travel encrypted. RankGear treats them as one selectable option because they share the same underlying model, differing only in whether the channel is secured.
How to interpret it
Pick the protocol your host actually supports, and prefer FTPS over bare FTP whenever the server offers it, since the only practical difference is encryption. If a publish fails, read the connection status and diagnostics before retrying: a timeout or a dropped socket points to a transient network problem worth one more attempt, while an authentication rejection or a permission error points to configuration and will keep failing until the credentials or remote path are corrected. The distinction matters because retrying a bad login wastes time without ever succeeding.
Example
You configure a deployment to a shared host that advertises FTPS on port 21 with explicit TLS. RankGear connects, negotiates the TLS session, and uploads the batch. One file times out mid-transfer; RankGear applies a single bounded retry and it completes. Later you point a second deployment at a server that only speaks plain FTP, so RankGear falls back to an unencrypted channel and surfaces that state clearly, letting you decide whether that host is acceptable for the files you are sending.
Important considerations
- FTP transmits credentials and data without encryption; use FTPS instead whenever the server supports it, and avoid plain FTP over untrusted networks.
- Credential tests should be read-only where possible so a connection check never alters files on the remote server.
- Secrets such as passwords and keys stay redacted in status output and logs; treat the stored credentials as sensitive.
- Server support varies. Some hosts disable FTP entirely or require specific TLS modes and ports, so the working option depends on the target, not on a universal default.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.