@colyseus/proxy sees undefined nodes in Redis when running cluster in Docker on

[luismariotti1]

Hi everyone,

I'm having trouble setting up a Colyseus cluster with Docker on WSL2. My goal is to use @colyseus/proxy to load balance between multiple nodes, but the nodes are registering themselves with an undefined address in Redis. This prevents the proxy from being able to route traffic correctly.

I suspect this is a networking issue related to how a Colyseus node inside a Docker container on WSL2 determines its public address.

[endel]

HI @luismariotti1, you can provide the SELF_HOSTNAME and SELF_PORT environment variables for each instance manually if these values are being undefined.

It is important to note the @colyseus/proxy is considered discontinued and since version 0.16 and moving forward it is recommended to make each Node.js process accessible via publicAddress instead.

See https://docs.colyseus.io/deployment/scalability#make-each-colyseus-process-publicly-accessible