Setting up echo speaks

I have a windows 10 mini computer and would like to setup echo speaks on it. Can you point me to the full installation process. Maybe using docker .... Also need to know how to setup docker too....Thanks

Docker for windows just requires you to click next a bunch of times to install: Install Docker Desktop on Windows | Docker Docs

Then I would suggest getting portainer: Install Portainer CE with Docker on WSL / Docker Desktop - Portainer Documentation

Here is my guide for setting up echo-speaks on docker.

Just be warned that by default Docker for Windows will allocate 2Gb of RAM. There is a config file that can be manually edited to reduce that if needed (if you system is low on free RAM).

OK. Continue from step 3 since you already have the node server setup.

You should be able to load the config page using the IP address of the node server at port 8091 (http://nodeserverip:8091).

It probably will not work correctly, it looks like you did not set the ipAddress variable as shown in my instructions. If you used portainer stacks it should be in the stack file already if you copied mine, you just need to uncomment and set it.

This should be showing the IP of the host machine.
image

1 Like

Good catch.

@junk7001 You need to fix that before you'll be able to move on.

1 Like

Do I change the IP no the Stack details? Which IP, Gateway or hub ip?

You need to set the IP of the machine the echo-speaks server is hosted on. If you do not already have it set to a reserved IP on your routers DHCP now would be the time to do that also.

Docker only runs in bridge mode on Windows so there is no way around it.

image

I changed the IP to the static IP of the computer from the stack editor, and updated the stack.

Using {http://nodeserverip:8091 1 } = # This site can’t be reached

Try from the host machine that is running docker as a first test - http://localhost:8091

If that works then try from another PC substituting the "localhost" with the IP address.

You could also show me a screen shot from the "Containers" page on portainer.
And check the logs again (you can see those right from Portainer also FYI).

The URL I gave is just an example, where you are supposed to replace nodserserverip with the IP of your ES server. Did you do that? http://192.168.x.x:8091 for example.

yes, I tried it on google and "didn't match any search results"

Tried what on Google? You aren't searching Google for your ES server. You need to enter the server's address in your browser's address bar.

What it the IP address of your Echo Speaks server?

This is how it would look in Chrome if using a server IP of 192.168.1.51.

image

yes I did that

You have the address wrong.

It looks like it should be http://192.168.208.1:8091

Show your most recent docker log that shows what IP it is running at:

Does that IP show 192.168.208.1?

You keep posting with different IP addresses.

What IP is your ES server running at? Is it 192.168.208.1 or 192.168.0.208?

Show your most recent docker log that shows what IP it is running at:

What IP does it show there?

2023-09-18 09:51:31 9-18-2023 - 1:51:31pm error: Config Check Did Not Pass
2023-09-18 09:51:31 9-18-2023 - 1:51:31pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 0.0.0.0 | Port: 8091) | ProcessId: 1 **
2023-09-18 09:51:31 9-18-2023 - 1:51:31pm info: ** On Heroku: (false) **
2023-09-18 09:51:31 9-18-2023 - 1:51:31pm info: Checking for Server Version Updates...
2023-09-18 09:51:34 9-18-2023 - 1:51:34pm info: Server Version is Up-to-Date.

This is your issue. It still shows you are running at 0.0.0.0

You need to update your Portainer stack file to use the IP you have reserved for your ES server. Then restart the ES server container.

You need to uncomment the line where you entered the IP address. Remove the # from line 20. That symbol comments out the code and must be removed.

Remove the # and restart the container. And make sure you use the correct address after for access. You have 192.168.1.208 entered so the url should be http://192.168.1.208:8091. Please verify that is correct, because you've posted different addresses.

2023-09-18 11:12:21 9-18-2023 - 3:12:21pm error: Config Check Did Not Pass
2023-09-18 11:12:21 9-18-2023 - 3:12:21pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 192.168.1.208 | Port: 8091) | ProcessId: 1 **
2023-09-18 11:12:21 9-18-2023 - 3:12:21pm info: ** On Heroku: (false) **
2023-09-18 11:12:21 9-18-2023 - 3:12:21pm info: Checking for Server Version Updates...
2023-09-18 11:12:23 9-18-2023 - 3:12:23pm info: Server Version is Up-to-Date.
2023-09-18 11:13:21 SIGTERM
2023-09-18 11:13:21 clean
2023-09-18 11:13:21 0
2023-09-18 11:13:21 graceful setting timeout for PID: 1
2023-09-18 11:13:32 9-18-2023 - 3:13:32pm error: Config Check Did Not Pass
2023-09-18 11:13:32 9-18-2023 - 3:13:32pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 192.168.1.208 | Port: 8091) | ProcessId: 1 **
2023-09-18 11:13:32 9-18-2023 - 3:13:32pm info: ** On Heroku: (false) **
2023-09-18 11:13:32 9-18-2023 - 3:13:32pm info: Checking for Server Version Updates...
2023-09-18 11:13:35 9-18-2023 - 3:13:35pm info: Server Version is Up-to-Date.