Help

Upcoming database upgrades. to improve our reliability at 03:30 UTC on Feb. 25 / 7:30pm PT on Feb. 24. Some users may briefly experience slow load times or error messages. Learn more here

How to change block port, port 9001 is already taken

Topic Labels: Custom Extensions
Solved
Jump to Solution
526 2
cancel
Showing results for 
Search instead for 
Did you mean: 

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

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

2 Replies 2

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!