You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should not be possible... looks like a node core bug to me
RangeError [ERR_OUT_OF_RANGE]: The value of "msecs" is out of range. It must be a non-negative finite number. Received NaN
at getTimerDuration (node:internal/timers:425:11)
at TLSSocket.setStreamTimeout [as setTimeout] (node:internal/stream_base_commons:243:11)
at resOnFinish (node:_http_server:1032:14)
at ServerResponse.emit (node:events:508:28)
at onFinish (node:_http_outgoing:1024:10)
at callback (node:internal/streams/writable:764:21)
at afterWrite (node:internal/streams/writable:708:5)
at onwrite (node:internal/streams/writable:686:7)
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:105:10)
Activity
ronag commentedon Sep 5, 2025
@haramj
ronag commentedon Sep 6, 2025
I think this might be related to http2 to http1 fallback. @nodejs/http2 Not sure I quite follow the logic yet...
ronag commentedon Sep 6, 2025
Found what causes this:
haramj commentedon Sep 6, 2025
@ronag
I recently opened PR #59243 (
http: add server.keepAliveTimeoutBuffer option),which touches a similar area of the HTTP keep-alive handling.
I thought this issue might be related to
keepAliveTimeout/keepAliveTimeoutBufferbeing leftundefinedwhen falling back from HTTP/2 to HTTP/1.I now see that follow-up PRs (#59773, #59784) are already in progress to fix this.
Sorry for the noise..
trivikr commentedon May 20, 2026
Closing as this issue was fixed in #59784