Socket.io connection drops and reconnects every 5 minutes

1

I am trying the free plan and I know it goes down after 15 minutes. But while doing this tests the service is staying up, but the socket connections drop after 5 minutes.
Is this a limitation from the free plan, or something else may be happening?

PS: It happens every 5 minutes from the connection and it ignores if packets are been sent.

Aug 12 03:47:28 PM  Connected to DBJ2 / HOST
Aug 12 03:52:28 PM  Client disconnected from DBJ2 / HOST >> transport close
Aug 12 03:52:31 PM  Connected to DBJ2 / HOST
Aug 12 03:57:32 PM  Client disconnected from DBJ2 / HOST >> transport close
Aug 12 03:57:36 PM  Connected to DBJ2 / HOST
Aug 12 04:02:36 PM  Client disconnected from DBJ2 / HOST >> transport close
Aug 12 04:02:40 PM  Connected to DBJ2 / HOST
Aug 12 04:07:40 PM  Client disconnected from DBJ2 / HOST >> transport close
Aug 12 04:07:44 PM  Connected to DBJ2 / HOST
2

Hey Mike,

This isn’t a limitation that I’m aware of. Do you have a reproducible example I can use to investigate this further?

3

I’ll try to put together an example on a git repository and post it here.

1 Like
4

I got it to happen again with a very basic and plain example:

Aug 15 01:53:15 PM  ==> Starting service with 'node src/main.js'
Aug 15 01:53:17 PM  Listening on PORT 10000
Aug 15 01:54:16 PM  Client connected
Aug 15 01:54:17 PM  Ping received
Aug 15 01:54:28 PM  Client disconnected transport close
Aug 15 01:54:30 PM  Client connected
Aug 15 01:54:30 PM  Ping received
Aug 15 01:55:00 PM  Ping received
Aug 15 01:55:30 PM  Ping received
Aug 15 01:56:00 PM  Ping received
Aug 15 01:56:30 PM  Ping received
Aug 15 01:57:00 PM  Ping received
Aug 15 01:57:30 PM  Ping received
Aug 15 01:58:00 PM  Ping received
Aug 15 01:58:30 PM  Ping received
Aug 15 01:59:00 PM  Ping received
Aug 15 01:59:30 PM  Client disconnected transport close
Aug 15 01:59:33 PM  Client connected
Aug 15 01:59:33 PM  Ping received
Aug 15 02:00:00 PM  Ping received
Aug 15 02:00:03 PM  Ping received

As you can see 5 minutes after the 1:54:30 connection it disconnects and connects back.

The code is in this Github repo. GitHub - MrAmericanMike/socketeer

5

Thanks for sharing this. I’ll investigate and get back to you.

1 Like
6

I believe this is related to how we configure free tier services. I’m checking if we can change the setting.

1 Like
7

Any update or workaround?

8

We have an internal issue tracking this, but we don’t currently have an ETA. This is a limitation specific to the free tier, so currently the only workaround is to upgrade to the paid tier.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.