"Error: listen EACCES: permission denied 0.0.0.0:80"

[dynamicdave1515]

Just tried your node in Node-RED v0.20.0 and got this error message from the Hub node

"Error: listen EACCES: permission denied 0.0.0.0:80"

[datech]

Ports under 1024 needs Node-Red to be started with root user or you can use docker containers, like Home Assistant is doing to run Node-Red. I will update the documntation to refrect this dowside

[rapejim]

I am running Node-RED with a docker container and I configure the port 80 to be published port:

But I recive the same error:
"Error: listen EACCES 0.0.0.0:80"

[datech]

Is process running with root user inside the docker container?

[rapejim]

It's not running as root:

But, I don't know how change it (inside the container).

[rapejim]

When you release the #2 enhancement, I could configure it on another port (a port that isn't need root access) and redirect that port to external 80 port...
is it right?

[datech]

You may try to override the docker user with --user=root argument on docker run command

This has to switch node-red user to root

https://docs.docker.com/engine/reference/run/#user

PS: Port forwarding of port 80 should be working too

[rapejim]

You may try to override the docker user with --user=root argument on docker run command

This has to switch node-red user to root

https://docs.docker.com/engine/reference/run/#user

PS: Port forwarding of port 80 should be working too

SOLVED!! Y have changed the run user to root (in Portainer, the docker webui) and now it's "conected" without port error.

But Alexa don't discover the new device "Cargador patín"... (I have Echo Dot 3gen). 🤔

[datech]

Could you verify the that you can open the following link which will be served by Amazon Echo Hub Node
http://<node-red-ip-address>:80/description.xml (Just replace the host with your Node-Red IP address)

Echo device will try to access this link during the discovery process

[rapejim]

I have this info:

[datech]

Thanks.

Ok, this is the expected XML.

That’s odd. I suppose, that both Node-Red and Echo are in the same network?

[rapejim]

Node-Red (on a Raspi) and Echo are connected at the same wifi (my unique router).

[datech]

I managed to reproduce it. The problem is that Amazon Echo Hub could not be discovered with SSDP.
If the container is running in isolated network, multicast messages cannot be delivered to it.

In order to fix it you have to select host network while deploying the docker container. Here is how you can do in Portainer:

[rapejim]

I managed to reproduce it. The problem is that Amazon Echo Hub could not be discovered with SSDP.
If the container is running in isolated network, multicast messages cannot be delivered to it.

In order to fix it you have to select host network while deploying the docker container. Here is how you can do in Portainer:

Yeah, this change solve de ports problem.
But when I add new node, (for new device), I must restart NodeRED, then Alexa detect the new device. If I don't restart NodeRED, Alexa don't detect new device...
The Mysteries of Technology 🤣

[dynamicdave1515]

I'm trying out the latest release and wanted to know...
Do you know the port number the Echo Dot Gen-2 listens on (or how I could find that out) ?

[datech]

Echo Dot 2 gen has to be able to connect to any port above 1024.

PS: I don't have Dot 2 Gen to test it.

[datech]

Hello David

I will close this issue as there is a confirmation that the packages is working with Echo Dot 2 Gen.

https://discourse.nodered.org/t/amazon-echo-hub/6724/6

Fill free to open another issue if you find any bug or missing functionality.

Thanks.

[ChazBurkhart]

You may try to override the docker user with --user=root argument on docker run command
This has to switch node-red user to root
https://docs.docker.com/engine/reference/run/#user
PS: Port forwarding of port 80 should be working too

SOLVED!! Y have changed the run user to root (in Portainer, the docker webui) and now it's "conected" without port error.

I'm having this same issue, but I went to that link I have no idea what it's saying. Can you help me dumb it down a bit? I'm still very new to all of this.

[cbrandlehner]

My node-red environment is running non-root and I did not want to change this.

To be able to bind to port 80 you can also use this command to allow non-root processes to bind to port 80.

sysctl -w net.ipv4.ip_unprivileged_port_start=80