Troubleshoot QCSB FTP Connections

This article shows how to diagnose DNS/host, port, credentials, TLS, passive-mode, exact-root, firewall, and provider permission failures using the QCSB test result rather than exposing secrets.

Troubleshooting procedure

  1. Verify host, port, username, password, exact root, and the FTP Security setting.
  2. Keep passive mode enabled unless the provider requires active mode; firewall/NAT issues commonly appear as successful login followed by failed listing/transfer.
  3. If FTP over TLS fails, confirm the server actually supports explicit TLS on the configured port and its certificate/FTP configuration is valid.
  4. Use QCSB Test Connection, then try a small listing and upload/download inside the exact root.
  5. When confidentiality matters, migrate the endpoint to SFTP instead of weakening unrelated QCSB security controls.

Verify the result

  • Test Connection succeeds.
  • The displayed/usable root is exactly the intended root and no parent folder is reachable.
  • A normal authorized user can perform only the operations intended for that connection/Workspace role.

Important limits and mistakes to avoid

  • Never broaden a connection root merely to work around a permission or provider error; fix the actual root/credential/hosting problem.

If it still fails

  • Change one variable at a time and repeat the same small test after each correction.
  • Use QCSB sanitized errors/Status/Test Connection before changing unrelated provider or Joomla settings.
  • If the issue remains, collect version, provider type, Workspace/user role, task state where relevant, and sanitized messages for support. Never include secrets.

Community Discussion

For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.