Node.js stream error proxy versus origin split response

When this happens

Use this when a cdn, load balancer, reverse proxy, or waf sits in front of the service. Do not stop at the screen message; validate whether the edge/proxy or the origin server creates the failure first.

Symptom checklist

• stream error appears repeatedly in the Node.js UI or logs.
• process env, npm tree, memory, port, module type differs between successful and failed requests.
• The issue appears only after separating Node runtime error from package dependency issue.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• stream error specifically changes the investigation surface for Node.js: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• Another process already listens on the configured port.
• A stream emits error or backpressure without an error handler.
• Worker threads or cluster workers exit without propagating the root error.
• The process manager restarts quickly and hides the first stack trace.
• Environment variables differ between shell, service, and container runtime.
• For the proxy versus origin split case, the first useful clue is whether the edge/proxy or the origin server creates the failure.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare process env, npm tree, memory, port, module type for success and failure in the same window.
3. Test the hypothesis: Node.js runtime failure caused by occupied port, stream backpressure, worker lifecycle, unhandled error event, or process manager restart loop.
4. Classify this as proxy versus origin split: whether the edge/proxy or the origin server creates the failure.
5. Capture current values before changing configuration.

First evidence

Treat stream error as a proxy versus origin split case. First collect evidence for whether the edge/proxy or the origin server creates the failure.

Output examples

Normal output

Direct origin and routed proxy return equivalent status and headers.

Failing output

Origin succeeds but proxy fails, or proxy succeeds while direct origin exposes the real backend error.

Output-to-action branches

• A CDN, load balancer, reverse proxy, or WAF sits in front of the service.
  Test direct origin and routed traffic separately, then change only the layer that differs.
• The working and failing outputs differ.
  Act on the differing layer first: For stream error, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not assume the CDN error code is the application root cause.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "stream error" ./logs

node --trace-warnings server.js

npm ls

lsof -i :3000

grep -R "stream error" src logs

lsof -i :3000 || netstat -ano | findstr :3000

node --trace-warnings server.js

grep -R "EADDRINUSE\|stream\|worker\|unhandled" ./logs src

npm ls

curl -Iv https://example.com --resolve example.com:443:ORIGIN_IP

Fix order

1. Record the full stream error message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for Node.js runtime failure caused by occupied port, stream backpressure, worker lifecycle, unhandled error event, or process manager restart loop.
3. Compare the failing case with a successful case before editing settings.
4. If this is the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For stream error, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Find the listener on the port before changing application code.
• Add error, close, and backpressure handling around streams.
• Log worker exit codes and messages at the parent process.
• Read the first crash in process manager logs.
• Print effective runtime environment during startup.
• For the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.

Evidence links

• Node.js errors official
• Node.js diagnostics official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Node.js stream error.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change Node runtime error from package dependency issue results.
• Do not trust only the Node.js UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for process env, npm tree, memory, port, module type.
• Add npm dedupe, ESM/CJS alignment, heap tuning, port cleanup to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Node.js ECONNRESET first triage response
• Node.js EADDRINUSE first triage response
• Node.js MODULE_NOT_FOUND first triage response
• Node.js ERR_REQUIRE_ESM first triage response
• Node.js heap out of memory first triage response
• Node.js npm peer dependency first triage response
• Node.js fetch failed first triage response
• Node.js timeout first triage response