# Node-red-alexa-home in docker: setting controller port

**URL:** https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544
**Category:** General
**Created:** [10 October 2019 11:40 UTC](https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544 "2019-10-10T11:40:26Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![zechasso](https://avatars.discourse-cdn.com/v4/letter/z/a87d85/32.png) [@zechasso](https://discourse.nodered.org/u/zechasso)
#### Post date: [10 October 2019 11:40 UTC](https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544/1 "2019-10-10T11:40:26Z")

</div>

Hello,  
this is my first post in this forum.

I'm using NodeRed in a docker an my synology with network in bridge-mode.  
Now I want to use node-red-alexa-home, for which I have to redirect the controller-port from port 80 in my physical networt to port 60000 in my docker.

I've tried to set the ennvironment variable ALEXA\_PORT=80 as described on the GitHub-page, but this was not the solution.  
Actually I get no connection from my Echo to this NodeRed-palette.

Can you tell me how to solve this problem please?

---

<div class="post-metadata">

### Author: ![miker256](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/miker256/32/13042_2.png) [@miker256](https://discourse.nodered.org/u/miker256)
#### Post date: [12 October 2019 00:21 UTC](https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544/2 "2019-10-12T00:21:30Z")

</div>

Did you follow these guides?

> **[node-red-contrib-alexa-local](https://flows.nodered.org/node/node-red-contrib-alexa-local)**
>
> No extra Alexa Skills required. Works directly with Alexa in local network.

> **[node-red-contrib-alexa-home](https://flows.nodered.org/node/node-red-contrib-alexa-home)**
>
> Works directly with Alexa in your local network

---

<div class="post-metadata">

### Author: ![zechasso](https://avatars.discourse-cdn.com/v4/letter/z/a87d85/32.png) [@zechasso](https://discourse.nodered.org/u/zechasso)
#### Post date: [13 October 2019 18:11 UTC](https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544/3 "2019-10-13T18:11:43Z")

</div>

Yes, I've tried the environment variable - but without suxxsess.  
But in den docker it's not possible to call sudo - so I couldn't try the way with iptables.

---

<div class="post-metadata">

### Author: ![domiko96](https://avatars.discourse-cdn.com/v4/letter/d/6de8d8/32.png) [@domiko96](https://discourse.nodered.org/u/domiko96)
#### Post date: [8 March 2020 19:28 UTC](https://discourse.nodered.org/t/node-red-alexa-home-in-docker-setting-controller-port/16544/4 "2020-03-08T19:28:48Z")

</div>

I have exactly the same problem. I was using docker compose with network: host. So I'm not able to forward the ports through docker.  
But  
I think if you are just using a single container you could use the argument -p 60000:80 to change the port. Maybe that will help you.  
I'm still looking for a solution to get it working with the environment variable..
