[GUIDE] Echo Speaks Server on Docker (or without)

NewbHub · June 25, 2026, 2:13pm

It certainly looks that way, but how? It seems to flip every 6 or 7 iterations. See log below.

Also, I get the same 404 result regardless of phone vs PC, Chrome Incognito vs Edge InPrivate.

6-25-2026 - 2:06:06pm info: -- Echo Speaks Web Service Starting Up! Takes about 10 seconds before it's available... --

getRemoteCookie...

6-25-2026 - 2:06:06pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 192.168.1.2 | Port: 8091) | ProcessId: 1 **

6-25-2026 - 2:06:06pm info: ** On Heroku: (false) **

6-25-2026 - 2:06:06pm info: Checking for Server Version Updates...

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

6-25-2026 - 2:06:07pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:07pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:07pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

6-25-2026 - 2:06:10pm info: Server Version is Up-to-Date.

getRemoteCookie...

6-25-2026 - 2:06:11pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:06:11pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:11pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:11pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:06:21pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:06:21pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:21pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:22pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:06:31pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:06:32pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:32pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:32pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:06:41pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:06:42pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:42pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:42pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:06:52pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:06:52pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:06:52pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:06:53pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

6-25-2026 - 2:06:55pm info: Server Wakeup Received | Reason: (runCookieRefresh)

getRemoteCookie...

6-25-2026 - 2:07:02pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:07:02pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:07:02pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:07:03pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

6-25-2026 - 2:07:04pm debug: set host url: 192.168.1.2

getRemoteCookie...

6-25-2026 - 2:07:04pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 192.168.1.2:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:07:04pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://192.168.1.2:8091/ with your browser.

6-25-2026 - 2:07:04pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:07:04pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

6-25-2026 - 2:07:12pm debug: set host url: 127.0.0.1

getRemoteCookie...

6-25-2026 - 2:07:12pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:07:13pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:07:13pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:07:13pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:07:23pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:07:23pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:07:23pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:07:23pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

getRemoteCookie...

6-25-2026 - 2:07:33pm debug: config(/) page requested

Alexa-Cookie: Use as Login-Amazon-URL: amazon.com

Alexa-Cookie: Use as Base-Amazon-URL: amazon.com

Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Alexa-Cookie: Use as Accept-Language: en-US

Alexa-Cookie: Proxy-Mode enabled if needed: 127.0.0.1:8091 to listen on 0.0.0.0

Proxy Init: loaded temp data store ■■■ fallback former data

Proxy Init: reuse frc from former data

Proxy Init: reuse map-md from former data

Proxy Init: reuse deviceId from former data

6-25-2026 - 2:07:33pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://127.0.0.1:8091/ with your browser.

6-25-2026 - 2:07:33pm debug: Alexa Login Status: There was an error

6-25-2026 - 2:07:34pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

Here is my config file (pardon the odd tab placements, the block quotes option keeps messing up the formatting):

services:
echo-speaks-server:

#worked until May 2026
#image: echo-speaks-server:2.7.2
#20260623 attempt to address 404 error when manually logging into Amazon
# Build image for non-amd64 systems
build: https://github.com/tonesto7/echo-speaks-server.git
#build:
#  context: ../
container_name: echo-speaks-server
restart: always
logging:
        driver: "json-file"
        options:
            max-size: "50m"
# Network mode host allows IP to be automatically detected
# Windows MUST change from host to bridge mode and set IP in settings below
network_mode: host
#network_mode: bridge
# Port mappings are ignored with host mode
ports:
  - 8091:8091   # WebUI must match PORT below
  
#env_file:
#  - './env.echo-speaks-server'

environment:
  - useHeroku=false
  - hubPlatform=Hubitat

  #### UNCOMMENT Options to use them (remove the # and keep the -) ####
  ## Host IP Address Override if needed
  ## MUST Uncomment next line and set IP when using network_mode: bridge
  - ipAddress=192.168.1.2
  ##was used with v2.7.2
  #- IPAddressOverride=192.168.1.2

  ## Change WebUI Port if needed
  #- PORT=8091

  ## Set callback URL here if you want
  #- appCallbackUrl=

  ## Set amazon domain and locale if need to change from default
  #- amazonDomain=amazon.com
  #- regionLocale=en-US
  - HOME=/mnt/es-data
healthcheck:
  test: "curl -sS 127.0.0.1:8091 -o /dev/null"
  interval: 10s
  timeout: 10s
  retries: 5      
volumes:
  # Data persistency
  - echo-speaks-server:/mnt/es-data

volumes:
  echo-speaks-server:
    external: true

Yes, I had pasted the wrong screenshot in the other thread. My hub didn’t change IP’s.

Here is the screenshot:

tray_e · June 25, 2026, 2:28pm

No, at the bottom of your Echo Speaks Server page, the callback URL should be your HUB address with an access token. See the image I posted with the red circle.

NewbHub · June 25, 2026, 2:35pm

Oh! Sorry…

It had the cloud API callback url since the beginning, but I just replaced it with the local IP. Same 404 error.

I am going to attempt to manually add the token…I just have to find the instructions.

jkudave · June 25, 2026, 2:40pm

You have a double // in the call back URL.

NewbHub · June 25, 2026, 2:46pm

Thank you for being patient with me. I fixed that but I still see the 404 error.

kahn-hubitat · June 25, 2026, 3:06pm

try adding an ipAddress parameter to your config for your container.. i believe i had to do that..

jkudave · June 25, 2026, 3:49pm

Not sure if this helps any, but this is my Docker YAML from when I ran ES servers on my Synology NAS. I've removed or Xed out sensitive info. Sorry if the formatting gets a little wonky in the post.

version: "3"
services:
echo-speaks-server:
container_name: echo-speaks-server
#image: tonesto7/echo-speaks-server
# Replace image definition with build for non-amd64 systems
build: GitHub - tonesto7/echo-speaks-server · GitHub
restart: unless-stopped

# Network mode host allows IP to be automatically detected
# Windows MUST change from host to bridge mode and set IP in settings below
network_mode: host
#network_mode: bridge
# Port mappings are ignored with host mode
ports:
  - 8091:8091   # WebUI must match PORT below

# Set environment variables
environment:
  - useHeroku=false
  - hubPlatform=Hubitat

  #### UNCOMMENT Options to use them (remove the # and keep the -) ####
  ## Host IP Address Override if needed
  ## MUST Uncomment next line and set IP when using network_mode: bridge
  #- ipAddress=192.168.1.XXX

  ## Change WebUI Port if needed
  #- PORT=8091

  ## Set callback URL here if you want
  - appCallbackUrl=http://192.168.xx.x/apps/api/13x/receiveData?access_token=

  ## Set amazon domain and locale if need to change from default
  #- amazonDomain=amazon.com
  #- regionLocale=en-US

# Keeps login and session if re-deployed
volumes:
  - /volume1/docker/echospeaks/etc-root:/root

volumes:
data: {}

NewbHub · June 25, 2026, 4:22pm

I had that set up from the beginning.

The IP address is specified in my Compose/Portainer Stack.

Any other ideas?

kahn-hubitat · June 25, 2026, 4:54pm

that is very weired that it is showing 127.0.0.1 whaen you goto http://192.168.1.2:8091 what page comes up?

jkudave · June 25, 2026, 5:11pm

See if any of this helps:

When a Docker container appears to be using or showing the local loopback address (127.0.0.1) instead of its expected configured IP address, it is usually due to one of a few common networking configurations.

Here are the most likely reasons why this is happening:

1. The Container is Using `host` Network Mode

If you started the container with --network=host (or network_mode: "host" in Docker Compose), the container does not get its own isolated network namespace or its own IP address.

What happens: It shares the host machine’s network stack entirely.
The result: Any service inside the container binding to localhost or 127.0.0.1 is binding directly to the host's loopback interface, and ifconfig or ip a inside the container will mirror the host's interfaces.

2. The Service Inside the Container is Bound to `127.0.0.1`

If you are looking at the logs of the application running inside the container (e.g., a Flask, Node.js, or Nginx server) and it says Listening on [http://127.0.0.1:8080](http://127.0.0.1:8080), this is an application configuration issue.

What happens: When an app inside a container binds strictly to 127.0.0.1, it will only accept traffic originating from within that exact same container. Docker’s bridge network will not be able to route external traffic to it.
The fix: Change your application's configuration to bind to 0.0.0.0 (all available interfaces) instead of 127.0.0.1.

3. The Network Mode is Set to `none`

If the container was accidentally configured with --network=none, Docker intentionally isolates it from all external networks.

The result: The only network interface created inside the container will be the local loopback (lo) interface with the address 127.0.0.1.

4. Port Mapping Misunderstanding (`-p 127.0.0.1:80:80`)

If you are checking docker ps from your host machine and you see 127.0.0.1:80->80/tcp, this is actually normal behavior if explicitly configured.

What happens: You explicitly told Docker to only bind the exposed container port to the host's loopback interface so that it isn't accessible from the outside world. The container itself still has a internal bridge IP (like 172.17.0.x), but the host is only routing 127.0.0.1 traffic to it.

NewbHub · June 25, 2026, 8:36pm

Thanks for the info. I never had to mess with the network settings when I set it up the first time. I decided to just bridge the network. It finally presented the Amazon login page, but even so, the ES-server log actually shows the IP address still flipping back and forth between the correct IP and the loopback. See log below.

From what I can tell, the hostname (from the request header) in index.js is the one getting changed. At this point, I don’t want to jinx it and I have to wait 24 hrs anyway to try things again. So, I appreciate the responses from everyone!

6-25-2026 - 7:02:45pm info: -- Echo Speaks Web Service Starting Up! Takes about 10 seconds before it's available... --

getRemoteCookie...

6-25-2026 - 7:02:45pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 192.168.1.2 | Port: 8091) | ProcessId: 1 **

6-25-2026 - 7:02:45pm info: ** On Heroku: (false) **

6-25-2026 - 7:02:45pm info: Checking for Server Version Updates...

6-25-2026 - 7:02:46pm info: ** Retrieved Alexa Cookie Data from Hubitat Cloud Endpoint Successfully! **

6-25-2026 - 7:02:46pm info: ** Alexa Cookie Data Received from Hubitat Cloud Endpoint has been Confirmed to be Valid! **

6-25-2026 - 7:02:46pm debug: Alexa Login Status: Login Successful (Retreived from Hubitat)

6-25-2026 - 7:02:46pm silly: Echo Speaks Alexa API is Actively Running at (IP: 192.168.1.2 | Port: 8091) | ProcessId: 1

6-25-2026 - 7:02:46pm error: AlexaGuardDataSupport | No Alexa Guard Appliance Data found...

6-25-2026 - 7:02:46pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

6-25-2026 - 7:02:49pm info: Server Version is Up-to-Date.

6-25-2026 - 7:02:51pm debug: config(/) page requested

6-25-2026 - 7:03:01pm debug: config(/) page requested

6-25-2026 - 7:03:03pm debug: set host url: 192.168.1.2

6-25-2026 - 7:03:03pm debug: config(/) page requested

6-25-2026 - 7:03:11pm debug: set host url: 127.0.0.1

6-25-2026 - 7:03:11pm debug: config(/) page requested

6-25-2026 - 7:03:22pm debug: config(/) page requested

6-25-2026 - 7:03:32pm debug: config(/) page requested

6-25-2026 - 7:03:42pm debug: config(/) page requested

6-25-2026 - 7:03:53pm debug: config(/) page requested

6-25-2026 - 7:04:03pm debug: config(/) page requested

6-25-2026 - 7:04:03pm debug: set host url: 192.168.1.2

6-25-2026 - 7:04:03pm debug: config(/) page requested

6-25-2026 - 7:04:13pm debug: set host url: 127.0.0.1

6-25-2026 - 7:04:13pm debug: config(/) page requested

6-25-2026 - 7:04:23pm debug: config(/) page requested

6-25-2026 - 7:04:34pm debug: config(/) page requested

6-25-2026 - 7:04:44pm debug: config(/) page requested

6-25-2026 - 7:04:54pm debug: config(/) page requested

6-25-2026 - 7:05:03pm debug: set host url: 192.168.1.2

6-25-2026 - 7:05:03pm debug: config(/) page requested

6-25-2026 - 7:05:04pm debug: set host url: 127.0.0.1

6-25-2026 - 7:05:04pm debug: config(/) page requested

6-25-2026 - 7:05:14pm debug: config(/) page requested

6-25-2026 - 7:05:25pm debug: config(/) page requested

6-25-2026 - 7:05:35pm debug: config(/) page requested

6-25-2026 - 7:05:45pm debug: config(/) page requested

6-25-2026 - 7:05:55pm debug: config(/) page requested

6-25-2026 - 7:06:03pm debug: set host url: 192.168.1.2

6-25-2026 - 7:06:03pm debug: config(/) page requested

6-25-2026 - 7:06:05pm debug: set host url: 127.0.0.1

6-25-2026 - 7:06:05pm debug: config(/) page requested

6-25-2026 - 7:06:16pm debug: config(/) page requested

6-25-2026 - 7:06:26pm debug: config(/) page requested

6-25-2026 - 7:06:36pm debug: config(/) page requested

6-25-2026 - 7:06:46pm debug: config(/) page requested

6-25-2026 - 7:06:57pm debug: config(/) page requested

6-25-2026 - 7:07:03pm debug: set host url: 192.168.1.2

6-25-2026 - 7:07:03pm debug: config(/) page requested

6-25-2026 - 7:07:07pm debug: set host url: 127.0.0.1

6-25-2026 - 7:07:07pm debug: config(/) page requested

6-25-2026 - 7:07:17pm debug: config(/) page requested

6-25-2026 - 7:07:19pm debug: set host url: 192.168.1.2

6-25-2026 - 7:07:19pm debug: /config page requested

6-25-2026 - 7:07:19pm info: Checking for Server Version Updates...

6-25-2026 - 7:07:21pm info: Server Version is Up-to-Date.

6-25-2026 - 7:07:27pm debug: set host url: 127.0.0.1

6-25-2026 - 7:07:27pm debug: config(/) page requested

6-25-2026 - 7:07:38pm debug: config(/) page requested

6-25-2026 - 7:07:48pm debug: config(/) page requested

phillypan · July 7, 2026, 10:00pm

So I think I got everything set up regarding docker. But when I go to EchoSpeaks on the Hubitat, it is showing this. And if I click it, it takes me to the blank There is nothing here page, on Heroku. My local server is set up, and I am able to get to that, and log in to amazon fine there. I guess what I am missing is how to connect the two? On the hubitat it says local server connected, as you can see.

jtp10181 · July 8, 2026, 1:24am

You deployed to Heroku via the echo speaks app. You need to reset the settings (its an option in there somewhere) and pick the option for a local server.

phillypan · July 8, 2026, 12:25pm

I ended up getting it sorted out. I could not get rid of that Heroku link, no matter how many times I cleared it. Finally uninstalled ES, reboot hub, then it all clicked and worked. So I am glad to say I am local now. My next question is, is the cookie holding longer local? Or is it still an issue?

marktheknife · July 8, 2026, 8:26pm

Something’s up even with local cookie refresh servers these days, presumably due to too many changes on Amazon’s end since the echo speaks code was last updated.

You can review some of the posts from the last few weeks in this thread to see how some have worked around the most recent issues:

lados · July 23, 2026, 2:08am

I’ve been trying to find a fix for refreshing the Echo Speaks / amazon cookie. I have the echo speaks server set up and running on Synology Docker and it was running great until a month or so ago. Then it just started getting 408 and Authentication errors, and it seems the cookie isn’t refreshing itself any more. I’ve been trying to find a fix for weeks and can’t seem to make anything work. Could someone please help steer me in the right direction to get it working correctly.

Echo Speaks

Cookie Status:

Auth Status:(✓)
• Cookie:(✓)
• CSRF Value:(✓)

Cookie Refresh:(✕)
• Last Refresh: (6 days, 2 hours ago)
• Next Refresh: (363 days, 21 hours, 29 mins)

Cookie Service Management

jkudave · July 23, 2026, 11:15am

Something changed on the amazon side of things that broke the auto cookie refresh. You will need to periodically manually login to Amazon and refresh the cookie.

Have you looked at the recent posts in this thread at all?

That should give you what you need. There are several options. The easiest, in my opinion, is to modify the ES app code to allow you to modify the cookie refresh time.

The alternative is, leave everything alone. If the app is working and you get your announcements/notifications, etc. on your Echo devices the cookie not auto refreshing is not a big deal. Several people have posted that they have gone months without a cookie refresh without issue.

lados · July 23, 2026, 3:45pm

Yes, I went through every post (>2K posts), not only on this thread, but on several other echo speaks threads. Its very frustrating trying pick pieces out of the puzzle that may work. It seems to be working, but with annoying error messages from Synology Docker to my email. I can’t seem to stop the messages, since Synology identifies this as a “critical” error.

There seems like there would be a straight-forward process to make the refresh work or to do away with it. I’m sure those with little experience struggle just like me, but it definitely not the end of the world…

jkudave · July 23, 2026, 3:47pm

Unfortunately, it's not that simple/easy. If you follow one of the workaround methods, you should be able to avoid getting the email alerts.

lados · July 23, 2026, 4:16pm

Yep- The problem is first identifying the workaround methods, then trying each one until you find one that “may” work. Its a 2K+ piece puzzle that I can’t quite make fit. Ugh….

[GUIDE] Echo Speaks Server on Docker (or without)

1. The Container is Using host Network Mode

2. The Service Inside the Container is Bound to 127.0.0.1

3. The Network Mode is Set to none

4. Port Mapping Misunderstanding (-p 127.0.0.1:80:80)

Cookie Service Management

1. The Container is Using `host` Network Mode

2. The Service Inside the Container is Bound to `127.0.0.1`

3. The Network Mode is Set to `none`

4. Port Mapping Misunderstanding (`-p 127.0.0.1:80:80`)