Connect to FTPS Server with FileZilla

Secure FTP connections using SSL/TLS encryption

FTPS (FTP over SSL/TLS) adds encryption to the traditional FTP protocol, securing your username, password, and data during transfer. FileZilla fully supports both explicit and implicit FTPS connections. This guide covers everything you need to connect securely.

FTPS vs SFTP vs FTP

🔐 FTPS (This Guide)

FTP + SSL/TLS encryption

  • Ports: 21 (explicit) or 990 (implicit)
  • Security: Encrypted with SSL/TLS certificates
  • Use case: Legacy FTP servers with added security

🔒 SFTP (Recommended)

SSH File Transfer Protocol

  • Port: 22
  • Security: SSH encryption (very secure)
  • Use case: Modern, most secure option
→ Learn about SFTP

âš ī¸ FTP (Not Secure)

Plain FTP without encryption

  • Port: 21
  • Security: None - all data sent in plain text
  • Use case: Only when FTPS/SFTP unavailable
→ Plain FTP guide

What You Need

Your hosting provider should give you these FTPS credentials:

1.
Server Address (Host)

Examples: ftps.yoursite.com,ftp.yoursite.com

2.
Username

Your FTPS account username

3.
Password

Your FTPS account password

4.
FTPS Type

Explicit FTPS (port 21, most common) or Implicit FTPS (port 990, legacy)

Explicit vs Implicit FTPS

✓ Explicit FTPS (Recommended)

Also called FTPS Explicit or AUTH TLS

How it works:

  • Starts as plain FTP on port 21
  • Client requests encryption with "AUTH TLS" command
  • Connection upgrades to encrypted

Advantages:

  • More compatible with firewalls
  • Standard port 21 (no special config needed)
  • Most widely used modern approach

âš ī¸ Implicit FTPS (Legacy)

Also called FTPS Implicit or FTP-SSL

How it works:

  • Encrypted from the start on port 990
  • No negotiation - encryption required immediately

Disadvantages:

  • Non-standard port 990
  • Less firewall-friendly
  • Considered deprecated (old-style)

💡 Most servers use Explicit FTPS. Start with that unless your provider specifically says to use Implicit.

How to Connect to FTPS Server

  1. 1

    Open Site Manager

    Go to File → Site Manager (or press Ctrl+S)

  2. 2

    Create New Site

    Click New Site and give it a name (e.g., "My FTPS Server")

  3. 3

    Configure General Tab

    Protocol:

    Select FTP - File Transfer Protocol

    Host:

    Enter your server address: ftps.yoursite.com

    Port:

    â€ĸ 21 for Explicit FTPS

    â€ĸ 990 for Implicit FTPS

    âš ī¸ Encryption (IMPORTANT):

    For Explicit FTPS:

    Select Require explicit FTP over TLS

    For Implicit FTPS:

    Select Require implicit FTP over TLS

    â„šī¸ "Use explicit FTP over TLS if available" will fall back to plain FTP if server doesn't support FTPS. Use "Require" for better security.

    Logon Type:

    Select Normal

    User:

    Enter your FTPS username

    Password:

    Enter your FTPS password

  4. 4

    Connect

    Click Connect

  5. 5

    Handle Certificate Warning

    You'll likely see an "Unknown certificate" dialog:

    Review the certificate:

    • Check that the hostname matches your server
    • Verify the certificate isn't expired
    • If it's a self-signed cert from a trusted server, it's usually safe to proceed

    To trust this certificate:

    • Check "Always trust this certificate in future sessions"
    • Click OK

    This prevents the warning from appearing on every connection to this server.

  6. ✓

    Connected Securely!

    When successfully connected:

    • Remote files appear in the right panel
    • Message log shows "TLS connection established"
    • Lock icon appears in status bar (indicating encryption)
    • All data is now encrypted with SSL/TLS

Troubleshooting FTPS Connections

❌ Connection timed out after 20 seconds of inactivity

Solution:

  • Wrong FTPS type - try switching between Explicit and Implicit
  • Wrong port - use 21 for Explicit, 990 for Implicit
  • Firewall blocking the connection

❌ GnuTLS error -15: An unexpected TLS packet was received

Solution:

  • You're using Implicit encryption on port 21 (or Explicit on port 990)
  • Switch encryption type: Explicit ↔ Implicit
  • Verify the correct port with your hosting provider

❌ Failed to retrieve directory listing

Solution:

  • Switch to Passive mode in Transfer Settings
  • Firewall may be blocking data connections
→ Fix passive/active mode issues

âš ī¸ Certificate verification failed

Causes:

  • Self-signed certificate (common in dev environments)
  • Hostname mismatch (connecting via IP instead of domain)
  • Expired certificate

Solution: Review the certificate details and check "Always trust" if you recognize and trust the server.

→ Complete SSL/TLS troubleshooting guide

🔐 Security Best Practices

✓

Use "Require" encryption instead of "if available" to prevent fallback to plain FTP

✓

Verify SSL certificates before trusting them, especially in production

✓

Use strong passwords for your FTPS accounts

✓

Keep FileZilla updated for the latest security patches

💡

Consider SFTP instead if available - it's generally more secure and easier to configure

→ Complete security guide

✓ Connected Successfully?

Frequently Asked Questions

What is the difference between FTPS and SFTP?

FTPS is FTP with SSL/TLS encryption (uses ports 21/990), while SFTP is SSH File Transfer Protocol (uses port 22). SFTP is generally considered more secure and modern. They are completely different protocols despite similar names.

Which port does FTPS use?

Explicit FTPS uses port 21 (same as FTP), while Implicit FTPS uses port 990. Most modern servers use Explicit FTPS on port 21.

Why do I get a certificate warning?

This happens when the server uses a self-signed certificate or the certificate doesn't match the hostname. You can review and accept the certificate if you trust the server. For production environments, use proper SSL certificates.

Is FTPS more secure than FTP?

Yes! FTPS encrypts all data including credentials using SSL/TLS, while plain FTP sends everything unencrypted. However, SFTP is generally preferred over FTPS in modern setups.

;