# IPv6 connect/disconnect issue with mqtt in or out nodes

**URL:** <https://discourse.nodered.org/t/ipv6-connect-disconnect-issue-with-mqtt-in-or-out-nodes/74444>\
**Category:** General\
**Tags:** mqtt\
**Created:** [30 January 2023 21:26 UTC](https://discourse.nodered.org/t/ipv6-connect-disconnect-issue-with-mqtt-in-or-out-nodes/74444 "2023-01-30T21:26:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [30 January 2023 23:41 UTC](https://discourse.nodered.org/t/ipv6-connect-disconnect-issue-with-mqtt-in-or-out-nodes/74444/2 "2023-01-30T23:41:06Z")

</div>

If you have only one subscription and you make a change that makes the MQTT node be redeployed (i.e if you modify it or use full deploy mode) you will be hitting a known bug

See here: [MQTT not reconnecting if only only one mqtt node using it](https://discourse.nodered.org/t/mqtt-not-reconnecting-if-only-only-one-mqtt-node-using-it/69381)

And here: [MQTT not reconnecting on edit if only only one mqtt node using the config node · Issue #3927 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/3927)

Fixed in next release (v3.1.0)

---

_[View the full topic](https://discourse.nodered.org/t/ipv6-connect-disconnect-issue-with-mqtt-in-or-out-nodes/74444)._