SuiteCloud CLI browser-based authentication fails with "Address already in use: bind" error on Windows systems with port exclusions

[mrab54]

Select the SuiteCloud tool where you encountered the issue

SuiteCloud CLI

Version of the SuiteCloud Tool

3.0.0

Operating system

Windows 11 24H2 (OS Build 26100.4946)

Node Version / VSCode Version

v22.13.1

JAVA Version

java 17.0.13+10-LTS-268

Bug description

SuiteCloud CLI fails during browser-based authentication with "Address already in use: bind" error when attempting to start the local callback server. This occurs when the CLI's hardcoded port range (52300-52315) conflicts with Windows port exclusions.

The CLI attempts to bind to ports 52300-52315 for authentication callback, but when these ports fall within a Windows excluded port range, the binding fails.

Steps To Reproduce

1. Check for existing port exclusions:
   netsh int ipv4 show excludedportrange protocol=tcp
2. If no port exclusion exists for port range 52300-52315, then create one (as Administrator): netsh int ipv4 add excludedportrange protocol=tcp startport=52300 numberofports=16
3. Run suitecloud file:upload or any command requiring authentication
4. Observe authentication attempt fails with "Address already in use: bind"

Actual Output

F:\dev> suitecloud file:upload
The authorization credentials associated with auhtid are no longer valid. Starting the browser-based authentication for refreshing them.
Address already in use: bind

---

There is a typo in the output there "auhtid" as well.

Expected Output

Browser-based authentication should complete successfully, opening browser for NetSuite login and completing the authorization flow without port binding errors.

Or, provide the ability to specify port range to use.

Anything else?

No response

[alisyed-19]

@mrab54
Are you continuously getting this error? or you blocked by this?

I want to understand the priority here, should we find a workaround for this (Maybe you already have one).
Are requesting a perm solution for this?

Restarting your machine helps get past this error?

[mrab54]

@alisyed-19
A reboot of my machine "fixes" it. I run into the problem about 2-3 times per week. I have not been able to identify what process is grabbing the ports. So, definitely not blocking but is disruptive enough that I came here to open an issue.

Thanks!

[alisyed-19]

@mrab54 Thanks for clarification.
I will mark it as "Enhancement request", where you would like to have the ability to define the port range for yourself.

[tyler-timm-ea]

I'd like to add that I'm also running into this same issue in the same scenario.

[lordvlad]

Same issue here.

I've worked around this by patching the suitecloud sdk jar file. With intellij, I decompiled the class files, and edited com/netsuite/ide/core/authentication/server/LocalAuthServerImpl.java, to search for an available port starting at 3000, and authentication succeeded.

Digging a little bit, I've found that windows prohibits binding a port in the 'ephemeral range'. On my windows machine its

PS > netsh int ipv4 show dynamicport tcp

Protocol tcp Dynamic Port Range
---------------------------------
Start Port      : 49152
Number of Ports : 16384

so it overlaps with suiteclouds auth port range of 52300 - 52315

Chatgpt suggested to change the ephemeral port range using

netsh int ipv4 set dynamicport tcp start=xxxxx num=yyyyy

but by then I already hacked my way around it. At least until the next sdk update.

It would be nice to make the listener port configurable, or just move the searched range a bit down below 49152.

For who's interested the exact steps:

• npm i -g @oracle/suitecloud-cli
• go to ~/.suitecloud-sdk/cli, unpack cli-VERSION.jar
• patch LocalAuthServerImpl using a decompiler of your choice, I used IntelliJ

  •    private int searchPortAvailable() throws SuiteCloudServiceException {
       ---   for(int port = 52300; port <= 52315; ++port) {
       +++   for(int port = 3000; port <= 52315; ++port) {
              if (this.isPortAvailable(port)) {
                  return port;
              }
          }
    
          String messageRange = String.format("%d-%d", 52300, 52315);
          String message = Messages.bind(Messages.msg_oauth_port_error, messageRange);
          throw new SuiteCloudServiceException(message);
      }

• compile the java file, put the class file back into the jar