Web interface is not connecting due to port issue

We are managing multiple CryoSPARC instances at our HPC center. After updating to version 4.7.0, we are encountering the following error:
"Error: listen EADDRINUSE: address already in use 0.0.0.0:39506"
As a result, the web interface fails to connect. We have verified that the port is not in use with netstat, but the issue persists. While a restart temporarily resolves the problem, frequent restarts are not a viable solution given the number of instances we are supporting.
Is there a recommended solution to address this issue effectively?


Error: listen EADDRINUSE: address already in use 0.0.0.0:39506
    at Server.setupListenHandle [as _listen2] (net.js:1331:16)
    at listenInCluster (net.js:1379:12)
    at doListen (net.js:1516:7)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1358:8)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '0.0.0.0',
  port: 39506
}

netstat --listen -n -p | grep 39506
shows no output.

Welcome to the forum @soottikkal.

Is port 39506 in the “ephemeral ports” range of the server?

cat /proc/sys/net/ipv4/ip_local_port_range

What is the output of the command

sudo ss -anp | grep 39506 | sed 's/\s\+/ /g'

32768 60999
We have one instance using port 39000, another using 39100, and another on 39200, among others. This setup may be causing port overlap issues.

We would like to confirm the maximum port range that a given instance can access. Our assumption was that it wouldn’t exceed a range of 100 ports, so we configured our servers accordingly. Could you clarify whether this assumption holds and if adjustments are needed?

CryoSPARC may open ports in the ephemeral port range in addition to ports in the designated port range.
To prevent overlaps between the “designated” port range and “ephemeral” ports, one should configure (during or after installation) ports outside the ephemeral port range. In your case, you might consider
61000, 61010, 61020 base ports instead of 39000, 39100, 39200, respectively, provided the 610?? ports are not already in use.

We were able to change the ip_local_port_range, not to overlap with any of the port assigned to Cryosparc servers.Thank you very much for your assistance.