# Sequoia Local Network Access Issue with the http request node

**URL:** <https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266>\
**Category:** General\
**Tags:** http-request, macos\
**Created:** [4 October 2025 16:07 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266 "2025-10-04T16:07:59Z")\
**Posts on this page:** 15\
**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:** [4 October 2025 16:07 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/1 "2025-10-04T16:07:59Z")

</div>

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:

> [@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 tried it, but the last `open /Applications/Node-RED.app` command briefly popped up a generic icon in the dock, but it quickly closed and there was no pop-up to allow it. I checked the Privacy & Security settings and there was no blocked app there to allow.

I tried `sudo spctl --master-disable` and selecting to allow from `Anywhere`, tried opening the "app" again, but the same thing happened.

Does anyone know if there are other necessary (perhaps edge-case) steps to get this to work?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 16:27 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/2 "2025-10-04T16:27:56Z")

</div>

> [@hepcat72](#):
>
> `open /Applications/Node-RED.app`

This is not an app that is distributed by the Node RED Project, so how (or what) did you install exactly?

Node RED is distributed via NPM, so is a Node JS app, (not a native Mac App)

Note : I have a standard Node Red install with Sequoia - zero issues, hence what did you install previously?

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [4 October 2025 16:33 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/3 "2025-10-04T16:33:10Z")

</div>

Open Settings, go to `Privacy and Security`, then `Local Network` and finally check if Node-RED is checked. Not tested (not yet upgraded to Sequoia)

> [@hepcat72](#):
>
> I checked the Privacy & Security settings and there was no blocked app there to allow.

Woops... no idea then

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 16:36 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/4 "2025-10-04T16:36:21Z")

</div>

This is not a standard Node RED install, so Im betting its not been maintained for Sequoia maybe?

Just a guess

---

<div class="post-metadata">

**Author:** ![Aaqu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/aaqu/32/101407_2.png) [@Aaqu](https://discourse.nodered.org/u/Aaqu)\
**Post date:** [4 October 2025 16:36 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/5 "2025-10-04T16:36:25Z")

</div>

same all works with npm for me on Tahoe, and you can always use podman and docker node-red container

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 16:38 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/6 "2025-10-04T16:38:21Z")

</div>

> [@Aaqu](#):
>
> Tahoe

And I should note; I am now running Tahoe. -again with no issues

@hepcat72  
The location you posted is not anything we are aware of - Node RED is not a native app - so not sure what you have

---

<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:** [4 October 2025 16:50 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/7 "2025-10-04T16:50:25Z")

</div>

OK everyone, please note that that "app" is created in a step in the FAQ post I linked to:

> [@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…

Please take a look at that post for the missing context.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 17:01 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/8 "2025-10-04T17:01:40Z")

</div>

OK, that was the missing link.

Ensure the executable `node` and the `app` is allowed to access the local network. - like @GogoVega posted.

 ![Screenshot 2025-10-04 at 18.01.00](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/b/3b5a0ac812df72d4c24b7529ec9a34431a326f3a.png)

Im on the latest Tahoe - but should be the same (Note; I don't have any issues), but use Node RED in a more standard way

---

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

</div>

Alright. I seem to have solved my problem without use of that procedure in the FAQ that I linked to (which creates that "app"). I had seen advice elsewhere that one solution for the network access issue is to simply re-install `node`. Even though I was at the latest version (`v24.9.0`), I did the following and after restarting node-red, I am again able to send to other devices on my network using the http request nodes. Here's my bash history:

```auto
export NVM_DIR="$HOME/.nvm"
[-s "$NVM_DIR/nvm.sh"] && \. "$NVM_DIR/nvm.sh"
nvm -v
nvm current
node -v
nvm deactivate
nvm uninstall v24.9.0
nvm current
nvm install node --reinstall-packages-from=$(nvm current)
node -v
node-red --h
which pm2
pm2 stop node-red
npm install -g --unsafe-perm node-red
node-red --h

```

I will note that there's a [macrumors thread](https://forums.macrumors.com/threads/local-network-access-nightmare.2448144/) that recommends deleting this file (`/Volumes/Macintosh HD/Library/Preferences/com.apple.networkextension.plist`) in recovery mode to reset the local network access settings, but I did not try that. Nor has `node`, `node-red`, or `Node.js` ever shown up in the Local Network settings to "enable it".

I had performed the same node update procedure a week or so ago to resolve this same issue on 2 mac minis. One is still functioning correctly, but this other has had the `EHOSTUNREACH` recur, which I noticed today.

I'm not sure why it popped up again, but after the node re-install, I checked out pm2 and discovered a problem in it's "describe":

```auto
 Divergent env variables from local env 
┌─────────────────┬─────────────────────────────────────────────────────┐
│ TERM_SESSION_ID │ REDACTED │
│ SSH_AUTH_SOCK │ /private/tmp/REDACTED/Listeners │
└─────────────────┴─────────────────────────────────────────────────────┘

```

So I addressed it:

```auto
pm2 -v
which pm2
npm install pm2@latest -g
pm2 update
pm2 -h
pm2 list
pm2 describe node-red
pm2 restart node-red --update-env
pm2 describe node-red

```

I don't know if that's what caused the problem to recur on this one mac mini or whether the error coming up again is due to some lesser usage pattern on this computer that perhaps made macos come down on it? No clue.

If it recurs, I will follow up.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 17:10 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/10 "2025-10-04T17:10:01Z")

</div>

I don't use `pm2` - I tend to stay away from anything that adds layers that adds to the complexity but if it works - hey! I'm game 😃

- install `npm`
- `npm install <packlage>`

im done

---

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

</div>

You know, I've been advised before to switch from using `pm2` as my manager. `pm2` was a part of the procedure I followed when I first started installing/using node-RED. When I did a node-red upgrade a few months ago on one of these mac minis, I tried setting up the manager that's described on this site (I think), but I couldn't get it to work. I don't know why, and I don't remember what the issue was, but I just updated `pm2` at the time and it was easy.

However, `pm2` has been somewhat problematic, because it stops working about 5 minutes after a reboot, so I always have to manually start node-red. I'd be willing to go with whatever is recommended on these macs, but at the moment, I have too much else going on to try and solve the problems I ran into last time. If you know a good setup article, specifically for macos, that uses the process manager you use, I'll bookmark it for when I have the time to migrate from pm2. Thanks!

_Clarification_: When I manually start node-red, I use `pm2` and it's stable from the on after that first crash upon reboot. I.e. It works to restart node-red from then on, when it crashes.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 17:25 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/12 "2025-10-04T17:25:56Z")

</div>

It might come of as bit of a sales pitch, its not intended to be, but it may help.

But if you require Node RED as a service on a Mac.  
Look at my project.

> **[GitHub - marcus-j-davies/Node-RED-SFE: A Single File Executable framework for Node-RED](https://github.com/marcus-j-davies/Node-RED-SFE)**
>
> A Single File Executable framework for Node-RED

1. Compile Node RED as a real executable
2. ensure the executable is aloud to access the network (change of location matters)
3. start it with the built in OSX daemon

`Node` is not even needed on the target system

What you are after, is the Standard Mode, not the emdbeed mode

---

<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:** [4 October 2025 17:34 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/13 "2025-10-04T17:34:36Z")

</div>

You don't use node-red as a service on any mac? I'm a little surprised, but I guess most people don't automate maybe as much as I do? I use Node-RED for all my home automations, which includes managing my security camera system running on one of these minis, email triggers, a ton of reminder triggers, and I even scripted the messages app to text myself home automation messages. A lot of that uses `osascript` to say, complete reminders and such. My reminders scripts use sqlite to "hack" the reminders DB. I have automations that trigger based on an `fswatch` of the DB file, so that me completing a reminder on my phone can trigger automations. It's pretty fuckin' cool if I do say so myself (which is more of a brag than a sales pitch, because I've only posted snippets of my scripts online).

(Oh, but my main automation hub is an rPi, hence the request node usage.)

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 October 2025 17:37 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/14 "2025-10-04T17:37:18Z")

</div>

> [@hepcat72](#):
>
> You don't use node-red as a service on any mac?

Not on Mac - I have an RPi5 doing all the Node Red stuff as a service.  
but use the standard `systemd` API - I like to keep as native possible.

Anything automated/started on boot is on my Pi

---

<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:** [18 October 2025 17:37 UTC](https://discourse.nodered.org/t/sequoia-local-network-access-issue-with-the-http-request-node/99266/15 "2025-10-18T17:37:24Z")

</div>

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