search

sherifabdlnaby / elastdocker

🐳 Elastic Stack (ELK) v8+ on Docker with Compose. Pre-configured out of the box to enable Logging, Metrics, APM, Alerting, ML, and SIEM features. Up with a Single Command.
https://towardsdatascience.com/running-securing-and-deploying-elastic-stack-on-docker-f1a8ebf1dc5b
MIT License
1.81k stars 320 forks source link

Exiting: error connecting to Kibana: fail to get the Kibana version: fail to parse kibana version (): passed version is not semver: #112

Closed alsoGAMER closed 9 months ago

alsoGAMER commented 9 months ago

After discussing with an Elastic team member over on the Elastic forum, they came with the conclusion that my specific issue could be caused by some specific configuration added by this project.

https://discuss.elastic.co/t/exiting-error-connecting-to-kibana-fail-to-get-the-kibana-version-fail-to-parse-kibana-version-passed-version-is-not-semver/353450

Describe the bug winlogbeat is unable to connect to the kibana instance

To Reproduce Steps to reproduce the behavior:

  1. Deploy the stack
  2. Import the CA certificates into the windows machine
  3. Run winlogbeat setup -e
  4. See error

Expected behavior It should just work

sherifabdlnaby commented 9 months ago

I believe Kibana is failing to start and hence your setup is not getting the response it expects; unfortunately, there is not enough context to be able to debug your issue. Please try adding more information and check if Kibana is up and running. What is the container status? What do you see on a browser page when it loads up, etc?

I'll go ahead and close this ticket -for now- as I am unable to find a specific bug to address, please re-open if you still believe there is a bug in Elastdocker setup itself.