Troubleshoot QCSB SFTP Connections

This article shows how to diagnose SSH reachability, port, username, password/key/passphrase, host-key mismatch, exact-root, and server permission problems while preserving trust checks.

Troubleshooting procedure

  1. Verify host, port, username, exact root, and the selected authentication type.
  2. For password auth, confirm the account permits password authentication. For private-key auth, verify the complete key and passphrase.
  3. Review host-key trust. A changed fingerprint is a security event; verify the server independently before accepting the new key.
  4. Confirm the SFTP account can list/write/delete the exact root according to the operations you intend to allow.
  5. Run Test Connection, then repeat the failing operation with the smallest safe test item and read the sanitized error message.

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.