Open matesio opened 6 years ago
I am unable to reproduce this, can you send exact URL to support@prerender.cloud
also, was there a more interesting error message in the Cloudwatch logs?
Done, please check your mail.
We are facing this same issue, with a fair degree of regularity. Sometimes it works, sometimes it doesn't. No changes to code or request... Our users randomly get this error.
Can you send an email to support@prerender.cloud with a few URLs I can investigate? I'll get it resolved within 48 hours.
hello @hephalump, in our case there were few failed calls which was very hectic to figure out. Same can be your case, check your logs for failed calls.
@matesio I've checked the logs but don't see any failed calls. I'm wondering if this is a Lambda cold-start or Lambda@Edge with VPC issue - we've had Lambda containers take >15 seconds to load and execute on first invoke after going cold, and the behaviour we're experiencing is consistent with cold start behaviour... We know how to solve it in our region, not sure how to solve it @Edge.
@hephalump did you see my email responses to your email?
@hephalump same was in our case and finally had to remove lambda@edge from our production system because it was taking much time load even failing few calls.
@jotto yes, responded to you.
@matesio we found an error in our logs
I have deployed your lambda function with cloudfront distribution but when i try to pass query string it gives me error 502 lambda function invalid URI format.
Url: cloudforntdist.cloudfront.net/search?q=&subtype=subtype%20type&purpose=purpose&type=type