# Nodered restarts several times

**URL:** <https://discourse.nodered.org/t/nodered-restarts-several-times/100451>\
**Category:** Industrial\
**Tags:** docker\
**Created:** [25 February 2026 08:18 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451 "2026-02-25T08:18:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Piou2fois](https://avatars.discourse-cdn.com/v4/letter/p/45deac/32.png) [@Piou2fois](https://discourse.nodered.org/u/Piou2fois)\
**Post date:** [25 February 2026 08:18 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/1 "2026-02-25T08:18:56Z")

</div>

Good morning  
I have a nodered in docker mainly working to communicate with SIEMENS PLC via S7 (node-red-contrib-s7) connected to influxdb 1.x and using some API for Grafana (to show ping results)  
I have from time to time nodered container restarting and in the log I have the following :

```auto
[red] Uncaught Exception:
24 Feb 16:37:27 - [error] Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:218:20)
24 Feb 16:37:28 - [info] 

```

Same message can be seen 3 or 4 times and then nothing for a day.  
I have a lot of error due to the S7 endpoints because we have some PLC that are shutdown so i was wondering if it could be due to that or something else.  
Is there a way to investigate the kind of error causing the restart ?

```auto
Node-RED version: v4.1.4

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 February 2026 09:28 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/2 "2026-02-25T09:28:38Z")

</div>

What do you see in the log that causes the container restart?

---

<div class="post-metadata">

**Author:** ![Piou2fois](https://avatars.discourse-cdn.com/v4/letter/p/45deac/32.png) [@Piou2fois](https://discourse.nodered.org/u/Piou2fois)\
**Post date:** [25 February 2026 10:00 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/3 "2026-02-25T10:00:11Z")

</div>

I have a lot of errors due to S7 endpoint request timeout but I can have this for hours without any issue.

```auto
24 Feb 16:25:49 - [info] Starting flows
24 Feb 16:25:50 - [info] Started flows
24 Feb 16:25:50 - [error] [s7 endpoint:XXX - FAULT] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:XXX - DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY - RESET] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY- FAULT] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY-INVERTERS] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:TTT- DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:TTT- FAULT] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:XXX- DATA] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:YYY- FAULT] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:TTT- FAULT] Error: read ECONNRESET
24 Feb 16:26:00 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:26:29 - [error] [s7 endpoint:ZZZ- FAULT] Error: Request timeout
24 Feb 16:26:29 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:26:30 - [error] [s7 endpoint:ZZZ- RESET] Error: Request timeout
24 Feb 16:26:39 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:26:54 - [error] [s7 endpoint:ZZZ - data] Error: Timeout connecting to the transport
24 Feb 16:26:57 - [error] [s7 endpoint:ZZZ - Totalizers] Error: Request timeout
24 Feb 16:27:09 - [error] [s7 endpoint:ZZZ - data] Error: Timeout connecting to the transport
24 Feb 16:27:19 - [error] [s7 endpoint:ZZZ - data] Error: Request timeout
24 Feb 16:36:28 - [error] [s7 endpoint:ZZZ- FAULT] Error: Request timeout
24 Feb 16:36:29 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:36:31 - [error] [s7 endpoint:ZZZ- RESET] Error: Request timeout
[red] Uncaught Exception:
24 Feb 16:36:34 - [error] Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:218:20)
24 Feb 16:36:35 - [info] 
Welcome to Node-RED
===================
24 Feb 16:36:35 - [info] Node-RED version: v4.1.4
24 Feb 16:36:35 - [info] Node.js version: v20.20.0
24 Feb 16:36:35 - [info] Linux 6.12.63+deb13-amd64 x64 LE
24 Feb 16:36:35 - [info] Loading palette nodes
24 Feb 16:36:36 - [info] Settings file : /data/settings.js
24 Feb 16:36:36 - [info] Context store : 'default' [module=memory]
24 Feb 16:36:36 - [info] User directory : /data
24 Feb 16:36:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
24 Feb 16:36:36 - [info] Flows file : /data/flows.json
24 Feb 16:36:36 - [info] Server now running at http://127.0.0.1:1880/

```

XXX YYY ZZZ TTT are replaced text but represents a production line

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 February 2026 10:21 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/4 "2026-02-25T10:21:13Z")

</div>

That looks like this issue [Uncaught ECONNRESET causes Node-RED crash after LOGO! reconnect · Issue #143 · st-one-io/node-red-contrib-s7 · GitHub](https://github.com/st-one-io/node-red-contrib-s7/issues/143)

If you follow the links through then it appears to have been fixed in the the package nodes7, but that does not seem to have been released to [npmjs.com](http://npmjs.com) so the contrib node does not include the fix.

---

<div class="post-metadata">

**Author:** ![Piou2fois](https://avatars.discourse-cdn.com/v4/letter/p/45deac/32.png) [@Piou2fois](https://discourse.nodered.org/u/Piou2fois)\
**Post date:** [25 February 2026 10:30 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/5 "2026-02-25T10:30:54Z")

</div>

Thank you for the feedback  
I will wait for the official fix in the package  
At least I know the origin

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 February 2026 10:37 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/6 "2026-02-25T10:37:06Z")

</div>

> [@Piou2fois](#):
>
> I will wait for the official fix in the package

Looking at the dates on those issues I suspect nothing will happen unless you ask for an update there.

---

<div class="post-metadata">

**Author:** ![Piou2fois](https://avatars.discourse-cdn.com/v4/letter/p/45deac/32.png) [@Piou2fois](https://discourse.nodered.org/u/Piou2fois)\
**Post date:** [25 February 2026 11:50 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/7 "2026-02-25T11:50:41Z")

</div>

There is in fact a pull request since Nov 13, 2025 on Nodes7 file s7endpoint.js but not yet released

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [11 March 2026 11:51 UTC](https://discourse.nodered.org/t/nodered-restarts-several-times/100451/8 "2026-03-11T11:51:41Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.