# Configure ingest manager in elasticseach 7.9

**URL:** <https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114>\
**Category:** Elasticsearch\
**Created:** [October 6, 2020, 11:52am UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114 "2020-10-06T11:52:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [October 6, 2020, 11:52am UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/1 "2020-10-06T11:52:13Z")

</div>

I have configured ELK on a single VM ( Centos 7 / 10Gig / 4 CPU) along with filebeat and auditbeat as POC and encountered the below error while trying to use the ingest manager.

![](https://us1.discourse-cdn.com/elastic/original/3X/0/9/094aa6947f17870c51a2be2caada3809ca305eab.png)

I followed the security setup as suggested in [this link](https://www.elastic.co/guide/en/ingest-management/7.9/ingest-management-getting-started.html), the elasticsearch wont come up after many attempts of troubleshooting and i need some help to fix it.

```auto
HTTPS is required in order to use the API key service; please enable HTTPS using the [xpack.security.http.ssl.enabled] setting or disable the API key service using the [xpack.security.authc.api_key.enabled] setting

```

The elasticsearch config is below:

```auto
#
# 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:
bootstrap.memory_lock: true
#
#action.destructive_requires_name: true
xpack.license.self_generated.type: basic
xpack.monitoring.collection.enabled: true
xpack.security.enabled: true
xpack.security.authc.realms.file.users.order: 0
xpack.security.transport.ssl.enabled: true
xpack.security.authc.api_key.enabled: true
xpack.security.http.ssl.enabled: true
xpack.security.transport.ssl.enabled: true

xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/certs/ca.p12
xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/certs/ca.p12
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: /etc/elasticsearch/certs/ca.p12
xpack.security.http.ssl.truststore.path: /etc/elasticsearch/certs/ca.p12

```

The Kibana config is below:

```auto
# 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.
# Supported languages are the following: English - en , by default , Chinese - zh-CN .
#i18n.locale: "en"
xpack.ingestManager.enabled: true
xpack.ingestManager.fleet.tlsCheckDisabled: true
xpack.security.enabled: true
xpack.encryptedSavedObjects.encryptionKey: "8ru3HMCHCLJfcWdKz2rtHQUX43krs5t9deb"
elasticsearch.username: "kibana_system"
elasticsearch.password: "welcome"
xpack.security.encryptionKey: "something_at_least_32_characters"
xpack.security.session.idleTimeout: "10m"
xpack.security.session.lifespan: "8h"

```

---

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [October 9, 2020, 11:51am UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/2 "2020-10-09T11:51:43Z")

</div>

Checking if anyone has any ideas ?

---

<div class="post-metadata">

**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\
**Post date:** [October 9, 2020, 1:59pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/3 "2020-10-09T13:59:15Z")

</div>

Could you share you full `elasticsearch.yml` and `kibana.yml`?

Refer to documentation below, you are required to change all url to https.

> Update all clients, tools, and applications that connect to Elasticsearch to use the `https` protocol in their configuration URL. For example, Kibana, Beats, Logstash, language clients, and custom applications.

> **[Configure TLS | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-tls.html#tls-http)**

---

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [October 13, 2020, 1:46pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/4 "2020-10-13T13:46:12Z")

</div>

HI @kavierkoo

Thank you for replying back, please find the requested config files below ( I have hashed the parameters from earlier config as i needed the ELK to be up for testing someting )

I am more than happy to edit any config to get this working.

elasticsearch.yml

```
**# ======================== 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: ELK**
 **#**
 **# ------------------------------------ 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: 0**
**discovery.seed_hosts : []**
**cluster.initial_master_nodes : []**
 **# Set a custom port for HTTP:**
 **#**
 **logger.org.elasticsearch.transport: debug**
 **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.**
 **#**
 **# ---------------------------------- 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:**
 **bootstrap.memory_lock: true**
 **#**
 **#action.destructive_requires_name: true**
 **xpack.license.self_generated.type: basic**
 **xpack.monitoring.collection.enabled: true**
 **#xpack.security.enabled: true**
 **#xpack.security.authc.realms.file.users.order: 0**
 **#xpack.security.transport.ssl.enabled: true**
 **#xpack.security.authc.api_key.enabled: true**
 **#xpack.security.http.ssl.enabled: true**
 **#xpack.security.transport.ssl.enabled: true**

**#xpack.security.enabled: true**
 **#xpack.security.transport.ssl.enabled: true**
 **#xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/certs/ca.p12**
 **#xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/certs/ca.p12**
 **#xpack.security.http.ssl.enabled: true**
 **#xpack.security.http.ssl.keystore.path: /etc/elasticsearch/certs/ca.p12**
 **#xpack.security.http.ssl.truststore.path: /etc/elasticsearch/certs/ca.p12**

```

Kibana

```
    > **# 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.**
> **# 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: "ELK-KIB"**
> 
> **# The URLs of the Elasticsearch instances to use for all your queries.**
> **elasticsearch.hosts: ["http://localhost:9200"]**
> **elasticsearch.ssl.certificateAuthorities: /etc/kibana/certs/ca.pem**
> 
> **# 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: "kibana"**
> **#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 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**
> 
> **# 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: 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: false**
> 
> **# 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: /var/log/kibana.log**
> 
> **# 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**
> 
> **# Specifies locale to be used for all localizable strings, dates and number formats.**
> **# Supported languages are the following: English - en , by default , Chinese - zh-CN .**
> **#i18n.locale: "en"**
> 
> 
> 
> 
> 
> 
> **#xpack.ingestManager.enabled: true**
> **#xpack.ingestManager.fleet.tlsCheckDisabled: true**
> **#xpack.security.enabled: true**
> **#xpack.encryptedSavedObjects.encryptionKey: "8ru3HMCHCLJfcWdKz2rtHQUX43krs5t9deb"**
> **#elasticsearch.username: "kibana_system"**
> **#elasticsearch.password: "welcome"**
> 
> 
> **#xpack.security.encryptionKey: "something_at_least_32_characters"**
> 
> 
> **#xpack.security.session.idleTimeout: "10m"**
> 
> 
> 
> **#xpack.security.session.lifespan: "8h"**
```

---

<div class="post-metadata">

**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\
**Post date:** [October 13, 2020, 2:14pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/5 "2020-10-13T14:14:30Z")

</div>

> [@Atul\_Chadha](#):
>
> `> **elasticsearch.hosts: ["http://localhost:9200"]**`

In `kibana.yml` this has to be https.

After that have a look if anything from the log.

Hope this can help

---

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [October 13, 2020, 2:17pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/6 "2020-10-13T14:17:31Z")

</div>

Let me try this out, will get back to you

---

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [October 13, 2020, 2:27pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/7 "2020-10-13T14:27:52Z")

</div>

@kavierkoo

Could you confirm if i had to make any other changes too ( the one i hashed earlier ? )

I did tried the change you suggested and restarted elasticsearch and kibana however no action seem to have been happening in the logs

```
[root@elk elasticsearch]# tailf ELK.log

```

[2020-10-13T15:17:05,645][DEBUG][o.e.t.TcpTransport] [elk] Bound profile [default] to address {[::]:9300}  
[2020-10-13T15:17:05,647][INFO][o.e.t.TransportService] [elk] publish\_address {192.168.32.119:9300}, bound\_addresses {[::]:9300}  
[2020-10-13T19:12:11,152][DEBUG][o.e.t.n.Netty4Transport] [elk] using profile[default], worker\_count[4], port[9300-9400], bind\_host[[0]], publish\_host[], receive\_predictor[64kb-\>64kb]  
[2020-10-13T19:12:11,174][DEBUG][o.e.t.TcpTransport] [elk] binding server bootstrap to: [0.0.0.0]  
[2020-10-13T19:12:36,660][DEBUG][o.e.t.TcpTransport] [elk] Bound profile [default] to address {[::]:9300}  
[2020-10-13T19:12:36,663][INFO][o.e.t.TransportService] [elk] publish\_address {192.168.32.119:9300}, bound\_addresses {[::]:9300}  
[2020-10-13T19:49:08,018][DEBUG][o.e.t.n.Netty4Transport] [elk] using profile[default], worker\_count[4], port[9300-9400], bind\_host[[0]], publish\_host[], receive\_predictor[64kb-\>64kb]  
[2020-10-13T19:49:08,033][DEBUG][o.e.t.TcpTransport] [elk] binding server bootstrap to: [0.0.0.0]  
[2020-10-13T19:49:32,164][DEBUG][o.e.t.TcpTransport] [elk] Bound profile [default] to address {[::]:9300}  
[2020-10-13T19:49:32,166][INFO][o.e.t.TransportService] [elk] publish\_address {192.168.32.119:9300}, bound\_addresses {[::]:9300}

[2020-10-13T19:54:41,142][DEBUG][o.e.t.n.Netty4Transport] [elk] using profile[default], worker\_count[4], port[9300-9400], bind\_host[[0]], publish\_host[], receive\_predictor[64kb-\>64kb]  
[2020-10-13T19:54:41,151][DEBUG][o.e.t.TcpTransport] [elk] binding server bootstrap to: [0.0.0.0]  
[2020-10-13T19:55:04,005][DEBUG][o.e.t.TcpTransport] [elk] Bound profile [default] to address {[::]:9300}  
[2020-10-13T19:55:04,010][INFO][o.e.t.TransportService] [elk] publish\_address {192.168.32.119:9300}, bound\_addresses {[::]:9300}

The UI shows "Kibana server is not ready yet" , Kibana logs are below

```
earch due to Error: No Living connections error"}

```

{"type":"log","@timestamp":"2020-10-13T14:27:35Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"Unable to revive connection: [https://localhost:9200/](https://localhost:9200/)"}  
{"type":"log","@timestamp":"2020-10-13T14:27:35Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"No living connections"}  
{"type":"log","@timestamp":"2020-10-13T14:27:37Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"Unable to revive connection: [https://localhost:9200/](https://localhost:9200/)"}  
{"type":"log","@timestamp":"2020-10-13T14:27:37Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"No living connections"}  
{"type":"log","@timestamp":"2020-10-13T14:27:40Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"Unable to revive connection: [https://localhost:9200/](https://localhost:9200/)"}  
{"type":"log","@timestamp":"2020-10-13T14:27:40Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"No living connections"}  
{"type":"log","@timestamp":"2020-10-13T14:27:42Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"Unable to revive connection: [https://localhost:9200/](https://localhost:9200/)"}  
{"type":"log","@timestamp":"2020-10-13T14:27:42Z","tags":["warning","elasticsearch","data"],"pid":3427,"message":"No living connections"}

---

<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:** [November 10, 2020, 2:28pm UTC](https://discuss.elastic.co/t/configure-ingest-manager-in-elasticseach-7-9/251114/8 "2020-11-10T14:28:05Z")

</div>

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