Troubleshoot Local Storage Paths, Permissions, and Writability

This article shows how to diagnose nonexistent roots, host filesystem permissions, read-only paths, ownership problems, and web-server limitations while keeping the configured exact-root boundary intact.

What you need to know

  • An explicit deny wins over allow, and no applicable allow means denied.
  • Frontend button visibility is only guidance. QCSB rechecks authorization server-side and rejects forged Workspace/location/item references.

Troubleshooting procedure

  1. Confirm the configured exact root exists on the Joomla server and is the intended path.
  2. Check the web/PHP user can read the root and can write/create/delete only where the Workspace role requires write operations.
  3. Verify host ownership/permissions and open_basedir or other hosting restrictions are not blocking the directory.
  4. Use Test Connection, then test a small create/upload from a normal Workspace account.
  5. Do not fix permission errors by broadening the exact root to a parent directory containing unrelated site files.

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

  • A successful Super User test does not prove a normal Joomla group has correct Workspace access. Test with the real role.

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.