Installing WAB on another port

[LefterisKoumis]

I got a new PC (windows 11), and trying to install the WAB on another port.

I followed the steps outlined on the WAB's Get Starter website  by typing under the server dir the command:

node_x64.exe server.js -4000

Then in the cmd window I noticed the screen further below.

When I tried to access the website by :

https://<mymachinename>:4000/webappbuilder I got "The site can't reached" 

Even though I tried to  run WAB under port 4000 it still uses 3344. What am I doing wrong?

@RobertScheitlin__GISP 

[Brian_Wilson]

Try "node_64.exe server.js --port=4000"

[LefterisKoumis]

No difference.

[Brian_Wilson · Accepted solution]

Ha !!! Use one dash not two      -port=4000

wabde_1  | Server listening tcp connection on port 4000 in development mode
wabde_1  | [2023-02-14T23:23:11.311] [INFO] repo - Read repository items: /srv/client/stemapp/widgets
wabde_1  | Server listening http connection on port 4001 in development mode
wabde_1  | Server listening https connection on port 4002 in development mode
wabde_1  | [2023-02-14T23:23:14.774] [INFO] repo - Read repository items: /srv/client/stemapp/themes

[LefterisKoumis]

Thank you. That was it. The only reason why I am using the default 3344 is because I get the "The site can't reached" . I checked the port 3344 and is not used so I am lost for words why is not working. 

[Brian_Wilson]

You use Windows!   🙂    Is there a firewall running on the machine? They have those by default these days.

[LefterisKoumis]

It is not the firewall. I disabled my firewall temporary, and still didn't work.

I installed WAB myriad of times and this the first time I have this issue. 

I run the netstat to review the ports and there is nothing unusual.  Thank you for your help.

[LefterisKoumis]

Just FYI, I found a way to run WAB on port 3344 by running a windows service instead of using the startup script.

[Brian_Wilson]

Good on you, I've never worked through running Node on Windows.

I run it (along with many other things) in Docker containers for both Windows and Linux and highly recommend that. There are many advantages, including not corrupting the operating system and running different incompatible apps that need different versions of Node.