Default 404 object storage rendering on custom 404.html page

I've set our 404 page to render a custom html file.
However, for some reason, the old 404 text still renders at the bottom of the page.
This doesn't happen all the time but every now and then.

Is this a bug in Object Storage or is there a setting I need to configure?

The error displayed is:

HTTP/1.1 404 Not Found Content-Length: 272 x-amz-request-id: tx00000000000000139e3d8-006087909c-2fc5e60-default Accept-Ranges: bytes     Content-Type: text/html Date: Tue, 27 Apr 2021 04:18:36 GMT Connection: close
404 Not Found

Code: NoSuchKey
BucketName: dxp-website
RequestId: tx00000000000000139e3d8-006087909c-2fc5e60-default
HostId: 2fc5e60-default-default

Command used:

s3cmd ws-create --ws-index=index.html --ws-error=404.html s3://$LINODE_OBJECT_STORAGE_BUCKET   


1 Reply

Linode Staff

Is this still happening for you? I was unable to duplicate what you're seeing, so I think this may have been a case of the cache within your local browser serving old content.

The way I checked this was in both regular and private sessions on Chrome, Firefox, Safari, and Opera.


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct