# Unable to run kibana on secured public IP after enable security feature

**URL:** <https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [July 12, 2019, 8:59am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178 "2019-07-12T08:59:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sharma3007](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sharma3007/32/43414_2.png) [@Sharma3007](https://discuss.elastic.co/u/Sharma3007)\
**Post date:** [July 12, 2019, 8:59am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178/1 "2019-07-12T08:59:14Z")

</div>

Hi Team,

I am getting error while running my kibana 🙂

[warning][admin][elasticsearch] Unable to revive connection: [https://0.0.0.0:9200/](https://0.0.0.0:9200/)

I am using https for communication

Elastic search is working with Https. But kibana failed to run.

please find my kibana .yaml file config:

```
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601
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"
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: "Test-Kibana"

# The URLs of the Elasticsearch instances to use for all your queries.
#elasticsearch.hosts: ["http://localhost:9200"]
elasticsearch.hosts: ["https://0.0.0.0: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"
elasticsearch.username: "kibana"
elasticsearch.password: "xxxxxxxx"

xpack.security.encryptionKey: "ueurd9jwerdw8erudw9ruw8e9jdrewhj"
xpack.security.sessionTimeout: 600000

# 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"]

elasticsearch.ssl.certificateAuthorities: D:\ElasticStack\Kibana\config\certs\elastic-ca.pem

# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
elasticsearch.ssl.verificationMode: certificate

# 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
#logging.dest: D:\ElasticStack\Kibana\logs\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
#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.
#i18n.locale: "en"
```

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 15, 2019, 5:36am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178/2 "2019-07-15T05:36:09Z")

</div>

You should specify the correct IP for the Elasticsearch URL instead of `0.0.0.0` in your Kibana config or just use `localhost` if it is running on the same host.

---

<div class="post-metadata">

**Author:** ![Sharma3007](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sharma3007/32/43414_2.png) [@Sharma3007](https://discuss.elastic.co/u/Sharma3007)\
**Post date:** [July 15, 2019, 7:19am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178/3 "2019-07-15T07:19:33Z")

</div>

Hi @Christian_Dahlqvist,

Yes,I am using the IP address over there.just for security purpose i am not exposing IP address here.

I want to use the secure communication & for that I have implemented security feature on that. My elastic search working fine on HTTPS, but kibana gets failed with above error.

---

<div class="post-metadata">

**Author:** ![Sharma3007](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sharma3007/32/43414_2.png) [@Sharma3007](https://discuss.elastic.co/u/Sharma3007)\
**Post date:** [July 16, 2019, 6:28am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178/4 "2019-07-16T06:28:29Z")

</div>

Hi team,  
Can you please provide the setting that we need to follow up during enable secure communication on kibana ?

---

<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 13, 2019, 6:28am UTC](https://discuss.elastic.co/t/unable-to-run-kibana-on-secured-public-ip-after-enable-security-feature/190178/5 "2019-08-13T06:28:45Z")

</div>

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