# Debugging http in node issues

**URL:** <https://discourse.nodered.org/t/debugging-http-in-node-issues/69644>\
**Category:** General\
**Created:** [26 October 2022 20:13 UTC](https://discourse.nodered.org/t/debugging-http-in-node-issues/69644 "2022-10-26T20:13:07Z")\
**Posts on this page:** 3\
**Page:** 4

<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:** [30 October 2022 19:27 UTC](https://discourse.nodered.org/t/debugging-http-in-node-issues/69644/61 "2022-10-30T19:27:51Z")

</div>

Stick with the IP while you are testing.  
Have you got another router you could temporarily use? It wouldn't matter if it didn't connect to the internet, you just need a basic router.

---

<div class="post-metadata">

**Author:** ![hepcat72](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hepcat72/32/8078_2.png) [@hepcat72](https://discourse.nodered.org/u/hepcat72)\
**Post date:** [1 November 2022 13:14 UTC](https://discourse.nodered.org/t/debugging-http-in-node-issues/69644/62 "2022-11-01T13:14:52Z")

</div>

OK. 2 things:

1. The problem appears to be restricted to mDNS
2. (SMH) When I edited the `WebSend` command, I introduced `http://` (because my eye skipped over to the end of the line in the tasmota commands doc which reads " `WebSend [myserver.com] /fancy/data.php?log=1234` sends `http://myserver.com/fancy/data.php?log=1234`" on one line. I.e. The bad command was entered as `WebSend [http://192.168.1.56:1880] /desklighton`

Once I fixed that to read `WebSend [192.168.1.56:1880] /desklighton`, using the static DHCP address worked.

I discovered this because on the tasmota discord, I decided I should do a sanity check and asked a second pair of eyes to ensure my `WebSend` command was right.

I still think that something in unifios changed to cause `WebSend [raspberrypi.local:1880] /desklighton` to stop working.

So I feel like a heel, obviously.

It's interesting to note that the tasmota developer claims tasmota doesn't support mDNS, so my next thought it: why did using `raspberrypi.local` ever work? Because it was definitely working for a loooong time. I didn't think that the sending device making the webhook call (or receiving device for that matter) had anything to do with the resolution of an mDNS domain. So what does it mean for a device to claim it doesn't support mDNS?

And if that's the case (the sending device plays a role in the resolution of an mDNS domain address), perhaps there's nothing technically wrong with the unifios update?

---

<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:** [15 November 2022 13:15 UTC](https://discourse.nodered.org/t/debugging-http-in-node-issues/69644/63 "2022-11-15T13:15:29Z")

</div>

Closed on 15 November 2022 13:15 UTC

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

[Previous page](https://discourse.nodered.org/t/debugging-http-in-node-issues/69644.md?page=3)