[ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes

Elastic Stack Kibana
1

Hi Team,

I have locally installed elasticsearch and kibana on Mac OS. it was working fine from last 1.5 months . However I am getting below error (while starting kibana) from last week:

Below is elasticsearch detail :

< certs git:(main) ✗ curl --cacert http_ca.crt -u elastic https://localhost:9200
Enter host password for user 'elastic':
{
  "name" : "GTDGCYHY4H",
  "cluster_name" : "pmpelastic",
  "cluster_uuid" : "YJUjHnjwRDm22QO1lSln2w",
  "version" : {
    "number" : "8.6.0",
    "build_flavor" : "default",
    "build_type" : "tar",
    "build_hash" : "f67ef2df40237445caa70e2fef79471cc608d70d",
    "build_date" : "2023-01-04T09:35:21.782467981Z",
    "build_snapshot" : false,
    "lucene_version" : "9.4.2",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"

For kibana:

< ➜  certs git:(main) ✗ curl -v --cacert http_ca.crt -u elastic https://localhost:5601
Enter host password for user 'elastic':
*   Trying 127.0.0.1:5601...
* Connected to localhost (127.0.0.1) port 5601 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: http_ca.crt
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version
* Closing connection 0
curl: (35) error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version />

Please assist me on this and let me know if you need anymore information while working on it.

Regards,
Mausam

2

Did you set up TLS for Kibana? You'd have to do that manually.

What happens if you run curl -v -u elastic http://localhost:5601?

3

Hi Xeraa,

I have installed kibana and Elasticsearch (version 8.6.0 ). I have not done any configuration manually except the basic one. As mentioned before it was working fine for 1.5 months. I already pushed data via Logstash and enable the Machine learning for my use case. Incase you think I should still do TLS setting for kibana. Please provide the link to do the same.

Regards,
Mausam

4

But by default, Kibana doesn't configure TLS (while Elasticsearch is). Are you sure Kibana is accessible through HTTPS rather than HTTP? What happens if you run the command from my previous comment?

1 Like
5

'''
Last login: Mon Feb 27 02:39:22 on ttys005
➜ ~ git:(main) ✗ curl -v -u elastic http://localhost:5601
Enter host password for user 'elastic':

  • Trying 127.0.0.1:5601...
  • Connected to localhost (127.0.0.1) port 5601 (#0)
  • Server auth using Basic with user 'elastic'

GET / HTTP/1.1
Host: localhost:5601
Authorization: Basic ZWxhc3RpYzpyZ3lmNkt4UXZUYTkwRWs3VFdSNA==
User-Agent: curl/7.86.0
Accept: /

  • Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    < x-content-type-options: nosniff
    < referrer-policy: no-referrer-when-downgrade
    < content-security-policy: script-src 'self' 'unsafe-eval'; worker-src blob: 'self'; style-src 'unsafe-inline' 'self'
    < kbn-name: GTDGCYHY4H
    < content-type: text/html; charset=utf-8
    < cache-control: private, no-cache, no-store, must-revalidate
    < content-length: 90299
    < vary: accept-encoding
    < accept-ranges: bytes
    < Date: Mon, 27 Feb 2023 01:45:48 GMT
    < Connection: keep-alive
    < Keep-Alive: timeout=120
    '''
6

Yes, that works — you're getting a 200 back.

I'm not sure what you are trying to do, but this is the right starting point.

7

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