Ordnary

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.

3 min readIntermediate

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.

Error response
<?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

CodeStatusMeaningWhat to do
AccessDenied403No Authorization header, or the key may not use this bucket.Sign the request with your access key. See Authentication.
InvalidAccessKeyId403Unknown access key ID.Generate the key again in the console and update your tool.
SignatureDoesNotMatch403The signature was made with another secret, endpoint or addressing style.Check the secret, the endpoint and path-style addressing.
InvalidArgument400No bucket in the request path.Use path-style requests. See Path-style requests.
EntityTooLarge413The request body is over 100 MB.Use multipart upload, or the console's Large file uploads.
NotImplemented501Chunked streaming signing was used.Sign the whole payload, or send it unsigned over HTTPS.
NoSuchBucket404No bucket with that name in your account.Check the name; buckets are per account.
NoSuchKey404No 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.

Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.