Unable to start node red (windows 10)

Hello, I am new to node-red and cannot seem to get it to launch. Here are the steps I have taken:

  • install Node.js
  • executed command "npm install -g --unsafe-perm node-red" in cmd
  • executed command "npm install --global --production windows-build-tools" in cmd
  • executed command "node-red" in cmd

Output is:

7 Aug 13:09:18 - [info] Node-RED version: v0.20.7
7 Aug 13:09:18 - [info] Node.js version: v10.16.2
7 Aug 13:09:18 - [info] Windows_NT 10.0.17134 x64 LE
7 Aug 13:09:20 - [info] Loading palette nodes
7 Aug 13:09:22 - [warn] rpi-gpio : Raspberry Pi specific node set inactive

That's it. Cmd is now waiting for another command. What gives?

Are you using your web browser to look at node red once launched?
If not, then open a browser and type 'localhost:1880' that should open up node red for you.

Your cmd window should not be waiting for another command, it should just be sitting there and when you access node-red on your browser, the cmd window will display actions that it is performing.
Keep the cmd window open until you finish with node red, then use 'CTRL - C' to exit.
Are you using just normal CMD window or using Shell in Admin mode?
Not sure if it makes a difference but I 'right-click' on windows (bottom left icon) and select Windows shell admin mode, then run node-red from within that. Same as above though, you access node red from within a browser.

You seem to have run the right commands in the right order (apart from installing v10 of node.js -the instructions say to install v8 but I don't think that is actually causing the issue here)

Does it work if you reboot your machine?

Hummmm, he must have either got it working or given up!

I ended up uninstalling node.js and manually deleting all associated folders such as ".node-red." After reinstalling node.js and node-red everything seems to be working. Thank you for the suggestions!

I can confirm that node.js v10 works just fine with Node-RED on Windows 10.

If it just hangs it could be a network issue if you are behind a corporate proxy. This issue has come up multiple times, but I can't find the related forum topics just now. It had something to do with NPM checking package versions, I think.

If that's the case, it should resume after 2-3 minutes.