Kibana is unable to connect to ElasticSearch

I have been using ELK now for about a year and half. I decided it was time to re-install my lab for better troubleshooting of the main environment. Now I am unable to get kibana to open. Both the Elasticsearch and Logstash respond just fine but the Kibana is not having any of it.

I have Elasticsearch on its own server, Kibana and Logstash share a server.
I have not configured any security at this time, that is the next step.
Kibana gives the error that it is not ready and when I check the logs I see the following

{"type":"log","@timestamp":"2023-02-02T09:05:11-05:00","tags":["info","plugins","taskManager"],"pid":1882,"message":"TaskManager is identified by the Kibana UUID: 108ddb56-1f00-42e6-959e-b737b70f4cd8"}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","security","config"],"pid":1882,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","security","config"],"pid":1882,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","reporting","config"],"pid":1882,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","reporting","config"],"pid":1882,"message":"Chromium sandbox provides an additional layer of protection, but is not supported for Linux CentOS 7.9.2009 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","encryptedSavedObjects"],"pid":1882,"message":"Saved objects encryption key is not set. This will severely limit Kibana functionality. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","actions","actions"],"pid":1882,"message":"APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2023-02-02T09:05:13-05:00","tags":["warning","plugins","alerting","plugins","alerting"],"pid":1882,"message":"APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2023-02-02T09:05:15-05:00","tags":["info","plugins","monitoring","monitoring"],"pid":1882,"message":"config sourced from: production cluster"}
{"type":"log","@timestamp":"2023-02-02T09:05:16-05:00","tags":["info","savedobjects-service"],"pid":1882,"message":"Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations..."}
{"type":"log","@timestamp":"2023-02-02T09:05:16-05:00","tags":["error","savedobjects-service"],"pid":1882,"message":"Unable to retrieve version information from Elasticsearch nodes."}

I have not made any foundational changes to any of the .yml files

Please Guru's of the Stack, what am I missing?

I was able to get this working. After reviewing the Elasticsearch log file I found that I needed to enable the following:

cluster.initial_master_nodes: ["node-1", "node-2"]

in the Elasticsearch.yml file.

I now have access.

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