FTP/FTPS Connections

Connect to FTP and FTPS (FTP over TLS) servers for legacy system compatibility.

Back to Guides

FTP vs FTPS vs SFTP

ProtocolEncryptionPortUse Case
FTP None 21 Legacy systems only
FTPS TLS/SSL 21 or 990 Secure FTP with certificates
SFTP SSH 22 Recommended (see SFTP guide)

Security Warning: Plain FTP transmits passwords in clear text. Use FTPS or SFTP whenever possible.

Connecting to FTP

  1. Go to Go -> Connect to FTP Server
  2. Enter connection details:
    • Host: Server hostname or IP
    • Port: Usually 21
    • Username: Your FTP username
    • Password: Your FTP password
  3. Click Connect

FTPS (Explicit TLS)

For encrypted FTP connections:

  1. Check the "Use TLS/SSL" option
  2. Select "Explicit" mode (most common)
  3. Port remains 21

FTPS (Implicit TLS)

Some servers use implicit TLS:

  1. Check "Use TLS/SSL"
  2. Select "Implicit" mode
  3. Change port to 990

Passive vs Active Mode

FTP has two data transfer modes:

Passive Mode (Default)

  • Works through firewalls and NAT
  • Recommended for most connections
  • Server opens data port, client connects

Active Mode

  • May be required by some legacy servers
  • Client opens data port, server connects back
  • Often blocked by firewalls

Captain's Deck uses passive mode by default. Switch to active mode in connection settings if needed.

Working with FTP

Once connected:

  • Navigate directories normally
  • Upload files with F5
  • Download files with F5
  • Rename with F2
  • Delete with F8

Transfer Mode: Captain's Deck automatically detects binary vs text files. Binary mode is used for all transfers to prevent corruption.

Troubleshooting

"Connection timed out"

  • Check hostname and port are correct
  • Verify FTP service is running on server
  • Check firewall allows outbound FTP

"Login incorrect"

  • Verify username and password
  • Some servers require email as username for anonymous FTP

"Unable to list directory"

  • Try switching between passive and active mode
  • Check if firewall blocks data connections

"TLS handshake failed"

  • Server certificate may be expired or self-signed
  • Try with certificate validation disabled (less secure)

Next Steps