node-red-contrib-alexa-remote2
node-red-contrib-alexa-remote2 copied to clipboard
586837r
unable to authenticate amazon account
https://i.imgur.com/iO7eMhA.png
https://i.imgur.com/bVC29Zv.png
When I type the address "192.168.1.56:3456" into my browser it just fails to load. I can't seem to authenticate my amazon account.
Is your nodered Running in a Docker and if so, have you expose the port in the Docker container?
Is your nodered Running in a Docker and if so, have you expose the port in the Docker container
No, I am not sure how to do that. Did not think of that.
No Docker or no port? And when no Docker, is there a firewall or a other service on port 3456?
@AleksCee I have the same problem. Im running node-red in a Docker Container. Can you please tell me how to expose the port in the Docker Container? I'm just searched the internet for hours and don't find something adequate. Thank in forward.
@vmrv79 in witch environment is your Docker running? I use a Synology NAS and in the GUI you can Setup the Ports. A mapping from local port to „external“ port. If you run the Container per cli you can set it with the -p option: https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose Like: docker run -d -p 1880:1880 -p 3456:3456 ........ To map the nodeRED port 1880 and the port for this node 3456
Alex
@AleksCee
Thank you very much for your support. Im running docker on a Raspberry Pi.
I was able to solve my problem in the meantime.
As a Docker newbie, I was probably on the wrong track and tried in vain to assign port 3456 to my running Node-Red container. This is probably not in the sense of Docker containers and not easily possible. I guess the ports are usually set when the container is first set up.
Solution: Therefore stop the container, delete it and start it again with the same already used command "docker run.... " but then as an addition to the already configured port e.g. "-p 1880:1880" simply add the additional port "-p 3456:3456" to the command.
For example, the command looks like this for me: "docker run -it -p 1880:1880 -p 3456:3456 -v /home/pi/.node-red:/data --name mynodered nodered/node-red:latest".
If you have defined the data folder outside the container beforehand, as strongly recommended, nothing can be lost when deleting and setting up the container again and thus all flows etc. are still there.
I hope I could help some docker beginners with this.
@AleksCee
Thank you very much for your support. Im running docker on a Raspberry Pi.
I was able to solve my problem in the meantime.
As a Docker newbie, I was probably on the wrong track and tried in vain to assign port 3456 to my running Node-Red container. This is probably not in the sense of Docker containers and not easily possible. I guess the ports are usually set when the container is first set up.
Solution: Therefore stop the container, delete it and start it again with the same already used command "docker run.... " but then as an addition to the already configured port e.g. "-p 1880:1880" simply add the additional port "-p 3456:3456" to the command.
For example, the command looks like this for me: "docker run -it -p 1880:1880 -p 3456:3456 -v /home/pi/.node-red:/data --name mynodered nodered/node-red:latest".
If you have defined the data folder outside the container beforehand, as strongly recommended, nothing can be lost when deleting and setting up the container again and thus all flows etc. are still there.
I hope I could help some docker beginners with this.
Can you tell me where to find the directions to change the data storage to a directory outside of the container?
@bertiebeez in the documentation of the nodered Docker installation-guid: https://nodered.org/docs/getting-started/docker#managing-user-data