# Flow collector doesnt recieve flows

**URL:** <https://forum.elastiflow.com/t/flow-collector-doesnt-recieve-flows/336>\
**Category:** ElastiFlow Community\
**Tags:** flow-collector\
**Created:** [October 3, 2025, 8:16am UTC](https://forum.elastiflow.com/t/flow-collector-doesnt-recieve-flows/336 "2025-10-03T08:16:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennis](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@dennis](https://forum.elastiflow.com/u/dennis)\
**Post date:** [October 3, 2025, 8:16am UTC](https://forum.elastiflow.com/t/flow-collector-doesnt-recieve-flows/336/1 "2025-10-03T08:16:57Z")

</div>

Im running elastic stack, kibana and Netobserve on ubuntu 24.04. Elasticsearch and Kibana are both up, howver i’m getting this error in journalctl on flowcoll service.

{“level”:“error”,“ts”:“2025-10-03T11:13:42.546+0300”,“logger”:“flowcoll.bootstrapper[elasticsearch]”,“caller”:“elasticsearch/bootstrap.go:152”,“msg”:“failed to bootstrap elasticsearch. retrying…”,“code”:“elasticsearch/bootstrap-failure”,“reason”:“error while creating default ilm policy: error while checking if ilm policy exists: error while checking ilm policy ‘elastiflow’ exists: Get “[https://127.0.0.1:9200/\_ilm/policy/elastiflow\”:](https://127.0.0.1:9200/_ilm/policy/elastiflow%5C%E2%80%9D:) tls: failed to verify certificate: x509: certificate is valid for 192.168.68.9, not 127.0.0.1”,“stacktrace”:“[github.com/elastiflow/flowcoll/pkg/outputs/elasticsearch.(\*Bootstrap).Run](http://github.com/elastiflow/flowcoll/pkg/outputs/elasticsearch.(*Bootstrap).Run)\n\t/tmp/collectors/pkg/outputs/elasticsearch/bootstrap.go:152\ngithub.com/elastiflow/flowcoll/pkg/outputs/elasticsearch.NewInstantiatorRegistration.newCreateInstanceFunc.func1\n\t/tmp/collectors/pkg/outputs/elasticsearch/instance\_registration.go:165\ngithub.com/elastiflow/go-env-conf/instantiator.(\*Instantiator).Run\n\t/go/pkg/mod/github.com/elastiflow/go-env-conf@v0.8.11/instantiator/instantiator.go:81\ngithub.com/elastiflow/flowcoll/pkg/apps/unified\_flowcoll.(\*App).Run\n\t/tmp/collectors/pkg/apps/unified\_flowcoll/app.go:170\nmain.main\n\t/tmp/collectors/cmd/flowcoll/main.go:106\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:272”}

Tried checking all YAML files (elasticsearch, kibana and netobserve ) for wrong paths to certificate or incorrect definition of server IP address.

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [October 3, 2025, 12:05pm UTC](https://forum.elastiflow.com/t/flow-collector-doesnt-recieve-flows/336/2 "2025-10-03T12:05:50Z")

</div>

The error is telling you that the flowcoll service is trying to connect to Elasticsearch at [https://127.0.0.1](https://127.0.0.1) but the certificate it is using is for 192.168.68.9. You probably need to change the EF\_OUTPUT\_ELASTICSEARCH\_ADDRESSES setting in flowcoll.yml from 127.0.0.1:9200 to 192.168.68.9:9200.

Let us know if that helps.

Regards,

Dexter

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.elastiflow.com/system/32/59_2.png) [@system](https://forum.elastiflow.com/u/system)\
**Post date:** [November 2, 2025, 12:06pm UTC](https://forum.elastiflow.com/t/flow-collector-doesnt-recieve-flows/336/3 "2025-11-02T12:06:28Z")

</div>

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