kibana/docs/setup/access.asciidoc

[[access]]
== Access {kib}

The fastest way to access {kib} is to use our hosted {es} Service. If you <<install, installed {kib} on your own>>, access {kib} through the web application.

[float]
=== Set up on cloud

include::{docs-root}/shared/cloud/ess-getting-started.asciidoc[]

[float]
[[log-on-to-the-web-application]]
=== Log on to the web application

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

. Point your web browser to the machine where you are running {kib} and specify the port number. For example, `localhost:5601` or `http://YOURDOMAIN.com:5601`.
+
To remotely connect to {kib}, set <server-host,server.host>> to a non-loopback address.

. Log on to your account.

. Go to the home page, then click *{kib}*.

. To make the {kib} page your landing page, click *Make this my landing page*.

[float]
[[status]]
=== Check the {kib} status

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

To view the {kib} status page, use the status endpoint. For example, `localhost:5601/status`. 

[role="screenshot"]
image::images/kibana-status-page-7_14_0.png[Kibana server status page]

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

[float]
[[not-ready]]
=== {kib} not ready

If you receive an error that the {kib} `server is not ready`, check the following:

* The {es} connectivity: 
+
[source,sh]
----
`curl -XGET elasticsearch_ip_or_hostname:9200/`
----
* The {kib} logs:
** Linux, DEB or RPM package: `/var/log/kibana/kibana.log`
** Linux, tar.gz package: `$KIBANA_HOME/log/kibana.log`
** Windows: `$KIBANA_HOME\log\kibana.log`
* The health status of `.kibana*` indices