# EADDRNOTAVAIL on connecting remote kibana

**URL:** <https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830>\
**Category:** Kibana\
**Created:** [April 12, 2018, 1:35pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830 "2018-04-12T13:35:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![jurquiza](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@jurquiza](https://discuss.elastic.co/u/jurquiza)\
**Post date:** [April 12, 2018, 1:35pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/1 "2018-04-12T13:35:37Z")

</div>

Hi! im trying to connect remotely to a server in wich i´ve setup the ELK stash. Im currently running it on remote ubuntu 12.04, 4gb ram.  
I started by looking for my public ip adress in order to modify my kibana.yml file, this is what i got:

 ![publicip](https://us1.discourse-cdn.com/elastic/original/3X/0/e/0e15293ed6ed679221230102ef3a5a300f9b38a9.jpg)

so then i modified the yml file like following:

 ![kibanayml](https://us1.discourse-cdn.com/elastic/original/3X/0/e/0e671f5e731078b73aa4d3301ee4f84e60072301.jpg)

i´ve tried to set up my ip to 0.0.0.0 on the yml file,but cant access from chrome or any other web browser either.  
This is the error i get when i try to launch kibana service:

 ![kibana%20error](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a57c46f97ec1e359b53e810d6701eca7e98a7b45.jpg)

If i modify kibana to bind to port 0.0.0.0 im able to access it locally with a curl ,but thats no the idea.  
what im i missing? is the issue related to port permissions, ip address or yml file? any help will be greatly appreciated  
The goal im trying to achieve is NOT to run kibana locally

[EDIT] Firewall is off

---

<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:** [April 12, 2018, 2:53pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/2 "2018-04-12T14:53:21Z")

</div>

I can not read any of the screenshots. Please try to copy and paste text instead as it is a lot easier to read and search.

---

<div class="post-metadata">

**Author:** ![jurquiza](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@jurquiza](https://discuss.elastic.co/u/jurquiza)\
**Post date:** [April 12, 2018, 3:13pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/3 "2018-04-12T15:13:29Z")

</div>

sorry 😅  
this is how i got my ip to bind kibana:

```
root@XXXXXX:~# curl ipinfo.io/ip
201.xxx.xxx.113

```

This is my yml file:

```
# 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: "201.216.251.113"
# Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
# the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
# to Kibana. This setting cannot end in a slash.
#server.basePath: ""

# 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: "TerrandKibana"

# The URL of the Elasticsearch instance to use for all your queries.
#elasticsearch.url: "http://localhost: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: true
server.ssl.certificate: /root/kibanaremote.crt
server.ssl.key: /root/kibanaremote.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: 0

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000

# 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

```

and this is the error log:

```
root@VMLnxPrApp01:/usr/share/kibana# sudo bin/kibana
  log [15:12:41.719] [info][status][plugin:kibana@6.2.3] Status changed from uninitialized to green - Ready
  log [15:12:41.808] [info][status][plugin:elasticsearch@6.2.3] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log [15:12:42.076] [info][status][plugin:timelion@6.2.3] Status changed from uninitialized to green - Ready
  log [15:12:42.090] [info][status][plugin:console@6.2.3] Status changed from uninitialized to green - Ready
  log [15:12:42.102] [info][status][plugin:metrics@6.2.3] Status changed from uninitialized to green - Ready
 error [15:12:42.139] [fatal] Error: listen EADDRNOTAVAIL 201.xxx.xxx.113:5601
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1249:19)
    at listen (net.js:1298:10)
    at net.js:1408:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
```

---

<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:** [April 12, 2018, 3:14pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/4 "2018-04-12T15:14:43Z")

</div>

> [@jurquiza](#):
>
> server.host: "201.216.251.113"

Is this the IP of the host Kibana is running on? Can you try with `0.0.0.0` instead?

---

<div class="post-metadata">

**Author:** ![jurquiza](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@jurquiza](https://discuss.elastic.co/u/jurquiza)\
**Post date:** [April 12, 2018, 3:34pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/5 "2018-04-12T15:34:10Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> Is this the IP of the host Kibana is running on?

Yep, thats the host kibana, elastic, and logstash are running.

> [@Christian\_Dahlqvist](#):
>
> Can you try with 0.0.0.0 instead?

Modified the YML file to bind 0.0.0.0  
Kibana started up correctly, but then when point on the browser 201.216.251.113:5601  
and:

```
This site can’t be reached
201.216.251.113 took too long to respond.
Search Google for 201 216 251 113 5601
ERR_CONNECTION_TIMED_OUT

```

---

<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:** [April 12, 2018, 3:43pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/6 "2018-04-12T15:43:14Z")

</div>

I would recommend checking if you have any firewall rules that prevent access to that port. If this host is open to the internet I would however also recommend that you secure it.

---

<div class="post-metadata">

**Author:** ![jurquiza](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@jurquiza](https://discuss.elastic.co/u/jurquiza)\
**Post date:** [April 12, 2018, 4:09pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/7 "2018-04-12T16:09:41Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> I would recommend checking if you have any firewall rules that prevent access to that port. If this host is open to the internet I would however also recommend that you secure it.

firewall is off, that shouldnt be an issue right?

---

<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:** [April 12, 2018, 4:25pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/8 "2018-04-12T16:25:48Z")

</div>

If you log into the host, can you telnet the port there?

---

<div class="post-metadata">

**Author:** ![jurquiza](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@jurquiza](https://discuss.elastic.co/u/jurquiza)\
**Post date:** [April 12, 2018, 5:48pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/10 "2018-04-12T17:48:19Z")

</div>

`telnet: Unable to connect to remote host: Connection timed out`  
did telnet on address and port and got that (im new to ubuntu btw sorry)

---

<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:** [May 10, 2018, 5:48pm UTC](https://discuss.elastic.co/t/eaddrnotavail-on-connecting-remote-kibana/127830/11 "2018-05-10T17:48:22Z")

</div>

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