starwarsfan/edomi-docker

edomi visu not starting... always red rotating circle

Closed this issue · 5 comments

Hi,

My Problem is, that I am able to create visualizations, add buttons, stuff here and there. Everything seems to work fine. But when I try to start the visu, I always get the red rotating circle. Does not matter if the visu is empty (just a text) or full with more complex stuff.
image

My setup:
Running edomi in a docker container.

Image: starwarsfan/edomi-docker:2.03.5

Ports:
22222:22/tcp
3671:3671/udp
50000:50000/udp
50001:50001/udp
81:80/tcp
8080:8080/tcp

Envs:
WEBSOCKETPORT=8080
HOSTIP=192.168.178.253

Restart: On failure

Created and mapped volumes to:
/usr/local/edomi
/var/edomi-backups
/var/lib/mysql

I call the visu with the following url:

http://192.168.178.253:81/visu/

Then I got asked to enter created user credentials:
image

After clicking "OK" I see the red circle

Any ideas here?

Thank you very much

Additional infos:

it has something to do with the web socket. But I don't know, how to solve it.

Chrome console:
image

Both, docker host and docker container (= connected via ssh to edomi) are listening on port 8080
image

Ok, next information:
image

If you look closely, the host of this port listening differs. 127.0.0.1:8080 means, that this container is only accepting connections from same machine. But this is not the case.

When I try to modify the setting in the edomi.ini, the changes are written back to "127.0.0.1" after each restart of the container. So where is the data coming from?
image

Tada. Solved 😄
image

The error in my case was in the file /root/start.sh in the docker container. See here:
image

This line overwrites the visu ip permanently to 127.0.0.1
So I changed it to the following:
image

and after that, the visu is working! And looking at the port binding:
image

Now it is listening to connections from outside.

I can't imagine that I am the only one with that problem?! Found nothing in the support forum.

Well, you did not read the documentation correctly. Otherwise you would have found that you're missing an important env var. ;-)

And this variable would be which one?