Socket hang up

[webberwang]

Description of Bug

• Socket hang up error with Node 20 on second request graffle-js/graffle#1057

---

On many seed requests for e2e https://app.circleci.com/pipelines/github/codelab-app/platform/14201/workflows/7530dc16-b91d-478d-ae91-b5afd06874d3/jobs/50922/parallel-runs/0/steps/0-114, we're getting

Failed to proxy ****************:***********/app/seed-cypress-app [Error: socket hang up] { code: 'ECONNRESET' }
[WebServer] [Error: socket hang up] { code: 'ECONNRESET' }
Server response: Internal Server Error

• Socket Hang Up / ECONNRESET / ECONNREFUSED on consecutive http requests (>= 100) and temporary FIX nodejs/node#55330
• "socket hang up" / ECONNRESET on consecutive requests with Node.js 19 and Node.js 20 node-fetch/node-fetch#1735
• FetchError: request to http://0.0.0.0:8000/graphql failed, reason: socket hang up remix-run/remix#4414

---

In Node.js 20 and 22, the connection reuse policy became stricter, which led to more “socket hang up” errors. The main reason for this change is better performance, resource management, and compliance with modern networking standards.

• [NEXT-1314] High memory usage in deployed Next.js project vercel/next.js#49929

---

• It seems we can supply custom fetch in graphql client to set keepAlive to true from false.
• Thought it was playwright request timeout
• Might be nextjx proxy timeout
• [next.config.js] rewrites be able to change the proxyTimeout vercel/next.js#36598

---

• https://nextjs.org/docs/app/api-reference/cli/next#configuring-a-timeout-for-downstream-proxies

---

• need to set in multiple places

1. Next.js nx project.json
2. Next.js config proxy
3. Nest.js main.ts
4. Nest.js fetch agent (headers maybe?)

---

Thought this was resolved

• High Proxy Timeout causes the server to hog resources vercel/next.js#62869

---

• requestTimeout and long running uploads nodejs/node#46574 (comment)
• Random HTTP 500 statuses or ECONNRESET when node-gyp fetches dependencies nodejs/node-gyp#2847
• ECONNRESET while doing http 1.1 keep alive requests and server closes the connections nodejs/node#47130
• Enable debug information for fetch() via NODE_DEBUG=http nodejs/undici#2191
• HTTP Keep-alive, "socket hang up" ECONNERR on a long-running second request axios/axios#6113

---

On local dev, when setting the keep-alive in controller before return, we do get the same in frontend client

[vladyslav-polishchuk]

via Hubstaff
User: Vladyslav Polishchuk

Project: platform - https://app.hubstaff.com/projects/2961404
Date Range: 02/26/25 - 03/05/25
Work session total: 16:29:37
Billable: Yes

Grand total: 16:29:37