Repository navigation
http socket might get reset instead of normal close while handling timeout #26166
Closed as not planned
Description
- Version: v10.15.1
- Platform: Linux 0fe3a1d57e94 4.9.125-linuxkit deps: update openssl to 1.0.1j #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
- Subsystem: http,net
We were experiencing unexpected dropped connections between AWS ALB and nodejs application resulting in 502 errors from load balancer.
Managed to replicate a condition when nodejs abnormally closes socket with RST packet instead of normal FIN packets.
Here's exact conditions:
server.timeout = 10 * 1000;
server.keepAliveTimeout = 0;
We kept doing requests to the same connection every 10 seconds to trigger the condition.
Note that data was received and acknowledged, but instead of handling data or closing socket in a normal way nodejs reset the tcp connection.
Activity
thomasjungblut commentedon Feb 28, 2019
I'm currently debugging a similar issue with carbon and AWS classic ELB.
We do set the IDLE timeout on it to 60s and our keepAliveTimeout to 65s.
thomasjungblut commentedon Mar 4, 2019
any idea? I realize that node.js uses libuv underneath, maybe it would be useful to involve them as well?
mariusgrigaitis commentedon Mar 5, 2019
@thomasjungblut you might also want to check #26165
Our solution was to set the headersTimeout
0thomasjungblut commentedon Mar 17, 2019
@mariusgrigaitis so we tried that out on top of node:dubnium-jessie-slim (currently at v10.15.3)
furthermore we have a similar issue using ALBs and websockets which give us 502s in that scenario.
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.