# Getting Timeout after sometime

**URL:** https://discuss.elastic.co/t/getting-timeout-after-sometime/347494
**Category:** Kibana
**Created:** [November 20, 2023, 5:32am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494 "2023-11-20T05:32:33Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![deepak\_Bahuguna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepak_bahuguna/32/127736_2.png) [@deepak\_Bahuguna](https://discuss.elastic.co/u/deepak_Bahuguna)
#### Post date: [November 20, 2023, 5:32am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/1 "2023-11-20T05:32:33Z")

</div>

HI Guys,

I am new to Elastic, Kibana. I have downloaded the Elastic and Kibana then I run both and it worked fine. What is problem is after installing I have kept it opened in evening and when I see it morning it has showing Timeout exception all the time evenafter I have restarted the Elastic and Kibana both servers. It always shows me " **Kibana server is not ready yet.**".

and the error I get in console is:

```auto
**[2023-11-20T10:04:29.626+05:30][INFO][plugins.screenshotting.chromium] Browser executable: D:\Softwares\Elastic Stack\kibana-8.11.1\node_modules\@kbn\screenshotting-plugin\chromium\chrome-win\chrome.exe**
**[2023-11-20T10:05:53.826+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. connect ETIMEDOUT 192.168.1.2:9200**
**[2023-11-20T10:24:28.552+05:30][ERROR][plugins.ruleRegistry] Error: Timeout: it took more than 1200000ms**
**at Timeout._onTimeout (D:\Softwares\Elastic Stack\kibana-8.11.1\node_modules\@kbn\alerting-plugin\server\alerts_service\lib\install_with_timeout.js:36:18)**
**at listOnTimeout (node:internal/timers:569:17)**
**at processTimers (node:internal/timers:512:7)**
**[2023-11-20T10:24:28.558+05:30][ERROR][plugins.ruleRegistry] Error: Failure during installation of common resources shared between all indices. Timeout: it took more than 1200000ms**
**at installWithTimeout (D:\Softwares\Elastic Stack\kibana-8.11.1\node_modules\@kbn\alerting-plugin\server\alerts_service\lib\install_with_timeout.js:48:11)**
**at ResourceInstaller.installCommonResources (D:\Softwares\Elastic Stack\kibana-8.11.1\node_modules\@kbn\rule-registry-plugin\server\rule_data_plugin_service\resource_installer.js:42:5)**

```

any suggestion is appriciated.

Thanks!

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 21, 2023, 10:29am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/2 "2023-11-21T10:29:57Z")

</div>

Hi @deepak_Bahuguna,

Welcome! That looks like a connection issue between Elasticsearch and Kibana. Can you check some of the troubleshooting steps [here](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/241217) including checking the logs to see if we can get more information.

Can you also share your configuration?

---

<div class="post-metadata">

### Author: ![deepak\_Bahuguna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepak_bahuguna/32/127736_2.png) [@deepak\_Bahuguna](https://discuss.elastic.co/u/deepak_Bahuguna)
#### Post date: [November 22, 2023, 10:25am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/3 "2023-11-22T10:25:46Z")

</div>

Hi Carly,

Thanks for you reply...I am sharing my config files...please have a look...

When I have downloaded the Elastic and Kibana..I just went with Default configuration..i did not make any changes manually...

**below is the kibana config file:**

```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: ""

# 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: ["http://localhost: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: "pass"

# 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.
# Use this token instead of a username/password.
# elasticsearch.serviceAccountToken: "my_token"

# 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: ["/path/to/your/CA.pem"]

# 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.default:
# type: file
# fileName: /var/logs/kibana.log
# 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

# This section was automatically generated during setup.
elasticsearch.hosts: ['https://192.168.0.169:9200']
elasticsearch.serviceAccountToken: AAEAAWVsYXN0aWMva2liYW5hL2Vucm9sbC1wcm9jZXNzLXRva2VuLTE3MDA0NjY2NzU0MTA6ZF9fcUxqbmhUVTJjZExjeHFxaVlGZw
elasticsearch.ssl.certificateAuthorities: ['D:\Softwares\Elastic Stack\kibana-8.11.1\data\ca_1700466676428.crt']
xpack.fleet.outputs: [{id: fleet-default-output, name: default, is_default: true, is_default_monitoring: true, type: elasticsearch, hosts: ['https://192.168.0.169:9200'], ca_trusted_fingerprint: dc760b73d2d996b19edfcb1f8525322e3a4f2fa88c1777b211d36b4790f464a2}]

```

**below is the elastic config file:**

```auto
# ======================== 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
#
# ---------------------------------- 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: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- 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 -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host: 192.168.0.1
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
#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: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false

#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 20-11-2023 06:56:06
#
# --------------------------------------------------------------------------------

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["DEEPAK-LAPTOP"]

# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0

# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
#transport.host: 0.0.0.0

#----------------------- END SECURITY AUTO CONFIGURATION -------------------------

```

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 22, 2023, 10:29am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/4 "2023-11-22T10:29:41Z")

</div>

Thanks @deepak_Bahuguna, Have you checked the logs for any errors (aside from the console) and the health of Elasticsearch to see if it can be connected to? The troubleshooting link I shared above should have the steps.

---

<div class="post-metadata">

### Author: ![deepak\_Bahuguna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepak_bahuguna/32/127736_2.png) [@deepak\_Bahuguna](https://discuss.elastic.co/u/deepak_Bahuguna)
#### Post date: [November 23, 2023, 10:55am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/5 "2023-11-23T10:55:53Z")

</div>

Hi Carly,

I have got it worked. What I was doing wrong is HOST IP in my config file was wrong and SSL security was set to TRUE.

Thanks for your consecutive respond.

---

<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: [December 21, 2023, 10:56am UTC](https://discuss.elastic.co/t/getting-timeout-after-sometime/347494/6 "2023-12-21T10:56:46Z")

</div>

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