# Node-Red Crashes - Leaves a TCP timeout error prior - How to trace?
**URL:** https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513
**Category:** General
**Created:** [29 March 2022 19:49 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513 "2022-03-29T19:49:11Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 19:49 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/1 "2022-03-29T19:49:11Z")
````nohighlight
29 Mar 19:46:14 - [error] Error: connect ETIMEDOUT 51.195.235.166:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'. ```
I'm trying to trace this in my project but can't seem to find out what the culprit is.
Any tricks to trace this to which node etc is causing node-red to exit and restart?
Happens about once every minute or two. Restarts.
NR is responsive until restart.
````
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:13 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/2 "2022-03-29T20:13:37Z")
Is that all the message you get?
What versions of node-red and nodejs (use `node -v` to get it) are you using?
What hardware/os are you using?
Do you recognise that IP address? The host appears to be [vps-e031dc24.vps.ovh.net](http://vps-e031dc24.vps.ovh.net)
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 20:17 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/3 "2022-03-29T20:17:46Z")
Thanks for verifying the host name.. I got as far as [ovh.net](http://ovh.net) but nothing specific. Maybe I can trace code to see if there is any entry with that.
My current NR version is `2.1.4`
Running on a Linux Ubuntu AWS EC2 service. t3a.medium as of now. I upgraded a step up to make sure I was clear on RAM at least, but never really maxed out even on the config prior...
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:19 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/4 "2022-03-29T20:19:59Z")
And the nodejs version?
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 20:20 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/5 "2022-03-29T20:20:03Z")
Sorry: Node Version is v12.22.4
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:25 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/6 "2022-03-29T20:25:00Z")
Probably worth upgrading node red to the latest, unless that is a problem for you. Also make sure you are using the latest versions of all installed nodes (check in Manage Palette).
There are two issues
1. Why is it trying to access that IP, which is presumably something in your flows
2. Why does the timeout cause a crash. Upgrading node red and all the nodes might help with this one.
You didn't say whether that is the complete message. Can you post the node red log all the way from the startup the beginning of the next restart please.
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 20:40 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/7 "2022-03-29T20:40:59Z")
````nohighlight
29 Mar 20:02:21 - [info] Node.js version: v12.22.4
29 Mar 20:02:21 - [info] Linux 5.4.0-1069-aws x64 LE
29 Mar 20:02:21 - [info] Loading palette nodes
29 Mar 20:02:23 - [info] +-----------------------------------------------------
29 Mar 20:02:23 - [info] | uibuilder initialised:
29 Mar 20:02:23 - [info] | Using Node-RED's webserver
29 Mar 20:02:23 - [info] | root folder: /home/ubuntu/.node-red/uibuilder
29 Mar 20:02:23 - [info] | version . .: 3.3.1
29 Mar 20:02:23 - [info] | packages . : jquery,socket.io,vue,bootstrap-vue,bootstrap
29 Mar 20:02:23 - [info] +-----------------------------------------------------
29 Mar 20:02:23 - [info] Dashboard version 3.1.2 started at /ui
29 Mar 20:02:24 - [info] Settings file : /home/ubuntu/.node-red/settings.js
29 Mar 20:02:24 - [info] HTTP Static : /home/ubuntu/www
29 Mar 20:02:24 - [info] Context store : 'default' [module=memory]
29 Mar 20:02:24 - [info] User directory : /home/ubuntu/.node-red
29 Mar 20:02:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Mar 20:02:24 - [info] Flows file : /home/ubuntu/.node-red/flows.json
Unhandled rejection Error: form-data: ENOENT: no such file or directory, open '/02.png'
29 Mar 20:02:24 - [info] Server now running at https://127.0.0.1:443/admin/
29 Mar 20:02:24 - [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.
---------------------------------------------------------------------
29 Mar 20:02:24 - [info] Starting flows
MongoDB URL: mongodb://127.0.0.1:27017/psiaf2020
MongoDB URL: mongodb+srv://streamtacular:[streamtacular123]@streamtacular.dg46e.mongodb.net/psiaf2020
MongoDB URL: mongodb://127.0.0.1:27017/psiaf2020
connecting: mongodb://127.0.0.1:27017/psiaf2020
connecting: mongodb+srv://streamtacular:[streamtacular123]@streamtacular.dg46e.mongodb.net/psiaf2020
... insert a ton of DB connections like logged above...
29 Mar 20:04:37 - [red] Uncaught Exception:
29 Mar 20:04:37 - [error] Error: connect ETIMEDOUT 51.195.235.166:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 27.
Stopped Node-RED graphical event wiring tool.```
I am currently upgrading NR and Node. I just got done, and I think I yet to have it restart... Will be watching, and update you later.
Thanks
````
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:44 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/8 "2022-03-29T20:44:59Z")
If you upgraded nodejs make sure it is to v14 or 16, not an odd numbered one. It was the installed nodes that I was suggesting you should check for updates rather than nodejs. nodejs 12 is approaching end of life though, so probably a good thing to update anyway.
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 20:50 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/9 "2022-03-29T20:50:21Z")
Yeah I went ahead and upgraded anyways...
The `stable` v16...
And NR to the latest...
I am still catching the error...
I will try and update the nodes via the pallet until it boots me...
I may need to look into how to update the nodes via command line.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:53 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/10 "2022-03-29T20:53:03Z")
What is the problem upgrading the nodes via Manage Palette?
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 20:53 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/11 "2022-03-29T20:53:35Z")
Odd:
` node -v v16.14.2`
but NR reports its using v12
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 20:55 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/12 "2022-03-29T20:55:34Z")
How did you install node-red and nodejs initially? Did you use the recommended Pi/Debian/Ubuntu script [Running on Raspberry Pi : Node-RED](https://nodered.org/docs/getting-started/raspberrypi)
How have you upgraded nodejs?
What does
`apt policy nodejs`
show?
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 21:01 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/13 "2022-03-29T21:01:43Z")
I generally install NR via the instructions at `https://nodered.org/docs/getting-started/local`
If I remember correctly this is how this instance was setup.
I used `nvm` to upgrade nodejs
````auto
Installed: 12.22.4-1nodesource1
Candidate: 12.22.11-1nodesource1
Version table:
12.22.11-1nodesource1 500
500 https://deb.nodesource.com/node_12.x bionic/main amd64 Packages
*** 12.22.4-1nodesource1 100
100 /var/lib/dpkg/status
8.10.0~dfsg-2ubuntu0.4 500
500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
8.10.0~dfsg-2ubuntu0.2 500
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages
8.10.0~dfsg-2 500
500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages```*emphasised text*
````
---
### Author:  [@mrSidX](https://discourse.nodered.org/u/mrSidX)
#### Post date: [29 March 2022 21:07 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/14 "2022-03-29T21:07:13Z")
I can confirm all the nodes are updated and just now had a restart... same
It seems to not happen as often?
````nohighlight
29 Mar 20:59:45 - [error] Error: connect ETIMEDOUT 51.195.235.166:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 47.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.```
````
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 21:12 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/15 "2022-03-29T21:12:06Z")
> [@mrSidX](#):
>
> I used `nvm` to upgrade nodejs
Not a good plan, I believe that installs nodejs in a different place to standard, so now you have both installed. In your position I would remove the nvm version and remove nvm, then I would use the script I linked to, with `--node16` on the end (after a space). That should install nodejs 16 and ensure you are on the latest version of node-red.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 March 2022 21:13 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/16 "2022-03-29T21:13:13Z")
As to the error, I think you need to find out what in the flows is trying to access that IP address.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [28 May 2022 21:14 UTC](https://discourse.nodered.org/t/node-red-crashes-leaves-a-tcp-timeout-error-prior-how-to-trace/60513/17 "2022-05-28T21:14:11Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.