Help

How to change block port, port 9001 is already taken

Topic Labels: Custom Extensions
Solved
Jump to Solution
1531 3
cancel
Showing results for 
Search instead for 
Did you mean: 
wbaleroni
4 - Data Explorer
4 - Data Explorer

I’m trying to create a custom block, but when I run:

block run

I get:

Error: listen EACCES: permission denied 0.0.0.0:9001

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?

1 Solution

Accepted Solutions
Billy_Littlefie
7 - App Architect
7 - App Architect

Hi @wbaleroni

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!

See Solution in Thread

3 Replies 3
Billy_Littlefie
7 - App Architect
7 - App Architect

Hi @wbaleroni

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!

msafi04
5 - Automation Enthusiast
5 - Automation Enthusiast

block run --port=<port number> is the correct command to change the default port number