Testing out winlogbeat to send syslogs to elastic instance with a kibana front end. kibana status page shows all things are green [1] two network options set in elasticsearch.yml are: network.host: 127.0.0.1 http.port: 9200 I have also tried changing network.host to 0.0.0.0 - but then kibana …

Thanks, that's much better Elasticsearch is listening on 10.68.70.151:9200: [image] littlejob: [2019-07-25T12:04:29,997][INFO ][o.e.h.AbstractHttpServerTransport] [mothership] publish_address {10.68.70.151:9200}, bound_addresses {[::]:9200} It looks like it's working correctly now. However,…

Connectivity issues to Elasticsearch via tcp\9200

Elastic Stack Elasticsearch

dgonzalezp July 25, 2019, 11:49am 11

Ok
Add again the line that I told before (discovery.seed_hosts: ["x.x.x.x"])
dont forget the "" and restart the elasticsearch service.
Then check the logs again.

cURL does not download the Elastic Agent, only on one of our sites in Amsterdam (otherwise cURL works fine)

Topic		Replies	Views
No connection could be made because the target machine actively refused it Elasticsearch	3	2713	September 30, 2021
Cannot connect to elasticsearch but i have connected to kibana Elasticsearch	11	2009	October 1, 2020
No connection could be made because the target machine actively refused it Beats winlogbeat	4	7626	November 11, 2020
ELK basic config Elasticsearch	9	767	September 23, 2019
Cant seem to connect to Elastic Search or Kibana Elasticsearch	8	396	February 13, 2023

Connectivity issues to Elasticsearch via tcp\9200

Related topics