# Node-red-contrib-modbus no reconnect

**URL:** <https://discourse.nodered.org/t/node-red-contrib-modbus-no-reconnect/50309>\
**Category:** General\
**Created:** [28 August 2021 00:24 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-no-reconnect/50309 "2021-08-28T00:24:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [28 August 2021 03:28 UTC](https://discourse.nodered.org/t/node-red-contrib-modbus-no-reconnect/50309/2 "2021-08-28T03:28:58Z")

</div>

Read this thread .. possibly related.

> [@Modbus TCP client not reconnecting after modbus server goes offline](https://discourse.nodered.org/t/modbus-tcp-client-not-reconnecting-after-modbus-server-goes-offline/50264):
>
> 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 ?

---

_[View the full topic](https://discourse.nodered.org/t/node-red-contrib-modbus-no-reconnect/50309)._