I have been trying out the free tier of Web Services and I have a Node application that uses Socket.io. However, I am having a problem that my websocket connection automatically gets closed exactly after 5 minutes of inactivity.
Although when I run the same server on Localhost I can stay connected for as long as I want and the connection doesn’t get automatically closed.
Is it some sort of Timeout that has been set by default on free web services? I am hesitant to upgrade to a paid tier if this problem still persists.
Our free tier services do automatically spin down after 15 minutes of inactivity. However, if you are seeing this after 5 minutes, that does seem a bit premature. Please feel free to DM me with the details of your service and we’ll be happy to take a closer look.
I seem to have the same issue, after about 5 minutes on the Free Tier (the server is active during that time) my open web sockets get closed. I just transferred my app from Heroku and I didn’t see this issue over there so I’m sure it’s not my code/application.
We have confirmed there is an open issue that causes long-running connections, such as websockets, to timeout on the free tier. We will update this thread once this limitation has been resolved. Very sorry for the trouble here!