# Can't log in Kibana when a specific elasticsearch node is not running
**URL:** https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914
**Category:** Kibana
**Created:** [March 30, 2023, 9:27am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914 "2023-03-30T09:27:17Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@jgl75](https://discuss.elastic.co/u/jgl75)
#### Post date: [March 30, 2023, 9:27am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/1 "2023-03-30T09:27:17Z")
Hi everyone,
First time poster here.
I'm working with ELK since a few weeks, learning new things every day ๐
I've solved all my problems except one.
I have a 3 nodes elasticsearch cluster and a separate node with kibana & logstash installed.
Everything is working fine when all nodes are up. If ES node 2 or 3 are down, all is well and kibana can be accessed. If ES node 1 is down, Kibana can't be accessed and I get the following error in the log
`License information could not be obtained from Elasticsearch due to ConnectionError: connect ECONNREFUSED`
When ES node 1 is back online, Kibana is happy as a bird...
So it seems that kibana is only checking on ES node 1 for the license and it will not try ES node 2 or 3 for it.
The 3 ES nodes are defined is the kibana.yml file under the elasticsearch.hosts array.
Thank you very much in advance.
Jean
---
### Author:  [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [March 30, 2023, 10:03am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/2 "2023-03-30T10:03:03Z")
Hi Jean,
Welcome to the community! Have you checked the roles of each of your nodes using the [`_nodes` API](https://www.elastic.co/guide/en/elasticsearch/reference/master/cluster-nodes-info.html). Are all nodes master eligible?
---
### Author:  [@jgl75](https://discuss.elastic.co/u/jgl75)
#### Post date: [March 30, 2023, 10:44am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/3 "2023-03-30T10:44:33Z")
Hi Carly,
Thank you for your fast answer. All ES nodes have all roles.
Master role is changing node without issue as far as I can tell.
Jean
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 30, 2023, 11:10pm UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/4 "2023-03-30T23:10:54Z")
Can you share your `kibana.yml`?
---
### Author:  [@jgl75](https://discuss.elastic.co/u/jgl75)
#### Post date: [March 31, 2023, 5:45am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/5 "2023-03-31T05:45:55Z")
Hi warkolm,
Here's my yml file ๐
Thank you in advance for you help !
```auto
# For more configuration options see the configuration guide for Kibana in
# https://www.elastic.co/guide/index.html
# =================== System: Kibana Server ===================
# 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: "localhost"
# 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.
# Defaults to `false`.
#server.rewriteBasePath: false
# Specifies the public URL at which Kibana is available for end users. If
# `server.basePath` is configured this URL should end with the same basePath.
server.publicBaseUrl: "http://"
# The maximum payload size in bytes for incoming server requests.
#server.maxPayload: 1048576
# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"
# =================== System: Kibana Server (Optional) ===================
# 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
# =================== System: Elasticsearch ===================
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts:
- https://:9200
- https://:9200
- https://:9200
# 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: "kibana_system"
elasticsearch.password: ""
# Kibana can also authenticate to Elasticsearch via "service account tokens".
# Service account tokens are Bearer style tokens that replace the traditional username/password based configuration.
# 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
# The maximum number of sockets that can be used for communications with elasticsearch.
# Defaults to `Infinity`.
#elasticsearch.maxSockets: 1024
# Specifies whether Kibana should use compression for communications with elasticsearch
# Defaults to `false`.
#elasticsearch.compression: false
# 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
# =================== System: Elasticsearch (Optional) ===================
# These files are used to verify the identity of Kibana to Elasticsearch and are required when
# xpack.security.http.ssl.client_authentication in Elasticsearch is set to required.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key
# Enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/http_ca.crt"]
# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
# =================== System: Logging ===================
# Set the value of this setting to off to suppress all logging output, or to debug to log everything. Defaults to 'info'
#logging.root.level: debug
# Enables you to specify a file where Kibana stores log output.
logging:
appenders:
file:
type: file
fileName: /var/log/kibana/kibana.log
layout:
type: json
root:
appenders:
- default
- file
# layout:
# type: json
# Logs queries sent to Elasticsearch.
#logging.loggers:
# - name: elasticsearch.query
# level: debug
# Logs http responses.
#logging.loggers:
# - name: http.server.response
# level: debug
# Logs system usage information.
#logging.loggers:
# - name: metrics.ops
# level: debug
# =================== System: Other ===================
# The path where Kibana stores persistent data not saved in Elasticsearch. Defaults to data
#path.data: data
# Specifies the path where Kibana creates the process ID file.
pid.file: /run/kibana/kibana.pid
# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000ms.
#ops.interval: 5000
# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English (default) "en", Chinese "zh-CN", Japanese "ja-JP", French "fr-FR".
#i18n.locale: "en"
# =================== Frequently used (Optional)===================
# =================== Saved Objects: Migrations ===================
# Saved object migrations run at startup. If you run into migration-related issues, you might need to adjust these settings.
# The number of documents migrated at a time.
# If Kibana can't start up or upgrade due to an Elasticsearch `circuit_breaking_exception`,
# use a smaller batchSize value to reduce the memory pressure. Defaults to 1000 objects per batch.
#migrations.batchSize: 1000
# The maximum payload size for indexing batches of upgraded saved objects.
# To avoid migrations failing due to a 413 Request Entity Too Large response from Elasticsearch.
# This value should be lower than or equal to your Elasticsearch clusterโs `http.max_content_length`
# configuration option. Default: 100mb
#migrations.maxBatchSizeBytes: 100mb
# The number of times to retry temporary migration failures. Increase the setting
# if migrations fail frequently with a message such as `Unable to complete the [...] step after
# 15 attempts, terminating`. Defaults to 15
#migrations.retryAttempts: 15
# =================== Search Autocomplete ===================
# Time in milliseconds to wait for autocomplete suggestions from Elasticsearch.
# This value must be a whole number greater than zero. Defaults to 1000ms
#unifiedSearch.autocomplete.valueSuggestions.timeout: 1000
# Maximum number of documents loaded by each shard to generate autocomplete suggestions.
# This value must be a whole number greater than zero. Defaults to 100_000
#unifiedSearch.autocomplete.valueSuggestions.terminateAfter: 100000
```
---
### Author:  [@jgl75](https://discuss.elastic.co/u/jgl75)
#### Post date: [March 31, 2023, 11:52am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/6 "2023-03-31T11:52:03Z")
Problem solved, I was using a user defined during elasticsearch installation so it was only defined on one node... Shame on me โน
I hope that it will help others facing the same issue to loose less time than me ๐
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 28, 2023, 11:52am UTC](https://discuss.elastic.co/t/cant-log-in-kibana-when-a-specific-elasticsearch-node-is-not-running/328914/7 "2023-04-28T11:52:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.