Access Kibanaedit

The fastest way to access Kibana is to use our hosted Elasticsearch Service. If you installed Kibana on your own, access Kibana through the web application.

Set up on cloudedit

There’s no faster way to get started than with our hosted Elasticsearch Service on Elastic Cloud:

  1. Get a free trial.
  2. Log into Elastic Cloud.
  3. Click Create deployment.
  4. Give your deployment a name.
  5. Click Create deployment and download the password for the elastic user.

That’s it! Now that you are up and running, it’s time to get some data into Kibana. Kibana will open as soon as your deployment is ready.

Log on to the web applicationedit

If you are using a self-managed deployment, access Kibana through the web application on port 5601.

  1. Point your web browser to the machine where you are running Kibana and specify the port number. For example, localhost:5601 or

    To remotely connect to Kibana, set to a non-loopback address.

  2. Log on to your account.
  3. Go to the home page, then click Kibana.
  4. To make the Kibana page your landing page, click Make this my landing page.

Check the Kibana statusedit

The status page displays information about the server resource usage and installed plugins.

To view the Kibana status page, use the status endpoint. For example, localhost:5601/status.

Kibana server status page

For JSON-formatted server status details, use the localhost:5601/api/status API endpoint.

Troubleshoot Kibana UI erroredit

Troubleshoot the Kibana Server is not Ready yet error.

  1. From within a Kibana node, confirm the connection to Elasticsearch:

    curl -XGET elasticsearch_ip_or_hostname:9200/
  2. Guarantee the health of the three Kibana-backing indices. All indices must appear and display status:green and status:open:

    curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session?v=true
  3. Shut down all Kibana nodes.
  4. Choose any Kibana node, then update the config to set the debug logging.
  5. Start the node, then check the start-up debug logs for ERROR messages or other start-up issues.

    For example:

    • When Kibana is unable to connect to a healthy Elasticsearch cluster, errors like master_not_discovered_exception or unable to revive connection or license is not available errors appear.
    • When one or more Kibana-backing indices are unhealthy, the index_not_green_timeout error appears.

For more information, refer to our walkthrough on troubleshooting Kibana Health.