I’ve checked and there’s a system task already listening to this port, so I’m not able to just kill it.
Is there a way to change the listening port so that I can make this work?
Sorry you’ve been running into issues! I would’ve expected the CLI to detect the collision and prompt you for another port, but I think you should be able to work around this by another means: the default port can be configured using the default-port argument, e.g.
Sorry you’ve been running into issues! I would’ve expected the CLI to detect the collision and prompt you for another port, but I think you should be able to work around this by another means: the default port can be configured using the default-port argument, e.g.
Sorry you’ve been running into issues! I would’ve expected the CLI to detect the collision and prompt you for another port, but I think you should be able to work around this by another means: the default port can be configured using the default-port argument, e.g.
block run --default-port 9002
Hope this helps!
I had the same issue; 9001 was taken by System - thanks!