ServiceNow Cowork binds to port 3000

JesperMol
ServiceNow Employee

4 weeks ago - last edited 4 weeks ago

Just a heads up for anyone on Brazil Patch 1 and is trying to use Cowork and the UI asks you to present a arc-server token. It just so happens that Cowork binds to port 3000 a very popular port for vibe coded web apps. 

 

Once you moved off your web app from Port 3000 Cowork will launch fine. 

 

#cowork

0 Helpfuls
  • 459 Views
1 REPLY 1

sanjaygupta
Tera Guru

a week ago

 

This looks like a port conflict rather than a Cowork configuration issue. A ServiceNow employee has confirmed that, on the Brazil Patch 1 release, Cowork uses port 3000, which is also commonly used by locally running web applications.

You can resolve it with a simple change:

  • Stop your local web application running on port 3000.

  • Change your web application's development port to another available port, such as 3001.

  • Restart your web application.

  • Launch ServiceNow Cowork again.

The original community post confirms that once the web application is moved away from port 3000, Cowork launches successfully without the Arc Server token prompt.

This is a port conflict workaround, not a change to your ServiceNow instance configuration.

Reference: ServiceNow Community – ServiceNow Cowork binds to port 3000

 
ServiceNow Community

 

Hope you find this helpful.
0 Helpfuls