# HTTP Request Node stuck on requesting, causes flow to Hang

**URL:** <https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138>\
**Category:** General\
**Tags:** http-request, home-assistant\
**Created:** [10 January 2026 17:07 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138 "2026-01-10T17:07:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rulasmur](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rulasmur/32/105351_2.png) [@Rulasmur](https://discourse.nodered.org/u/Rulasmur)\
**Post date:** [10 January 2026 17:07 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/1 "2026-01-10T17:07:51Z")

</div>

I have node-red installed on Home Assistant, with a flow that takes mqtt events, processes them, then goes to a secondary system to fetch and image and finally sends all the information to ntfy via http-request node.

I have 3 http-request nodes in my flow, and they are now randomly getting stuck on "requesting". Attempting to open the node gives me a "Failed to load node credentials".  
Reloading the webpage simply hangs.

Even with logging on trace, there is nothing that shows why it is hanging.  
After a while the HACS addon does seem to restart:

```auto
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[18:21:30] INFO: Service NGINX exited with code 0 (by signal 0)

```

I have found by individually isolating each node in the flow, that this only starts occurring when the last http-request node is attached to the rest. This, somehow, causes the first or second http-request nodes to start acting up

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [10 January 2026 17:12 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/2 "2026-01-10T17:12:32Z")

</div>

Try deleting then reconstructing the http headers between request nodes,

From the sidebar help text

> #### Using multiple HTTP Request nodes

> In order to use more than one of these nodes in the same flow, care must be taken with the `msg.headers` property. The first node will set this property with the response headers. The next node will then use those headers for its request - this is not usually the right thing to do. If `msg.headers` property is left unchanged between nodes, it will be ignored by the second node. To set custom headers, `msg.headers` should first be deleted or reset to an empty object: `{}`.

P.s. Welcome to the forum.

[edit]  
Without seeing your flow there is not much more to be said , we would be simply guessing.

---

<div class="post-metadata">

**Author:** ![Rulasmur](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rulasmur/32/105351_2.png) [@Rulasmur](https://discourse.nodered.org/u/Rulasmur)\
**Post date:** [10 January 2026 17:16 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/3 "2026-01-10T17:16:55Z")

</div>

This is not something I considered, thanks! However unfortunately, it seems I have already accidentally prevented this issue.

All my pre request functions have some form of:

```auto
msg.headers = {
    ...
};

```

Also this should not cause them to hang right? I could understand the request failing, but these simply freeze, and take node-red with them.

The part that concerns me most is that if I unlink the last http-request, the other nodes start behaving properly. I find it odd that a node down the chain can cause upstream problems

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [10 January 2026 17:25 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/4 "2026-01-10T17:25:23Z")

</div>

All the node use the same underlying http request library so it is possible to confuse the later nodes.  
please post an example flow causing the issue.

---

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [10 January 2026 18:16 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/5 "2026-01-10T18:16:50Z")

</div>

I made my own subflow wrapper around http request node, mostly because I needed a retry mechanic and robust handling of exceptions and errors. But another feature I added was a checkbox to remove headers on output. In almost all cases I faced the return headers are useless.

---

<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:** [10 April 2026 18:17 UTC](https://discourse.nodered.org/t/http-request-node-stuck-on-requesting-causes-flow-to-hang/100138/6 "2026-04-10T18:17:17Z")

</div>

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