I’ve noticed that web service no longer wakes up when receiving an HTTP POST request, even though this used to work reliably for months, including on the free tier. It was functioning as expected until just a couple of days ago.
The cold start now seems to be triggered only by a GET request (e.g. visiting the URL manually). Any POST request sent while the service is asleep has no effect, and the container doesn’t wake up.
Restarting or redeploying the service temporarily restores the expected behavior, but the issue returns after the first sleep.
I’ve seen this issue mentioned in older posts from previous years, but it seems to have resurfaced now.
Has there been a recent change in how cold start triggers are handled on the free tier?
Hi,
I am also facing the same issue. My website is hosted on freetier, when i login it gived me a bad request network error, when i clear cache and redeploy my server the issue gets fixed and i can use my website successfully, but then this issue happens again after 20-30 minutes. Although i have been working on it since 1 month didnt face this issue but just from couple past days i am facing this issue of coldstart now.
I have written a complaint request but no reply i got from there.
I can confirm this. I’m one of the people who made a post about this exact issue a while back.The problem has resurfaced. It’s been going on for the past few days. In short, everything works as expected after a fresh deploy, but after the web service spins down, it only wakes up with GET requests..