Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.

See original GitHub issue

Running lhci server on k8s using patrickhulce/lhci-server image. When a pod restart occurs, a RangeError for the port is raised and the pod cannot be started successfully.

Issue Analytics

State:
Created 3 years ago
Comments:14 (3 by maintainers)

Top GitHub Comments

2reactions

patrickhulcecommented, Apr 14, 2020

@MahmoudDolah well something in the chain is setting the port to an invalid number. https://github.com/GoogleChrome/lighthouse-ci/pull/270 should add more debug information to help track it down.

0reactions

annezcommented, May 26, 2020

Okay I have found out the issue here @patrickhulce. The system documented in Kubernetes doesn’t take into account a deployment or a service being attached (this is how we would set up a Kube system). In the situation of an lhci server we would define:

A deployment with LHCI container
A service linking to the LHCI container
An ingress connected to such service

In the kubernetes world, a service linked to a deployment automatically creates SERVICE_PORT and SERVICE_HOST ENV vars. This means if your service is named lhci then the env vars filtered down are LHCI_PORT=tcp://.... This is the issue people are encountering above.

Should we amend the documentation to highlight this clash?

Top Results From Across the Web

Port should be >= 0 and < 65536. Received NaN - Stack ...

Anyone help me in resolving this error. ` WARNING: Adonis has detected an unhandled promise rejection, which may cause undesired behavior in ...

Port should be >= 0 and < 65536. Received - Glitch Support

RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received . ... I get this error, and idk what to do.

Port should be >= 0 and < 65536. Received NaN-mongodb

Coding example for the question RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN-mongodb.

Solved Can't start after update nodejs/npm - NodeBB

Received NaN. at validatePort (internal/validators.js:211:11) at ... RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536.

T205505 process.env.PORT not defined

port ); ^ RangeError [ERR_SOCKET_BAD_PORT]: Port should be > 0 and < 65536. Received NaN. Clearly the javascript var port = parseInt(process.env.PORT, 10)...