# Followup to: Sequoia Local Network Access Issue with the http request node

**URL:** <https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520>\
**Category:** General\
**Created:** [27 October 2025 15:44 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520 "2025-10-27T15:44:47Z")\
**Posts on this page:** 5\
**Page:** 1

<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:** [27 October 2025 15:44 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520/1 "2025-10-27T15:44:47Z")

</div>

In this discussion:

> [@Sequoia Local Network Access Issue with the http request node](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266):
>
> I recently updated 2 mac minis to Sequoia and after doing so, none of my http request nodes would work. They all had EHOSTUNREACH errors. After updating node and node-RED to the latest versions, one of the 2 minis still has no issue. The other (which uses those nodes less frequently) appeared to be fixed at first, but I just opened it up today and it's not working again. I found this post in the FAQ: I tried it, but the last open /Applications/Node-RED.app command briefly popped up a gene…

I referenced that I would followup if the issue recurred. It has recurred and I again fixed it this morning by re-installing node (updating to v25.0.0 in the process).

I don't understand the cause of the recurrence of the `EHOSTUNREACH` error, but my understanding is that either `node` (or `node-red`?) needs to be added to System Settings \> Security & Privacy \> Local Network.

I have no firewall running on this computer. Based on my related issues with Apple's security features that I have dealt with in the past, each process has to be explicitly granted various permissions and it does this via the executable. If that executable ever changes, those permissions have to be redone. An easy example of this is "apps" created using Apple's Script Editor app. If you ever touch the underlying script, permissions must be redone. I ultimately worked around that by switching to using `osascript` and saving my scripts in a text file.

The problem is that I can manually add apps/executables to some permissions, but not in the Local Network pane. App developers have to "do something" to make things show up in that system settings pane. I don't know what has to be done, but I'm familiar with the behavior for apps that do show up there:

1. You run the app
2. When you do something that needs local network access, you get a popup asking to grant permission to access the network.
3. You click something like "always allow"
4. The app shows up in the system prefs for Local Network

I think the problem is that the executable needs to be packaged somehow. The "node-red" executable though is a "script", which is what lead me to focus on the `node` executable as a means of solving the issue. And somehow, the executable ends up getting permissions magically even though it doesn't show up in the Local Network pane in the system settings.

So one idea I've had is to maybe (abstract idea here - I'm not literally suggesting this because I don't know how to do it) move the node (or node-red) "executable" into an apple app package. Maybe the granted permission would have somewhere to live in that "package" container.

Are other people having this issue and know any solutions to prevent the `EHOSTUNREACH` error from eventually recurring? Or does anyone have a more efficient solution as opposed to re-installing node?

---

<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:** [27 October 2025 16:43 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520/2 "2025-10-27T16:43:10Z")

</div>

> [@hepcat72](#):
>
> updating to v25.0.0 in the process)

Don't do that, stick with a max of 24, which is a long term support version. You will almost certainly have problems with odd numbered versions.

---

<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:** [27 October 2025 17:07 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520/3 "2025-10-27T17:07:44Z")

</div>

Oh, thanks for the tip!

---

<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:** [27 October 2025 17:21 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520/4 "2025-10-27T17:21:11Z")

</div>

I think I need to try to revisit this FAQ and see if I can get it to work this time:

> [@Node-RED on Mac OS Sequoia - local network access issues](https://discourse.nodered.org/t/node-red-on-mac-os-sequoia-local-network-access-issues/97139):
>
> I had given up on getting Node-RED to run properly on my Mac after upgrading to Sequoia. The new Mac security protections that prevent local network access unless explicitly granted to applications is a real nightmare. I recently asked perplexity.ai for help. Using its basic model, it gave me some suggestions that did not work. I switched to using its "research" model, though, and hit pay dirt. I finally settled on this workaround and thought I would share it here in case it's of use to oth…

I had tried it awhile back, unsuccessfully, as described here:

> [@Sequoia Local Network Access Issue with the http request node](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266):
>
> I recently updated 2 mac minis to Sequoia and after doing so, none of my http request nodes would work. They all had EHOSTUNREACH errors. After updating node and node-RED to the latest versions, one of the 2 minis still has no issue. The other (which uses those nodes less frequently) appeared to be fixed at first, but I just opened it up today and it's not working again. I found this post in the FAQ: I tried it, but the last open /Applications/Node-RED.app command briefly popped up a gene…

But the last step failed. I never got the permissions popup. I think it takes the right approach though. Has anyone else been able to get it to work or does that pseudo-`Node-RED.app` fail to launch like mine did when I tried it?

---

<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:** [25 January 2026 17:21 UTC](https://discourse.nodered.org/t/followup-to-sequoia-local-network-access-issue-with-the-http-request-node/99520/5 "2026-01-25T17:21:22Z")

</div>

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