Troubleshoot Storage Roots and Provider Connectivity
This article shows how to use provider tests and exact-root reasoning to distinguish credential, network, trust/OAuth, root, permissions and connector-specific failures.
What you need to know
- Each Storage Connection represents one provider and one exact root. QCSB normalizes paths and refuses navigation/operations outside that boundary.
- Allow access to subdirectories controls depth below the root; it never exposes or infers parent directories above the root.
- Basic includes Local storage and the first active Workspace. Pro adds FTP/SFTP, multiple Workspaces, advanced permissions, and background continuation. Max/All Access adds Google Drive, OneDrive, Private Connections, Recovery Vault management, and bulk operations.
- A plan gate decides whether a feature exists at the current Effective tier. Joomla access and QCSB permission rules separately decide whether a particular user may use that feature.
Troubleshooting procedure
- Run Test Connection on the affected Storage Connection.
- Verify provider credentials/authorization and the exact root independently.
- Confirm Allow access to subdirectories matches the path depth the user is trying to reach.
- Check Status connector readiness and remote runtime requirements.
- Use a small safe browse/upload test before retrying a large transfer.
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.