# Updated to 7.2, now I cannot connect to kibana gui

**URL:** <https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592>\
**Category:** Kibana\
**Created:** [July 9, 2019, 4:13pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592 "2019-07-09T16:13:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![durrellgray](https://avatars.discourse-cdn.com/v4/letter/d/cc9497/32.png) [@durrellgray](https://discuss.elastic.co/u/durrellgray)\
**Post date:** [July 9, 2019, 4:13pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/1 "2019-07-09T16:13:11Z")

</div>

I recently deployed version 7.2. My elasticsearch is running, but I cannot get to the Kibana interface. here are my configs.

======================== 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: test-LOGGING

# 

# ------------------------------------ Node ------------------------------------

# 

# Use a descriptive name for the node:

# 

node.name: elasticsearch01

# 

# 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: x.x.182.5

# 

# 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 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: elasticsearch01

# 

# For more information, consult the discovery and cluster formation 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.

#

---

<div class="post-metadata">

**Author:** ![durrellgray](https://avatars.discourse-cdn.com/v4/letter/d/cc9497/32.png) [@durrellgray](https://discuss.elastic.co/u/durrellgray)\
**Post date:** [July 9, 2019, 4:14pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/2 "2019-07-09T16:14:02Z")

</div>

# 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: x.x.182.5

# Enables you to specify a path to mount Kibana at if you are running behind a proxy.

# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath

# from requests it receives, and to prevent a deprecation warning at startup.

# This setting cannot end in a slash.

#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with

# `server.basePath` or require that they are rewritten by your reverse proxy.

# This setting was effectively always `false` before Kibana 6.3 and will

# default to `true` starting in Kibana 7.0.

#server.rewriteBasePath: false

# 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: elasticsearch01

# The URLs of the Elasticsearch instances to use for all your queries.

elasticsearch.hosts: [http://x.x.182.5:9200](http://x.x.182.5: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: none

# 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: 30000

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.

#elasticsearch.startupTimeout: 5000

# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.

elasticsearch.logQueries: true

# 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: true

# Set the interval in milliseconds to sample system and process performance

# metrics. Minimum is 100ms. Defaults to 5000.

#ops.interval: 5000

# Specifies locale to be used for all localizable strings, dates and number formats.

[root@elasticsearch01 elasticsearch]# curl -X GET "x.x.182.5:9200"  
{  
"name" : "elasticsearch01",  
"cluster\_name" : "test-LOGGING",  
"cluster\_uuid" : "Ja7u-BhWRDqKr799x0FQ3w",  
"version" : {  
"number" : "7.2.0",  
"build\_flavor" : "default",  
"build\_type" : "rpm",  
"build\_hash" : "508c38a",  
"build\_date" : "2019-06-20T15:54:18.811730Z",  
"build\_snapshot" : false,  
"lucene\_version" : "8.0.0",  
"minimum\_wire\_compatibility\_version" : "6.8.0",  
"minimum\_index\_compatibility\_version" : "6.0.0-beta1"  
},  
"tagline" : "You Know, for Search"  
}

---

<div class="post-metadata">

**Author:** ![Aaron\_Caldwell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaron_caldwell/32/45755_2.png) [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)\
**Post date:** [July 9, 2019, 5:22pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/3 "2019-07-09T17:22:44Z")

</div>

Hello,

Nothing is jumping out at me immediately configuration-wise. A couple of thoughts:

- Is Kibana running on the same machine? If not, could you try a curl command from that machine?
- You might consider using a minimal Kibana configuration with as few customizations as possible at first. Try it on the same machine first and then try it on a different machine if you plan to run it on a separate server
- Depending on the results of the last two steps, enable your configurations one at a time and check for any issues after each

Hopefully this will help narrow it down!

Regards,  
Aaron

---

<div class="post-metadata">

**Author:** ![durrellgray](https://avatars.discourse-cdn.com/v4/letter/d/cc9497/32.png) [@durrellgray](https://discuss.elastic.co/u/durrellgray)\
**Post date:** [July 9, 2019, 6:12pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/4 "2019-07-09T18:12:45Z")

</div>

Thanks. Kibana and elasticsearch are running on the same machine

---

<div class="post-metadata">

**Author:** ![Peter\_Schretlen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_schretlen/32/49024_2.png) [@Peter\_Schretlen](https://discuss.elastic.co/u/Peter_Schretlen)\
**Post date:** [July 9, 2019, 7:03pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/5 "2019-07-09T19:03:51Z")

</div>

Hi Durrell,

It might also be worth configuring a log file in kibana.yml, for example:  
`logging.dest: /var/log/kibana.log`  
(by default the logs go to stdout which can make it hard for troubleshooting).

These logs might give an indication of the problem?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 6, 2019, 7:03pm UTC](https://discuss.elastic.co/t/updated-to-7-2-now-i-cannot-connect-to-kibana-gui/189592/6 "2019-08-06T19:03:51Z")

</div>

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