I use Node-RED behind a firewall, which blocks all data traffic from and to the Internet. The block is only temporarily lifted for individual URLs if necessary, for example to install updates. The firewall simply terminates the connections to the Internet. No status and no response is sent back from the firewall. This behavior cannot be changed either.
Now I had to find out that Node-RED no longer starts if the URL https://registry.npmjs.org is blocked by the firewall during the start process.
I would have expected that Node-RED would carry out error handling at this point and skip the NPM registry check.
The start process stops in the log after the operating system version has been output. As soon as I deactivated the firewall and restart Node-RED, Node-RED starts successfully.
If I set the logging to Debug or Trace (settingsfile-> logging.console: trace), no error message is output.
The blocking of the Internet does not cause any problems during operation, because I have deactivated the public node catalog of node-red. The only major problem for me is the blocking of the Internet during the start-up process.
Is there a way to skip the npm registry check without changing the url in the npm configuration?
I've seen that where the console (CMD) is paused & required a keyboard input. Not saying that is definitely what happened to you but that these things do happen.
In other words, the issue you see today looks more like the 3m delay issue & the issue you had in Dec may be a different issue?
Where your console output shows node-red loading & waiting on line 3 Jan 09:05:56 - [info] Windows_NT 10.0.14393 x64 LE is where updateNotifier.checkNpm() occurs.
So my point still stands, try it, it should solve your issue for this 3rd Jan start up issue