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

General
1

In this discussion:

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?

2

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.

3

Oh, thanks for the tip!

4

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

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

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?