# I can't access Kibana
**URL:** https://discuss.elastic.co/t/i-cant-access-kibana/136811
**Category:** Kibana
**Created:** [June 21, 2018, 9:03am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811 "2018-06-21T09:03:50Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 21, 2018, 9:03am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/1 "2018-06-21T09:03:50Z")
Hi guys, after updating Kibana to version 6.3 I can not access it.
The following error message appears.
Does anyone know how to solve this?
---
### Author:  [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [June 21, 2018, 9:49am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/2 "2018-06-21T09:49:53Z")
Hey @cassiocesarps,
Could you please provide more details:
- How do you run Elasticsearch (e.g. command line arguments)?
- How do you run Kibana (e.g. command line arguments)?
- How does your `kibana.yml` look like (if you modified that, exlcuding sensitive info)?
- How does your `elasticsearch.yml` look like (if you modified that, exlcuding sensitive info)?
- Maybe you have Kibana/Elasticsearch logs that you can attach or at least notice something suspicious there?
Thanks,
Oleg
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 21, 2018, 10:46am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/3 "2018-06-21T10:46:33Z")
What happened was that Kibana was working normally in the browser, after upgrading to 6.3 unable to access it anymore.
I'm running Elasticsearch and Kibana on a Fedora 28 server
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 21, 2018, 10:47am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/4 "2018-06-21T10:47:28Z")
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601
# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: 0.0.0.0
# Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
# the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
# to Kibana. This setting cannot end in a slash.
#server.basePath: ""
# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576
# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"
# The URL of the Elasticsearch instance to use for all your queries.
#elasticsearch.url: "[http://localhost:9200](http://localhost:9200)"
# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true
# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"
# The default application to load.
#kibana.defaultAppId: "home"
# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
#elasticsearch.username: "user"
#elasticsearch.password: "pass"
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key
# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key
# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]
# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500
# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000
# List of Kibana client-side headers to send to Elasticsearch. To send _no_ client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]
# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}
# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 0
# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000
# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid
# Enables you specify a file where Kibana stores log output.
#logging.dest: stdout
# Set the value of this setting to true to suppress all logging output.
#logging.silent: false
# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false
# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false
# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000
# The default locale. This locale can be used in certain circumstances to substitute any missing
# translations.
#i18n.defaultLocale: "en"
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 21, 2018, 10:48am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/5 "2018-06-21T10:48:28Z")
# ======================== 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](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 -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
#network.host: 192.168.0.1
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum\_master\_nodes:
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover\_after\_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive\_requires\_name: true
---
### Author:  [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [June 21, 2018, 11:41am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/6 "2018-06-21T11:41:23Z")
Hmm, so security plugin is enabled (since you see login page), but your `kibana.yml` doesn't include username and password for internal Kibana user:
```auto
#elasticsearch.username: "user"
#elasticsearch.password: "pass"
```
Can you please set these and make sure they are correct? If that's the reason you should see something like this in Kibana logs: `security_exception\",\"reason\":\"failed to authenticate user ...`.
Best,
Oleg
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 21, 2018, 12:22pm UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/7 "2018-06-21T12:22:32Z")
How do I disable the security plugin? Because before updating kibana this page did not appear
---
### Author:  [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [June 21, 2018, 1:14pm UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/8 "2018-06-21T13:14:00Z")
You can set `xpack.security.enabled: false` in `elasticsearch.yml` to disable x-pack security plugin.
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 22, 2018, 9:33am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/9 "2018-06-22T09:33:35Z")
Even when entering the command, the login page continues to appear
---
### Author:  [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [June 22, 2018, 9:35am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/10 "2018-06-22T09:35:40Z")
Okay, so we need Elasticsearch and Kibana logs then, otherwise it's really hard to say what's the reason.
Can you share those?
---
### Author:  [@cassiocesarps](https://discuss.elastic.co/u/cassiocesarps)
#### Post date: [June 22, 2018, 9:38am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/11 "2018-06-22T09:38:14Z")
Could you tell me where the logs are?
---
### Author:  [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [June 22, 2018, 9:43am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/12 "2018-06-22T09:43:06Z")
I guess you didn't configure logging-to-file, so logs should be output to console/terminal window where you run elasticsearch and kibana. So this content should be enough to debug the issue.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 20, 2018, 9:43am UTC](https://discuss.elastic.co/t/i-cant-access-kibana/136811/13 "2018-07-20T09:43:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.