Kibana container can ping but won't connect to ES container?


#1

I'm trying to setup ELK on one host using docker, but after 2 days and various settings changed, currently Kibana simply refused to connect to ES (or the other way around idk)

Kibana log give out error:

{"type":"log","@timestamp":"2018-07-01T09:53:53Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
{"type":"log","@timestamp":"2018-07-01T09:53:55Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://10.0.9.2:9200/"}

I can ping the IP from inside Kibana container, but curl -XGET http://10.0.9.2:9200 give "no route to host" error.

I can visit the address from my computer and ES is giving out its stats as normal.

Visiting IP:5601 get me Kibana login page with "login is disabled" message (can't connect to ES I think)


(David Pilato) #2

Share your elasticsearch logs (correctly formatted please).


#3

Hello, it's working.

I need to setup a private bridge network for ELK containers and connect them via container interface. I think docker default rule wouldn't allow that.

Somehow I kept thinking this is related to ELK, nothing a couple of beer won't solve.


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.