Why SFTP’s port is often mistaken for FTPS and how the confusion hurts developers. By Alex Lim.
SFTP uses TCP 22 by default, but many newcomers confuse it with FTPS (which also runs on 21). The article explains why this happens: both protocols employ widely‑known ports in documentation, leading to cross‑protocol assumptions. For developers building secure remote file transfers, clarifying the distinct port usage demystifies deployment and helps avoid integration errors.
The main points projected in this article:
- Port 22: sole command/control channel for SFTP; never used by FTPS.
- Port 990: TLS‑enabled FTPS mode—not true “21” usage.
- Confusion stems from shared documentation citing both protocols on 21/22.
- Developers must verify SSHD config (
Port 22) and usenetstatchecks to confirm SFTP’s port. - Best practice: document the correct port in project READMEs; test deployments with explicit
ssh -p 22.
The article sheds light on a subtle but crucial detail: correct port usage prevents integration headaches. For teams adopting modern CI/CD workflows, understanding SFTP’s exclusive TCP 22 vs. FTPS’s optional TLS‑enabled TCP 990 eliminates port‑confusion errors in automated deployments—making it a significant advancement for DevOps stability and clarity. Nice one!
[Read More]