Closed GuillaumeCyber closed 4 years ago
Actually I just realized that I can log in by using:
http://elasticsearch:9200
http://172.21.0.3:9200
So I'm wondering why it's not working with:
http://localhost:9200
http://127.0.0.1:9200
And why it raises an exception (error message) instead of a classic log message for a bad "Node address"? Thanks,
If cerebro and elasticsearch are running as docker containers, each of them are assigned an ip. So, for cerebro localhost
refers to its local. To mitigate this in local development you can use host driver instead of bridge see here ( I think host driver doesn't work if you are a mac user though)
Hi,
I contact you because, after several attempts, I got an error when trying to access elasticsearch from cerebro web interface
############# Here are some info on my config:
#############
For information, Elasticsearch is running in a dedicated container on the same machine in "single-mode" and by doing:
curl -X GET "localhost:9200/_cat/nodes?v&pretty"
we get:So basically the problem I'm facing appears when I'm filling in the "Node Adress" field with http://localhost:9200. Each time I got the following error message in the console:
If I fill in the "Node address" with "http://localhost:9200" and I check on docker logs, I got the following message:
If I fill in the "Node address" with "localhost:9200", cerebro raises an unexpected exception for a bad address:
For information I build my elastic stack from a docker-compose.yml file where I put the following information for Cerebro:
In the project directory I have a cerebro folder which contains: your Dockerfile and a config folder which contains application.conf file. To debug I removed all authentication mechanism and so my application.conf file looks like:
If you need more details, feel to ask me. Thanks in advance,