Timeout on Heroku for /lifecycle requests
See original GitHub issueHello! I have lighthouse-ci server deployed to Heroku, following exactly the recipe described in the docs.
It has been running fine since last year, but recently we have been experiencing request timeouts for /lifecycle
endpoint. Heroku has the 30 seconds request timeout (which is not configurable), do you have any ideas on how to workaround this issue?
PS: We are using version 0.6.1
Thanks in advance!
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Request Timeout | Heroku Dev Center
If the server keeps the connection open for 55 seconds without sending any data, you'll see a request timeout.
Read more >Setting request timeout (services) | Cloud Run Documentation
For Cloud Run services, the request timeout setting specifies the time within which a response must be returned by services deployed to Cloud...
Read more >Direct Uploads to S3 - Shrine
If your request workers have a timeout configured or you're using Heroku, uploading large files to S3 or any external service inside the...
Read more >gunicorn config, [critical] worker timeout heroku, celery worker ...
Let's now configure Nginx to pass web requests to that socket by making some small additions to its configuration file. Begin by creating...
Read more >What is request queue time, and why is it so important?
Web request lifecycle; Web request metrics; Why is request queue time so ... resulting in the dreaded H12 Request Timeout errors on Heroku....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI improved debug logging should be shipped and can be enabled by setting environment flag
DEBUG=lhci:*
Hi @patrickhulce! Unfortunately this has happened again today (when merged to master a commit adding one more page to track on Lighthouse-ci, if that helps). Here are the logs, let us know if you need more information or anything else to help solve this.
Logs