# Modbus TCP client not reconnecting after modbus server goes offline

**URL:** <https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264>\
**Category:** General\
**Created:** [27 August 2021 09:19 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264 "2021-08-27T09:19:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![krish7](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krish7/32/47045_2.png) [@krish7](https://discourse.nodered.org/u/krish7)\
**Post date:** [27 August 2021 09:19 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/1 "2021-08-27T09:19:13Z")

</div>

I am running a modbus TCP client (node-red-contrib-modbus) on a node red inside a docker container. However, when the server goes offline and comes online - it's not reconnecting - it shows "reconnecting after 2000 msec" message. Any thoughts to re establish the connection ?

---

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [27 August 2021 13:39 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/2 "2021-08-27T13:39:45Z")

</div>

What Nodejs version are you running ?

I think there is an issue with those nodes reconnecting when running nodejs higher than v12.  
Read about this issue on the node's [github page](https://github.com/BiancoRoyal/node-red-contrib-modbus/issues/236) and [here](https://github.com/BiancoRoyal/node-red-contrib-modbus/pull/271)

---

<div class="post-metadata">

**Author:** ![krish7](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krish7/32/47045_2.png) [@krish7](https://discourse.nodered.org/u/krish7)\
**Post date:** [27 August 2021 14:27 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/3 "2021-08-27T14:27:12Z")

</div>

How to check that. I am running this on a docker container using the following command

```auto
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red

```

I believe this will fetch the latest version of all, how to change the node.js version ?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [27 August 2021 14:36 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/4 "2021-08-27T14:36:29Z")

</div>

Plenty of tags to choose from ... [Docker Hub](https://hub.docker.com/r/nodered/node-red/tags?page=1&ordering=last_updated)

---

<div class="post-metadata">

**Author:** ![krish7](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krish7/32/47045_2.png) [@krish7](https://discourse.nodered.org/u/krish7)\
**Post date:** [27 August 2021 20:20 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/5 "2021-08-27T20:20:42Z")

</div>

Thanks for that.  
I pulled one image with node JS version 10.xx. It's working

---

<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:** [10 September 2021 20:21 UTC](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264/6 "2021-09-10T20:21:10Z")

</div>

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