# Error connecting to Kibana: fail to get the Kibana version **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [April 8, 2025, 11:20am UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903 "2025-04-08T11:20:32Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![lundi](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@lundi](https://discuss.elastic.co/u/lundi)\ **Post date:** [April 8, 2025, 11:20am UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/1 "2025-04-08T11:20:32Z")
I get an error after trying to load the dashboards from Filebeat into Kibana. ```auto filebeat setup --dashboards Loading dashboards (Kibana must be running and reachable) Exiting: error connecting to Kibana: fail to get the Kibana version: fail to parse kibana version (): passed version is not semver: ``` Kibana is running and I can also see the logs populate the Discover page in it. Kibana is on version 8.17.2 and Filebeat is 8.17.3, so they should be compatible. Filebeat and the ELK-Stack are running on the same Ubuntu 24 host. Kibana, Logstash and Elasticsearch are running in Docker containers each, while Filebeat was installed via ```auto curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-8.17.4-amd64.deb sudo dpkg -i filebeat-8.17.4-amd64.deb ``` In `filebeat.yml` I currently have nothing in the Kibana section because the official [Filebeat Quick Start Guide](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html) says `If you plan to use our pre-built Kibana dashboards, configure the Kibana endpoint. Skip this step if Kibana is running on the same host as Elasticsearch.` Please let me know if I should provide more information 🙏 ---
**Author:** ![lundi](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@lundi](https://discuss.elastic.co/u/lundi)\ **Post date:** [April 14, 2025, 8:56am UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/2 "2025-04-14T08:56:36Z")
In case anyone stumbles upon the same problem: It worked after I added the credentials in the Kibana part of `filebeat.yml`. Now I can see the dashboards, but they don't show anything ("No results found") even though I can see the logs on the Discover page. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 15, 2025, 2:33pm UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/3 "2025-04-15T14:33:35Z")
Did you run `filebeat setup -e` I always suggest that and that is part of the [quickstart](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-installation-configuration) as well That loads all the necessary artifacts like templates (schema) etc... When you run... `filebeat setup --dashboards` That _only_ loads the dashboards and will often lead to things not working You might need to "clean up" and try again... ---
**Author:** ![lundi](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@lundi](https://discuss.elastic.co/u/lundi)\ **Post date:** [April 15, 2025, 2:51pm UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/4 "2025-04-15T14:51:33Z")
Thanks for the reply. I don't think i ran `filebeat setup -e` - I probably thought that `filebeat setup --dashboards` would suffice. Can you point me in the right direction regarding "cleaning up"? Would it be enough to delete the indices that were created up until now? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 15, 2025, 3:48pm UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/5 "2025-04-15T15:48:18Z")
> [@lundi](#): > > Can you point me in the right direction regarding "cleaning up"? Would it be enough to delete the indices that were created up until now? Yes, deleting that should do it on the elasticsearch side. > [@lundi](#): > > Kibana is on version 8.17.2 and Filebeat is 8.17.3 typically with versions Beats version \<= Stack Version so technically you should run filebeat 8.17.2 Curious Why you are using Logstash ... that can complicate things.... do you have a reason too instead of Filebeat -\> Elasticsearch ---
**Author:** ![lundi](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@lundi](https://discuss.elastic.co/u/lundi)\ **Post date:** [April 16, 2025, 9:25am UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/6 "2025-04-16T09:25:08Z")
> [@stephenb](#): > > Curious Why you are using Logstash ... that can complicate things.... do you have a reason too It was a requirement from higher up... I guess the idea is to "future-proof" the setup because more and more data sources will be added gradually. I tried `filebeat setup -e` but got this error: ```auto {"log.level":"error","@timestamp":"2025-04-16T11:17:16.220+0200","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/cmd/instance.handleError","file.name":"instance/beat.go","file.line":1594},"message":"Exiting: index management requested but the Elasticsearch output is not configured/enabled","service.name":"filebeat","ecs.version":"1.6.0"} Exiting: index management requested but the Elasticsearch output is not configured/enabled ``` Do I have to change the output in `filebeat.yml` to Elasticsearch temporarily and then change back to Logstash afterwards, or is there another way? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 16, 2025, 1:39pm UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/7 "2025-04-16T13:39:44Z")
> [@lundi](#): > > Do I have to change the output in `filebeat.yml` to Elasticsearch temporarily and then change back to Logstash afterwards, or is there another way? Yes. Also if you are using filebeat \> Logstash\> Elasticsearch The logstash conf needs to be correct > **[Use ingest pipelines for parsing | Elastic Documentation](https://www.elastic.co/docs/reference/logstash/use-ingest-pipelines)** > > When you use Filebeat modules with Logstash, you can use the ingest pipelines provided by Filebeat to parse the data. You need to load the pipelines into... And this > **[Ingest data from Beats with Logstash as a proxy | Elastic documentation](https://www.elastic.co/docs/manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy)** > > This guide explains how to ingest data from Filebeat and Metricbeat to Logstash as an intermediary, and then send that data to your Elastic Cloud Hosted... ---
**Author:** ![lundi](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@lundi](https://discuss.elastic.co/u/lundi)\ **Post date:** [April 24, 2025, 12:26pm UTC](https://discuss.elastic.co/t/error-connecting-to-kibana-fail-to-get-the-kibana-version/376903/8 "2025-04-24T12:26:39Z")
I followed the steps provided by @stephenb and then edited the logstash.conf file as outlined in the second link above. I can now see the dashboards and they seem to work correctly. Thanks again!