Node-Red will not start after adding the open weather nodes

To start I have node-red installed on a windows 10 PC

I installed this node but did not fully configure it with the API so it would not let me deploy it so I removed it from the flow but now I cant start node red normally. I was able to start Node-Red in safe mode and I uninstalled the openweather nodes but I still cant start Node-Red normally?

I start node-red in the command prompt and it looks like its starting but then the command prompt just closes and node-red never starts.

Before anyone can begin to help - please paste the output of Node RED during it's attempt at start.
please don't use a screenshot, and surround it with 3 backticks (```)

```
Paste here 
```

how do I capture this in the command prompt, it closes so quickly?

open up CMD presumably (I don't use windows)
And fork the output to a text file

node-red-start > output.txt

it should appear in the directory that CMD is running in

I will give it a try. thank you

1 Like

Does node-red-start work on Windows? If not then try

node-red > output.txt

1 Like

Good call - I don't think it does, I'm not entirely sure what all the commands are to be honest in windows.

nothing happens when I type node-red > output.txt

That is almost expected - it redirects stdout to a text file (so you won't see anything in the command window), check for output.txt in the directly that CMD was running under (usually your user directory)

I see. getting the text file off of the other PC now

12 Dec 13:53:15 - [info] 

Welcome to Node-RED
===================

12 Dec 13:53:15 - [info] Node-RED version: v3.0.2
12 Dec 13:53:15 - [info] Node.js  version: v16.15.1
12 Dec 13:53:15 - [info] Windows_NT 10.0.19044 x64 LE
12 Dec 13:53:16 - [info] Loading palette nodes
12 Dec 13:53:17 - [info] Dashboard version 3.6.1 started at /ui
12 Dec 13:53:17 - [info] Settings file  : C:\Users\nbmaintenance\.node-red\settings.js
12 Dec 13:53:17 - [info] Context store  : 'default' [module=memory]
12 Dec 13:53:17 - [info] User directory : \Users\nbmaintenance\.node-red
12 Dec 13:53:17 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Dec 13:53:17 - [info] Flows file     : \Users\nbmaintenance\.node-red\flows.json
12 Dec 13:53:17 - [info] Server now running at http://127.0.0.1:1880/
12 Dec 13:53:17 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

12 Dec 13:53:17 - [info] Starting flows
12 Dec 13:53:17 - [info] [tcp in:b7b4abcfeccdd815] connecting to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:53:17 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:53:17 - [info] [tcp out:f8a7fa6523899483] connecting to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:4e2fa3970eb64269] connecting to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:Barcode Data] connecting to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:Barcode Data] connecting to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:53:17 - [info] Started flows
12 Dec 13:53:17 - [info] [aedes broker:Local Broker Shop PC] Binding aedes mqtt server on port: 1883
12 Dec 13:53:17 - [info] [tcp in:b7b4abcfeccdd815] connected to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp out:f8a7fa6523899483] connected to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:4e2fa3970eb64269] connected to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:Barcode Data] connected to 10.3.13.80:23
12 Dec 13:53:17 - [info] [tcp in:Barcode Data] connected to 10.3.13.80:23
12 Dec 13:53:17 - [info] [mqtt-broker:1d430f4081fd9f67] Connected to broker: mqtt://10.3.5.126:1883
12 Dec 13:53:19 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:19 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:53:19 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:19 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:53:19 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:19 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:53:29 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:53:29 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:53:29 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:31 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:53:41 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:53:41 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:53:41 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:53:43 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:53:53 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:53:53 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:53:53 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:53:55 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:54:05 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:54:05 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:54:05 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:07 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:54:17 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:54:17 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:54:17 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:19 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:54:29 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:54:29 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:54:29 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:31 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:54:41 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:54:41 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:54:41 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:43 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:54:53 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:54:53 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:54:53 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:54:55 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:05 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:55:05 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:55:05 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:55:08 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:55:18 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:55:18 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:55:18 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:20 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:55:30 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:55:30 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:55:30 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:32 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:55:42 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:55:42 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:55:42 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:44 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:55:54 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:55:54 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:55:54 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:55:56 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:56:06 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:56:06 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:56:06 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:08 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:56:18 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:56:18 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:56:18 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:20 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:56:30 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:56:30 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:56:30 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:32 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:56:42 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:56:42 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:56:42 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:44 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200
12 Dec 13:56:54 - [info] [tcp in:8a58d8fae02858cc] connecting to 10.3.102.164:57200
12 Dec 13:56:54 - [info] [tcp out:6f330034d12e7f6c] connecting to 10.3.102.164:57200
12 Dec 13:56:54 - [info] [tcp out:f1b6980a53b77f6a] connecting to 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp in:8a58d8fae02858cc] Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp in:8a58d8fae02858cc] connection lost to 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp out:6f330034d12e7f6c] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp out:6f330034d12e7f6c] connection lost to 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp out:f1b6980a53b77f6a] error: Error: connect ECONNREFUSED 10.3.102.164:57200
12 Dec 13:56:56 - [info] [tcp out:f1b6980a53b77f6a] connection lost to 10.3.102.164:57200

Woah!!!

That's is truck load of connections failing, and likely causing an eventual crash with the Node runtime.

Start node red in safe-mode.

node-red --safe

Identify the problem in your flow (seek and destroy) - your flows will start when you deploy, rinse and repeat until your find the problem

Not that its a good thing to have all of those connection issues but all of those were there before installing the weathercloud nodes

So it just closes (Evan when forking the output)?
Do try safe mode - something in your flow may have gone bad or the weather nodes is causing an issue, and isn't fully removed.

as well as running in safe mode to investigate.

run this (it will show you what nodes are installed and may highlight a borked removal of the node)

cd C:\Users\nbmaintenance\.node-red
npm ls

I did try in safe mode and it deploys fine until I try to restart. I do think it has to do with the openweather node

I removed the node and installed again and this is what i was originally getting

I removed the openweather node again and ran this command. the only thing I saw was node-red in this directory

I am not sure why its says missing node type when I have the node in the workspace? I only installed one node package.

any idea why its says missing node types or module not found when I am tryin to use the node I just installed?
image