MacOS Sequoia and node-red-contrib-ftp

I upgraded MacOS to Sequoia last week and I have a simple flow that has worked for ages that now doesn't work. The ftp node returns an error - EHOSTUNREACH 192.169.1.xxx:21. I can ftp from this Mac using FileZilla to the NAS at the IP address above using the same user/password. The flow is reading a file on the local drive and doing an ftp "put" - the file does exist.

I think it may have something to do with expressly granting permissions to access the local network but I can't figure out how to give Node-RED and/or the ftp node access to that. Any help would be really appreciated. Thanks

Hi @rakgupta

Check OSX Settings -> Privacy & Security -> Local Network
and check that the Node executable has the access.

Access won't be specific to a single Node RED node (or even Node RED itself) - but more the process running it all (Node)

If using Docker however - then others may provide guidance, I (and most here) don't use docker

1 Like

Hmm - on mine Node doesn't have access. There appears to be no way to "add" an application to this panel either.

I would check your network or FTP node settings

I have no issue accessing any network resources via Node RED.
(it's also not listed on allowed connections - so maybe its not related)

  • Node RED : 4.0.5
  • OSX Sequoia 15.0.1

1 Like

Thanks so much for testing this out. I will continue to see why it's not working for me. My Node-RED is v3.1.9, MacOS is 15.1.1.

I also tried the node-red-contrib-fs-ops to "move" the file to the NAS and that did not work either. It had no issues moving the file from local directory to another local directory, so I'm assuming it is something to do with local network access again or network drive paths are treated in by this node (the mv command line from Terminal works perfectly)

What is the exact name of the ftp node you are using? If you click on the Flow tab here on the forum and then do a search with ftp it returns 23 nodes, so knowing the exact node would be helpful.

As for node-red-contrib-fs-ops it hasn't been updated in 4 years and the author hasn't been replying to issues that have been opened on GitHub

You also might want to try updating your Node-RED version.

@zenofmud - I don't think the issue is with the node-red-contrib-fs-ops or the node-red-contrib-ftp nodes. I'm running node-red via PM2 on launch and when I stopped that and ran it from the terminal window, the ftp did work. So it's something do with with processes started from launchd (which is how PM2 is started on boot).

Got it working - I updated/re-installed PM2 and that appears to have fixed it :man_shrugging:t2:

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