Kibana server is not ready yet error

I am getting an error that is shown below when I visit localhost:5601

Kibana server is not ready yet.

When I enter the command curl -cacert /etc/Elasticsearch/certs/http_ca.crt -u Elasticsearch https://localhost:9200, this is shown below

Here is my Elasticsearch config

network.host: 0.0.0.0
discovery.seed_hosts: ["0.0.0.0"]



# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host: 192.168.0.1
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false

#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 03-03-2022 18:39:06
#
# --------------------------------------------------------------------------------

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["elastic.local"]

# Allow HTTP API connections from localhost and local networks
# Connections are encrypted and require user authentication
http.host: [_local_, _site_]

# Allow other nodes to join the cluster from localhost and local networks
# Connections are encrypted and mutually authenticated
#transport.host: [_local_, _site_]

#----------------------- END SECURITY AUTO CONFIGURATION -------------------------

Here is the top part of Kibana config

Here is the code for _cluster/health?pretty

{
  "cluster_name" : "elasticsearch",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 2,
  "active_shards" : 2,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}

Here is systemctl status kibana.service -L

● kibana.service - Kibana
   Loaded: loaded (/usr/lib/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2022-03-03 14:09:35 CST; 1h 6min ago
     Docs: https://www.elastic.co
 Main PID: 42996 (node)
    Tasks: 11 (limit: 76550)
   Memory: 577.9M
   CGroup: /system.slice/kibana.service
           └─42996 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist

Mar 03 15:15:36 elastic.local kibana[42996]: [2022-03-03T15:15:36.507-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58786, Remote: 127.0.0.1:9200
Mar 03 15:15:39 elastic.local kibana[42996]: [2022-03-03T15:15:39.005-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58794, Remote: 127.0.0.1:9200
Mar 03 15:15:41 elastic.local kibana[42996]: [2022-03-03T15:15:41.525-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58802, Remote: 127.0.0.1:9200
Mar 03 15:15:44 elastic.local kibana[42996]: [2022-03-03T15:15:44.026-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58810, Remote: 127.0.0.1:9200
Mar 03 15:15:46 elastic.local kibana[42996]: [2022-03-03T15:15:46.519-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58818, Remote: 127.0.0.1:9200
Mar 03 15:15:49 elastic.local kibana[42996]: [2022-03-03T15:15:49.018-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58826, Remote: 127.0.0.1:9200
Mar 03 15:15:51 elastic.local kibana[42996]: [2022-03-03T15:15:51.512-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58834, Remote: 127.0.0.1:9200
Mar 03 15:15:54 elastic.local kibana[42996]: [2022-03-03T15:15:54.005-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58842, Remote: 127.0.0.1:9200
Mar 03 15:15:56 elastic.local kibana[42996]: [2022-03-03T15:15:56.518-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58850, Remote: 127.0.0.1:9200
Mar 03 15:15:59 elastic.local kibana[42996]: [2022-03-03T15:15:59.031-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - Local: 127.0.0.1:58858, Remote: 127.0.0.1:9200

Is this related to the a token?

Can you change the config from localhost to host ip (In Kibana and Elastic file) for test? Instead of using 0.0.0.0=localhost use the machine ip? You can block external connection before changing this setting if you are worried about possible external requests.

This error means that kinana cannot establish connection to es.

I updated the config to add this

elasticsearch.hosts: ["https://localhost:9200"]

These are the errors I have now. I believe that 0.0.0.0 will have to be the IP address

● kibana.service - Kibana
   Loaded: loaded (/usr/lib/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2022-03-03 15:50:03 CST; 1min 11s ago
     Docs: https://www.elastic.co
 Main PID: 47860 (node)
    Tasks: 11 (limit: 76550)
   Memory: 466.1M
   CGroup: /system.slice/kibana.service
           └─47860 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist

Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.499-06:00][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recommended.
Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.511-06:00][WARN ][plugins.security.config] 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.
Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.512-06:00][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recommended.
Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.521-06:00][WARN ][plugins.reporting.config] 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.
Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.522-06:00][WARN ][plugins.reporting.config] Found 'server.host: "0.0.0.0"' in Kibana configuration. Reporting is not able to use this as the Kibana server hostname. To enable PNG/PDF Reporting to work, 'xpack.reporting.kibanaServer.hostname: localhost' is automatically set in the configuration. You can prevent th>
Mar 03 15:50:10 elastic.local kibana[47860]: [2022-03-03T15:50:10.568-06:00][INFO ][plugins.ruleRegistry] Installing common resources shared between all indices
Mar 03 15:50:11 elastic.local kibana[47860]: [2022-03-03T15:50:11.038-06:00][WARN ][plugins.screenshotting.config] Chromium sandbox provides an additional layer of protection, but is not supported for Linux Red Hat Linux 8.5 OS. Automatically setting 'xpack.screenshotting.capture.browser.chromium.disableSandbox: true'.
Mar 03 15:50:12 elastic.local kibana[47860]: [2022-03-03T15:50:12.733-06:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. self signed certificate in certificate chain
Mar 03 15:50:13 elastic.local kibana[47860]: [2022-03-03T15:50:13.554-06:00][INFO ][plugins.screenshotting.chromium] Browser executable: /usr/share/kibana/x-pack/plugins/screenshotting/chromium/headless_shell-linux_x64/headless_shell
Mar 03 15:50:13 elastic.local kibana[47860]: [2022-03-03T15:50:13.555-06:00][WARN ][plugins.screenshotting.chromium] Enabling the Chromium sandbox provides an additional layer of protection.

What is the ip of your machine? I mean the IP of the interface that connects the machine with LAN. For example 192.168.1.10. On windows, you can check it with ipconfig in cmd on linux with ip addr.

From my experience, I found that Kibana misbehaves if I use 0.0.0.0. Use localhost or machine IP.

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