Docs Ordnary Web Services Ordnary R2
S3 API errors
The error responses the S3 API returns, what each one means, and the request ID to quote when you contact support.
Errors come back the way S3 tools expect them: an HTTP status and an XML body with a Code, a Message, a RequestId and a HostId. SDKs surface the code as the exception's name.
<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>AccessDenied</Code>
<Message>Anonymous requests are not supported. Include an Authorization header signed with your Ordnary R2 access key.</Message>
<RequestId>65EAD26C1F0B</RequestId>
<HostId>s3.ordnary.com</HostId>
</Error>Codes
| Code | Status | Meaning | What to do |
|---|---|---|---|
| AccessDenied | 403 | No Authorization header, or the key may not use this bucket. | Sign the request with your access key. See Authentication. |
| InvalidAccessKeyId | 403 | Unknown access key ID. | Generate the key again in the console and update your tool. |
| SignatureDoesNotMatch | 403 | The signature was made with another secret, endpoint or addressing style. | Check the secret, the endpoint and path-style addressing. |
| InvalidArgument | 400 | No bucket in the request path. | Use path-style requests. See Path-style requests. |
| EntityTooLarge | 413 | The request body is over 100 MB. | Use multipart upload, or the console's Large file uploads. |
| NotImplemented | 501 | Chunked streaming signing was used. | Sign the whole payload, or send it unsigned over HTTPS. |
| NoSuchBucket | 404 | No bucket with that name in your account. | Check the name; buckets are per account. |
| NoSuchKey | 404 | No object at that key. | Check the key, including the prefix. |
Contacting support
Quote the RequestId from the error and the time of the request. With those we can find the request on our side. Never include your secret access key in a ticket.