prerender: 'NoSuchKey' S3 cache errors

Deployed a self hosted version of prerender to Heroku with S3 HTML cache enabled. Whenever I try hitting the server with a URL for it to cache, this is what shows up in the logs.

{ [NoSuchKey: The specified key does not exist.] 
Mar 10 00:43:47 webablerender app/web.1:  2016-03-10T08:43:47.233Z got 504 in 817ms for favicon.ico 
Mar 10 00:43:47 webablerender app/web.1:    message: 'The specified key does not exist.', 
Mar 10 00:43:47 webablerender app/web.1:    code: 'NoSuchKey', 
Mar 10 00:43:47 webablerender app/web.1:    region: null, 
Mar 10 00:43:47 webablerender app/web.1:    time: Thu Mar 10 2016 08:43:46 GMT+0000 (UTC), 
Mar 10 00:43:47 webablerender app/web.1:    requestId: '7358796100DAD80A', 
Mar 10 00:43:47 webablerender app/web.1:    extendedRequestId: 'xuIBXUU9Yc+BSBnU/Fi9gvxgsE0fhutWF36mDJ1OPgveH2HW+VI8rqClY2L2ZTHq', 
Mar 10 00:43:47 webablerender app/web.1:    statusCode: 404, 
Mar 10 00:43:47 webablerender app/web.1:    retryable: false, 
Mar 10 00:43:47 webablerender app/web.1:    retryDelay: 65.99937928840518 }

The page does render in the browser but due to it not caching the page, bigger pages time out when debugging a URL with Facebook’s Open Graph Debugger.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 32 (17 by maintainers)

Most upvoted comments

Yeah that’s really weird. Let me look more into this and get back to everyone.

+10

thoop on Apr 21, 2016

Yes @thoop ! We also use the pretender status codes in our web application…

laurent-le-graverend on Jul 11, 2016

@thoop Getting the same problem here - I dont think its an S3 permissions issue, I don’t think that the afterPhantomRequest event is firing. If I put a console.log as the very first line in that event it never gets outputted, yet the call to the lib/server.js ~ line 444 is being made. I think that the response is being sent before the event gets to fire.

ngr79 on May 17, 2016