There seems to be a bug when using FORWARDED_FOR_HEADER.

I have scc-state behind a AWS ALB load balancer, which add "X-Forwarded-For" header to HTTP request to inform about the callers IP address. I added FORWARDED_FOR_HEADER="x-forwarded-for" to scc-state, and based on the logs from scc-state, it is reporting correctly the IP address of scc-worker and scc-broker processes connection to scc-state via the ALB.

But when scc-state calls getSCCBrokerClusterState, it will return an URI with brackets [] : https://github.com/SocketCluster/scc-state/blob/master/server.js#L79-L85, causing the workers to throw an parse error since ws://[10.150.34.147]:50020/socketcluster is not a valid URI.

It will only return a non-bracket (IPv4) URI if instanceIp is provided :

I'm not sure if this is considered a bug, but I expected scc-state to be able to detect what instanceIpFamily should be when using FORWARDED_FOR_HEADER.

Right now TLS/SSL is supported in scc-broker but not in scc-state.
Maybe there should be an option/environment variable in scc-state.

We try to connect from one server to state server and het this error

{ CompatibilityError: The undefined@undefined at address ::ffff:xxxxxx is incompatible with the scc-state@^6.0.3. Please, update the undefined up to version ^6.0.0

Is it possible to specify an IP as an env var, a passed argument to node server, etc to bind to for scc-state, scc-broker, etc?

I think this is what I'm looking for in scc-broker, but it doesn't seem to have a parallel in scc-state:
https://github.com/SocketCluster/scc-broker/blob/master/server.js#L9

Without binding to a specific IP, there's no way to take advantage of TUN/TAP virtual devices for encrypted networking (or preventing external access).

https://www.npmjs.com/package/scc-state

Only version 1.5.0 is present

@jondubois

Hey Jon,

Is there a reason why sc-state-server is on SC 4.3.x? Thanks!

• Nick