Configure an FTPS Export Destination in QC Backup Manager
FTPS lets QCBM copy Recovery Packages to an FTP-style server over TLS. It is useful when an existing storage server supports FTPS but not SFTP. QCBM uses PHP's FTPS/FTP functions, so server TLS support, firewall rules, passive ports, credentials, and folder permissions all matter.
Off-site export requires Pro, Max, or All Access. A saved destination should be tested before you rely on it for production backups.
What You Need
Collect the FTPS host, port, username, password, and remote folder from the storage provider. QCBM defaults FTP/FTPS destinations to port 21, but you can enter a different port when the server requires one.
The Joomla server must provide PHP's FTP extension with ftp_ssl_connect() support. QCBM cannot use an FTPS destination when that function is unavailable.
Create the FTPS Destination
- Open Settings > Export Destinations and choose Add New.
- Enter a destination name and select FTPS.
- Enter the Remote host, Port, Username, Password, and Remote folder.
- Leave Use passive mode for FTP/FTPS enabled unless your FTPS server or network specifically requires active-mode behavior.
- Adjust the timeout only when necessary.
- Enable the destination and optionally make it the default.
- Save the destination.
Passive Mode and Firewalls
Passive mode is commonly required when the Joomla server is behind NAT or a firewall. In passive mode, the client opens the data connection instead of requiring the remote server to connect back to the Joomla host.
If login works but uploads or directory operations fail, check the provider's passive-port configuration and your hosting firewall before repeatedly changing credentials.
How QCBM Tests FTPS
Click Test in the destination list. QCBM opens the FTPS connection, authenticates, applies the passive-mode setting, makes sure the remote folder is reachable or can be created, uploads a small temporary file, verifies that the remote size is greater than zero, and removes the test file.
QCBM's FTPS connector uses PHP's FTP SSL API. That connector encrypts the transport, but it does not provide the same host-key pinning model used by the SFTP connector.
Run a Controlled Backup Export
After the test passes, manually export one completed Backup Set to the FTPS destination. This proves that the destination can handle QCBM's actual Recovery Package, not merely a tiny test object.
Review the export result separately from the local Backup Set. A failed FTPS transfer can leave the local Recovery Package fully usable.
Troubleshoot FTPS by Failure Type
- Could not connect: verify host, port, TLS support, firewall rules, and provider availability.
- Authentication failed: verify the saved username and password.
- Folder or upload failure: verify the remote path and write/create permissions.
- Intermittent data connection failure: review passive mode and the server's passive-port/firewall configuration.
Re-run the destination Test after correcting the specific problem, then repeat a controlled manual export.
Community Discussion
Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.