2 years ago
It seems like currently health checks only works between deployments.
But when the container sleeps, it doesn't check the container health before serving the request, and the current behavior is displaying an error page.
3 Replies
2 years ago
This is what i get when the container is sleeping and I send a request.
After a while, it's normal again
My container takes a while to be ready for serving.
2 years ago
This is correct, the health check isn't checked when a container wakes, instead there is a TCP probe that waits until your app accepts the connection, this is done so that the same logic can be used with database services.
However, there is currently a flaw with that on the V2 runtime that results in the first page being an error.
You can either switch back to the legacy runtime or disable app sleeping.
a year ago
Hello,
We've resolved an issue where apps with longer startup times were showing 502 errors. Apps now have up to 10 seconds to start accepting traffic, thus preventing these error pages from appearing.
You will need to trigger a deployment so that the changes we have made take effect.