Fixing S3 Connection Errors
When a connection fails, S3 Files shows the server's error: a code, such as Signature Does Not Match, and a sentence. Look for the code below.
After any change, check with Test Server, in the menu of the server details on iPhone and iPad and in the toolbar on a Mac. Log next to it shows every request and answer for that server.
Keys
- Invalid Access Key Id. The provider doesn't know this access key: it's mistyped, belongs to another provider or account, or was deleted or deactivated. On AWS it can also mean a region that isn't enabled.
- Signature Does Not Match. The secret doesn't match the access key, often because it belongs to an older key. Paste it again, or create a new key. Some providers also report a wrong region this way.
- Request Time Too Skewed. Your device's clock is more than a few minutes off; let it set the time automatically.
- Access Denied, or HTTP error 403. The keys are valid but not allowed this action on this bucket. On AWS, a bucket policy or your organisation's rules can deny it too.
Buckets and regions
- You need s3:ListAllMyBuckets permission to list available buckets. Consider configuring single bucket. Enter the bucket name in the server details, or allow
s3:ListAllMyBuckets. Cloudflare R2 and Backblaze B2 have messages of their own for this. - No Such Bucket. The bucket name is misspelled (names are case sensitive), the bucket was deleted, or it belongs to another account or provider.
- Permanent Redirect or Authorization Header Malformed naming another region. Set the region the message names in the server details; on AWS, S3 Files follows the redirect by itself.
- Unable to determine region for bucket, followed by its name. Pick the region yourself.
Addresses and networks
- A server with the specified hostname could not be found. The address has a typo, the name only exists on another network, such as a
.localname away from home, or the device is offline. - Local Network Access Required. Tap Open Settings and turn on Local Network for S3 Files.
- Untrusted Certificate or Certificate Mismatch. Typical for a self-hosted server: check the SHA256 fingerprint against the server and tap Trust. Never do this for a big provider like AWS, where it means something on your network is intercepting the connection.
- The request timed out or Could not connect to the server. Nothing answered at that address and port. Check the port, that the server is running, and any firewall or VPN in between.
Still stuck
IAM Identity Center sign-in errors are explained under Troubleshooting in AWS S3. For anything else, send what Log shows along with your question, as described in Further Help.