Skip to main content

Connecting FTP

This guide walks you through connecting an FTP storage destination to Pluton.

Prerequisites​

Before connecting FTP, you need:

  1. An FTP server accessible from your Pluton instance (must support passive mode)
  2. FTP credentials (username and password) with read/write access to the target directory
  3. The FTP server hostname or IP address

Getting Your FTP Credentials​

FTP credentials are typically provided by your hosting provider or system administrator. If you manage your own FTP server, here's how to gather the required information:

Step 1: Identify Your FTP Server Details​

  1. Note the hostname or IP address of your FTP server (e.g., ftp.example.com)
  2. Confirm the port — the default is 21 for standard FTP, or 990 for implicit FTPS
  3. Verify the server supports passive mode, which is required for Pluton

Step 2: Create or Verify FTP User​

  1. Log into your FTP server's admin panel or connect via SSH
  2. Create a dedicated FTP user for backups (recommended for security)
  3. Assign the user read/write permissions to the directory where backups will be stored
  4. Test your credentials using an FTP client (e.g., FileZilla) to confirm access
tip

For anonymous FTP access, use anonymous as the username and leave the password blank. However, this is not recommended for backup storage due to security concerns.

Connecting to Pluton​

Step 1: Add Storage​

  1. In Pluton, navigate to Storages
  2. Click Add Storage button
  3. Select FTP from the provider list

Step 2: Configure Connection​

Fill in the required fields:

  • Storage Name: A friendly name (e.g., "Office FTP Backups")
  • FTP Host: The hostname or IP address of your FTP server (e.g., ftp.example.com)
  • FTP Username: Your FTP username
  • FTP Password: Your FTP password
  • FTP Port: The port your FTP server listens on (default: 21)

Step 3: Advanced Options (Optional)​

Additional settings available:

  • Use Implicit FTPS: Enable if your server uses FTP over TLS on port 990. This encrypts the entire connection from the start.
  • Use Explicit FTPS: Enable if your server supports explicit TLS. The client requests TLS security after connecting on the standard port.
  • Do Not Verify TLS Certificate: Skip TLS certificate verification. Useful for self-signed certificates, but reduces security.
  • Max FTP Simultaneous Connections: Limit the number of concurrent FTP connections (default: 0 for unlimited). Some servers impose connection limits — set this to match your server's policy.
  • Disable EPSV: Disable Extended Passive Mode. Enable this if you experience connection issues behind certain firewalls or NAT configurations.
  • Disable MLSD: Disable the MLSD command for directory listings. Enable this for older FTP servers that don't support it.
  • Disable UTF-8: Disable UTF-8 encoding for file names. Use this if your server has issues with non-ASCII characters.
  • Use MDTM: Enable the MDTM command for setting modification times. Required as a workaround for VsFTPd servers.
  • Force Listing Hidden Files: Force the server to list hidden files (those starting with a dot).
  • Idle Connection Timeout: Time before idle connections are closed (default: 1m0s).

Step 4: Test and Save​

  1. Click Test Connection to verify credentials
  2. If successful, click Save
  3. Your FTP storage is now ready for backup plans

Using FTPS (FTP over TLS)​

FTP transmits data in plain text by default. For secure connections, Pluton supports two FTPS modes:

Implicit FTPS​

  • The entire session is encrypted from the start
  • Typically runs on port 990
  • Enable the Use Implicit FTPS option and set the port to 990

Explicit FTPS​

  • Starts as a regular FTP connection on port 21, then upgrades to TLS
  • More widely supported than implicit FTPS
  • Enable the Use Explicit FTPS option
caution

Do not enable both Use Implicit FTPS and Use Explicit FTPS at the same time. Choose one based on your server's configuration.

Common Issues​

Connection Timeout: Ensure your FTP server is reachable from the Pluton instance. Check firewalls, security groups, and that the correct port is open. FTP passive mode requires additional port ranges to be open — consult your server's documentation.

Authentication Failure: Double-check your username and password. Some FTP servers are case-sensitive for usernames. Verify the account is active and has not expired.

TLS/SSL Errors: If using FTPS with a self-signed certificate, enable Do Not Verify TLS Certificate. For production environments, use a valid certificate instead.

Directory Listing Fails: Try enabling Disable MLSD if your server doesn't support the MLSD command. Older servers may require this option.

Passive Mode Issues: If connections stall during data transfer, try enabling Disable EPSV to fall back to standard passive mode. Also verify that your server's passive port range is accessible.

File Name Encoding Issues: If file names appear garbled, try enabling Disable UTF-8 to fall back to the server's default encoding.

Best Practices​

  • Always use FTPS (implicit or explicit) to encrypt data in transit
  • Create a dedicated FTP user for Pluton with access limited to the backup directory
  • Set a connection limit (Max FTP Simultaneous Connections) to avoid overloading your FTP server
  • Use a strong password and change it periodically
  • Monitor available disk space on your FTP server to prevent backup failures
  • Test your FTP connection after any server configuration changes