Troubleshooting
Find the symptom below, then try the suggested checks. Detailed behavior and limits are in the user guide.
I cannot connect or see my bucket
Check the bucket region, AccessKey pair and any STS token expiry. If your identity cannot list all buckets, specify the bucket in advanced options. Confirm that your RAM policy permits the requested operation. Internal and PrivateLink endpoints require an appropriate network; CNAME and PrivateLink also require a bucket and an HTTPS endpoint.
My search does not find a file
Search matches a remote key prefix, not arbitrary text inside a filename or file contents. Open the correct folder, check the prefix and load more results. Sorting only rearranges loaded rows.
A transfer stopped after closing the app
Reconnect with the same profile and AccessKey ID, then retry the restored entry in Transfers. Transfers never restart automatically. Valid checkpoints are reused; if the source changed, follow the recovery prompt. Copy, move and delete queues are session-only. Cancellation retains checkpoints and unfinished multipart parts; clean up abandoned remote parts through OSS lifecycle rules or the console.
A download fails or runs out of disk space
Choose a writable local folder and allow space for both the partial download and the temporary publication copy. Reserved names, case collisions and symlinked subdirectories are rejected. Check the failed item for the exact cause. If an older record cannot safely resolve its destination, create a new download task.
A file cannot be previewed or edited
Text editing supports UTF-8 files up to 5 MiB. Preview reads are capped at 8 MiB and decoded images at 20 megapixels. Documents, FLV and unsupported codecs use external-open or download fallback. Download the file to work with a local application when preview is unavailable.
A share link has expired or cannot be opened
Generate another link and check the selected host and expiry. Known STS expiry caps a signed link’s lifetime; public links require public access. Do not change an object to public solely to work around a failed private link. Anyone holding a valid signed URL can exercise its access.
Settings or saved credentials are unavailable
Credentials stay in memory by default. Saving them requires the operating system keyring; unlock or enable that service, or connect without saving. Invalid settings files are preserved and writes are blocked: back up the file, repair it and reload. See Settings for the storage location.
How do I report a problem?
Include the app version from About, your OS and architecture, steps to reproduce, expected and actual results, and a redacted error or screenshot. Local diagnostic logs are opt-in. Remove AccessKeys, tokens, authorization codes, SMTP passwords and signed URLs. Submit an issue on GitHub.