# Strange debug message. Where is it coming from?

**URL:** <https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058>\
**Category:** General\
**Created:** [5 August 2018 03:59 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058 "2018-08-05T03:59:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![SteveMann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevemann/32/3810_2.png) [@SteveMann](https://discourse.nodered.org/u/SteveMann)\
**Post date:** [5 August 2018 03:59 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/1 "2018-08-05T03:59:12Z")

</div>

I imported a few nodes that had a Home Assistant node in it to help someone understand his flow. Did that, then deleted the nodes. But now, I am getting this error: Is there ANY way to determine what node could be trying to connect to duckdns? I have looked at every node in every flow and can't find the offending node. I even tried rebooting the Raspberry this instance of Node-red is on. I went to "Selected Nodes" in the Debug tab and unticked everything, but I am still getting this error. Debug is useless as I am getting this error every second.

Help??

```
8/4/2018, 11:34:44 PM Home Assistant
msg : string[165]
"Home assistant connection failed with error: Connection to home assistant could not be established with config: https://MyDomain.duckdns.org:8123 <password redacted>"

```

![Sig](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/87494c8512470399062d2299b339f0275c0994e1.jpg)

---

<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:** [5 August 2018 06:39 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/2 "2018-08-05T06:39:42Z")

</div>

When you deploy do you get a message about unused configuration nodes? If so then that is the problem.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 August 2018 06:59 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/3 "2018-08-05T06:59:25Z")

</div>

As Colin suggests, you may still have a HA config node lurking in the background.

If you open the configuration nodes sidebar from the drop-down menu, look for any home assistant nodes in there. If there is one, double click it and hit the delete button to remove it.

---

<div class="post-metadata">

**Author:** ![SteveMann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevemann/32/3810_2.png) [@SteveMann](https://discourse.nodered.org/u/SteveMann)\
**Post date:** [5 August 2018 14:07 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/4 "2018-08-05T14:07:05Z")

</div>

Thanks Colin and Knolleary- This is one of the first tings I thought of, but there is no 'unused configuration nodes' warning on deploy, and the only 'HomeAssistant' nodes are my own:

 ![ha-node-red%20configuration](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/a/af99af60e24ce63d6226a2d65581cab2c9e58522.jpg)

I could try removing all 32 of my Home Assistant nodes and reinstall them, but there's no guarantee that this would work. The worst case would be to remove Node-Red from Home Assistant and reinstall NR from scratch. But if I just export/import my flows, will this phantom come back?

Where else can I look?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 August 2018 14:29 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/5 "2018-08-05T14:29:58Z")

</div>

You could search your nodes (using menu option) for MyDomain to see if any of your nodes contain that. Or open your flow file in a text editor and do likewise.

---

<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:** [5 August 2018 14:34 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/6 "2018-08-05T14:34:33Z")

</div>

> [@SteveMann](#):
>
> Home assistant connection failed with error: Connection to home assistant could not be established with config

Ah, I misunderstood, I thought you had deleted all HA nodes. I presume therefore that you did have your domain at duckdns configured at one point.  
Have you tried restarting node-red? Perhaps deleting a node has left something running.

---

<div class="post-metadata">

**Author:** ![SteveMann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevemann/32/3810_2.png) [@SteveMann](https://discourse.nodered.org/u/SteveMann)\
**Post date:** [5 August 2018 19:48 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/7 "2018-08-05T19:48:25Z")

</div>

First, I did reboot the Raspberry at the command line - no change.  
I did export everything and look at the flows text file for the offending link- nothing there. (Also, when I selected "All Nodes" and deselected everything, the error continued).

One last try- I did a cold-boot. Shutdown from the command line then unplug the power to the Pi.

Plug-in, reboot, and now, the offending message is gone. Apparently there was something in RAM that survived a warm-reboot.

Thanks for the assistance- it is greatly appreciated. Note that this Node-red is running on [hass.io](http://hass.io), not Raspian. The last time this happened with Node-red on my Raspian, deleting the offending flow or node always fixed it. So you can appreciate why this one was so confounding.

(And, BTW, I've never used DuckDNS).

![Sig](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/87494c8512470399062d2299b339f0275c0994e1.jpg)

---

<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:** [5 August 2018 20:53 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/8 "2018-08-05T20:53:20Z")

</div>

> [@SteveMann](#):
>
> And, BTW, I've never used DuckDNS.

When you said the error contains "[MyDomain.duckdns.org:8123](http://MyDomain.duckdns.org:8123)" was that literally MyDomain or was it your domain? I assumed the latter. I now suspect it was the former. I imagine this is some default in something somewhere.  
I have great difficulty understanding how a reboot without power cycle had a different effect in this respect to a power cycle. I think I will steer clear of [hass.io](http://hass.io) if (as you suggest) it has a habit of presenting you with such issues.

---

<div class="post-metadata">

**Author:** ![SteveMann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stevemann/32/3810_2.png) [@SteveMann](https://discourse.nodered.org/u/SteveMann)\
**Post date:** [5 August 2018 21:33 UTC](https://discourse.nodered.org/t/strange-debug-message-where-is-it-coming-from/2058/9 "2018-08-05T21:33:33Z")

</div>

> [@Colin](#):
>
> When you said the error contains "[MyDomain.duckdns.org:8123](http://MyDomain.duckdns.org:8123)"

Easy mistake. This was the address in the other user's Home Assistant node. Why it didn't go away when I deleted his flow mysterifies me. I have had other "oddities" in [hass.io](http://hass.io) that only cleaned up with a cold boot, so it will likely be my default tool in that Pi.
