# Unable to access Elasticsearch 6.3.1 outside server
**URL:** https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667
**Category:** Elasticsearch
**Created:** [July 19, 2018, 7:16am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667 "2018-07-19T07:16:14Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Ravi\_Kumar1](https://discuss.elastic.co/u/Ravi_Kumar1)
#### Post date: [July 19, 2018, 7:16am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/1 "2018-07-19T07:16:14Z")
Hi,
I have Elasticsearch 6.3.1 installed on Digitalocean droplet running Ubuntu 14.04.5 LTS.
I am able to curl Elasticsearch on localhost, but unable to access it from outside network.
Here is the snapshot of my netstat
I tried updating the elasticsearch.yml, but that also did not help.
---
### Author:  [@mnozawa](https://discuss.elastic.co/u/mnozawa)
#### Post date: [July 19, 2018, 8:36am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/2 "2018-07-19T08:36:54Z")
Hi
Set the "network.host" or "network.bind.host" such as "0.0.0.0".
[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html)
Otherwise, your host's network/security setting issue maybe.
regards
---
### Author:  [@Ravi\_Kumar1](https://discuss.elastic.co/u/Ravi_Kumar1)
#### Post date: [July 25, 2018, 1:17pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/3 "2018-07-25T13:17:12Z")
Hi Makoto,
Thanks a lot for your reply.
I have set "network.host" to 0.0.0.0 in my elasticsearch.yml file. I can curl elasticsearch in localhost, but not from other computer(my personal machine)
kindly help me to connect to elasticsearch sever from outside the network.
---
### Author:  [@tdasch](https://discuss.elastic.co/u/tdasch)
#### Post date: [July 25, 2018, 2:15pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/4 "2018-07-25T14:15:30Z")
Ravi,
The following link should get you connected. I'm making the assumption you want to SSH into your droplet.
[The link.](https://www.digitalocean.com/docs/droplets/how-to/connect-with-ssh/)
---
### Author:  [@Ravi\_Kumar1](https://discuss.elastic.co/u/Ravi_Kumar1)
#### Post date: [July 26, 2018, 11:37am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/5 "2018-07-26T11:37:06Z")
Hi Thomas,
I can connect to my Digitalocean droplet via SSH. I have also successfully installed Elasticsearch on the droplet. I can curl Elasticsearch on the droplet localhost, but when I try to curl the droplet from my local machine (from outside the droplet), it throws me a curl error. I need a way to curl my Elasticsearch server from outside the network.
---
### Author:  [@sharju](https://discuss.elastic.co/u/sharju)
#### Post date: [July 26, 2018, 12:47pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/6 "2018-07-26T12:47:34Z")
Check your ES node initialization logs for publish\_address and bound\_address to verify that your configuration is really applied. If your publish\_address is not a loopback address, your configuration should be ok and host security is blocking the connection from outside.
---
### Author:  [@Ravi\_Kumar1](https://discuss.elastic.co/u/Ravi_Kumar1)
#### Post date: [July 27, 2018, 9:32am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/7 "2018-07-27T09:32:54Z")
Hi Sharju,
Thanks a lot for your reply,
As suggested, I checked the elasticseach logs and found two lines with publish\_address and bound\_address.
[2018-07-27T14:56:07,013][INFO][o.e.t.TransportService] [VH1h1RB] publish\_address {159.65.145.59:9300}, bound\_addresses {[::]:9300}
and another one,
[2018-07-27T14:56:10,153][INFO][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [VH1h1RB] publish\_address {159.65.145.59:9200}, bound\_addresses {[::]:9200}
It seems like publish\_address is not a loopback address, and problem is with host security.
Please find the Nmap results for the server below.
Starting Nmap 6.40 ( [http://nmap.org](http://nmap.org) ) at 2018-07-27 15:00 IST
Nmap scan report for 159.65.145.59
Host is up (0.0000080s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
143/tcp open imap
443/tcp open https
9200/tcp open wap-wsp
Nmap done: 1 IP address (1 host up) scanned in 2.46 seconds
If you need any other information please let me know.
I would be very helpful if you can provide me with a solution or a link to some tutorial which shows how to access elasticsearch from out side network
---
### Author:  [@sharju](https://discuss.elastic.co/u/sharju)
#### Post date: [July 27, 2018, 11:18am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/8 "2018-07-27T11:18:27Z")
This doesnt seem to be a problem with elasticsearch. Check if your ubuntu has a firewall up:
sudo ufw status
If its up and running, add ports:
sudo ufw allow 9200/tcp
sudo ufw allow 9300/tcp
sudo ufw status
I have no experience with DO droplets. If your ubuntu aint blocking connections, I suggest looking through DO guide materials and forums.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 24, 2018, 11:18am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-6-3-1-outside-server/140667/9 "2018-08-24T11:18:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.