# Odd MQTT connect behavior. Maybe AEDES broker node, maybe not

**URL:** <https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771>\
**Category:** General\
**Created:** [7 December 2024 22:16 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771 "2024-12-07T22:16:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmorris644](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jmorris644/32/31964_2.png) [@jmorris644](https://discourse.nodered.org/u/jmorris644)\
**Post date:** [7 December 2024 22:16 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771/1 "2024-12-07T22:16:08Z")

</div>

I am using project management. I maintain the project on one computer, push it to github, and then pull it down to another computer.

I am using Aedes broker node and it is installed on both computers.

I can create a MQTT Server node for localhost:1883 (I have also tried 127.0.0.1:1883) and it works just fine on the source node-red. But when I push and pull it, the MQTT-out node, for example, will not connect.

---

<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:** [8 December 2024 15:13 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771/2 "2024-12-08T15:13:37Z")

</div>

I don't know why Aedes might not work, but my advice would be to install Mosquitto.

---

<div class="post-metadata">

**Author:** ![greengolfer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/greengolfer/32/28276_2.png) [@greengolfer](https://discourse.nodered.org/u/greengolfer)\
**Post date:** [8 December 2024 18:43 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771/3 "2024-12-08T18:43:26Z")

</div>

If I understand correctly, you are using this [node-red-contrib-aedes (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-aedes) ?  
Like Colin, I prefer using mosquitto... However, as it avoids an external broker, that may be interesting in some cases.  
Are you using authentication on MQTT ? It don't think you can "transfer" authentication through github.

---

<div class="post-metadata">

**Author:** ![jmorris644](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jmorris644/32/31964_2.png) [@jmorris644](https://discourse.nodered.org/u/jmorris644)\
**Post date:** [9 December 2024 16:04 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771/4 "2024-12-09T16:04:21Z")

</div>

Thanks.

I have previously used mosquito but I have a need to grab some of the messages from the broker and I take action based on what I see in node-red.

I have determined that it is an Aedes node issue and have posted an issue stating

```auto
I manage node-red replicated projects through github.

When I push and pull a node-red instance that contains the Aedes broker node, the node will not respond to MQTT nodes that are configured with either localhost or 127.0.0.1 as their server. I can change the server on the MQTT nodes to any other server and it works.

If I delete the Aedes broker node and drop it on the workspace and redeploy then it all works as expected. localhost and 127.0.0.1 can be accessed.

```

---

<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:** [9 March 2025 16:04 UTC](https://discourse.nodered.org/t/odd-mqtt-connect-behavior-maybe-aedes-broker-node-maybe-not/93771/5 "2025-03-09T16:04:23Z")

</div>

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