# Can't connect to ES 1.6

**URL:** <https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315>\
**Category:** Elasticsearch\
**Created:** [June 10, 2015, 12:40pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315 "2015-06-10T12:40:19Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 12:40pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/1 "2015-06-10T12:40:19Z")

</div>

I was able to index 230K documents overnight, doing a curl on health and indices I can see the index and the health returns a yellow status - everything just like on the previous version of ES - except I can't seem to connect to instance.

I've tried 3rd party tools - that all work on the last version of ES - and none connect (ElasticHQ for example). When I try to "search" my site returns a blank, white, page - no errors.

The installation process seemed very different for this version - as does the start process - and I can't get ES to run as a service with this version. Is it supposed to be installed in a specific location? Right now it's in /opt/elasticsearch-1.6.0

Is it possible to downgrade the installation or copy the index into an installation of a previous version? I just don't want to spend another 8 hours indexing today 😉

Thanks!

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 2:51pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/2 "2015-06-10T14:51:56Z")

</div>

UPDATE:  
If I do a "netstat -tanp" on the system running 1.5.2 I get this line, which is not present  
in 1.6:

tcp 0 0 127.0.0.1:55207 127.0.0.1:9200 TIME\_WAIT -

1.5.2 works perfectly.  
1.6 is running but nothing can connect to it.

Help - please advise 😄  
Rob

---

<div class="post-metadata">

**Author:** ![costin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/costin/32/44950_2.png) [@costin](https://discuss.elastic.co/u/costin)\
**Post date:** [June 10, 2015, 5:39pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/3 "2015-06-10T17:39:57Z")

</div>

Moved the post from `Elasticsearch Hadoop` category to `Elasticsearch`.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:07pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/4 "2015-06-10T22:07:35Z")

</div>

What does curl $IP:9200/ return?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:10pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/5 "2015-06-10T22:10:55Z")

</div>

Hello Mark,

It returns:

curl: (6) Could not resolve host:

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:13pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/6 "2015-06-10T22:13:55Z")

</div>

Did you use that exact command or did you replace $IP with your own IP?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:17pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/7 "2015-06-10T22:17:34Z")

</div>

lol…the exact command….

Okay - I put in 127.0.0.1 and my public facing IP - both didn't return a thing.

I hit enter, the cursor drops down a line, and just hangs there. I have to cntr-c to get back to a prompt.

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:20pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/8 "2015-06-10T22:20:08Z")

</div>

Tried it again, as I was responding with my last, and it just timed out:

curl: (7) Failed to connect to IP port 9200: connection timed out.

But the IP it gives is not anything I've ever seen and isn't anywhere in my netstat

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:20pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/9 "2015-06-10T22:20:38Z")

</div>

How are you installing ES, how are you starting it?  
Have you checked the logs to see if anything is reported?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:31pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/10 "2015-06-10T22:31:22Z")

</div>

Mark - sorry - I was in the wrong terminal window when I tried that curl.

The return is:

curl (7) Failed to connet to IPxxx.xxx.xxx.xxx port 9200: Connection Refused.

I installed it per the instructions as follows:  
curl -L -O [https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.6.0.tar.gz](https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.6.0.tar.gz)  
tar -xvf elasticsearch-1.6.0.tar.gz  
cd elasticsearch-1.6.0/bin

and started it with this command:  
./elasticsearch

Also, when it started, the process said "recovered [0] indices…" and then hung, I had to cntr-c out of it, but I posted it as an issue on Github last night and was told that was okay.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:36pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/11 "2015-06-10T22:36:25Z")

</div>

As I mentioned in the GH issue it's not hung, that is what you see when ES has started and is ready to serve requests.

Does `ps -ef|grep java` show Elasticsearch running?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:40pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/12 "2015-06-10T22:40:38Z")

</div>

Ah - that was you - thank you again!

Here is what that returns:  
tomcat6 1782 1 0 14:22 ? 00:00:33 /usr/lib/jvm/default-java/bin/java -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -Xmx128m -XX:+UseConcMarkSweepGC -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -classpath /usr/share/tomcat6/bin/bootstrap.jar -Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tomcat6-tmp org.apache.catalina.startup.Bootstrap start  
root 2000 1 0 14:27 pts/0 00:02:25 /usr/bin/java -Xms256m -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.path.home=/opt/elasticsearch-1.6.0 -cp :/opt/elasticsearch-1.6.0/lib/elasticsearch-1.6.0.jar:/opt/elasticsearch-1.6.0/lib/_:/opt/elasticsearch-1.6.0/lib/sigar/_ org.elasticsearch.bootstrap.Elasticsearch  
root 3467 1961 0 22:38 pts/0 00:00:00 grep --color=auto java

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:41pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/13 "2015-06-10T22:41:14Z")

</div>

You're running ES in Tomcat?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:41pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/14 "2015-06-10T22:41:18Z")

</div>

By the way, this is a test system, so I can blow it up, no problem - reinstall, etc...

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 10:45pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/15 "2015-06-10T22:45:14Z")

</div>

That's the first I've seen Tomcat mentioned on this server. I'm running Apache2, php5.9,Mariadb10.x and not much else. No idea how Tomcat got into this mix - like I said, I just followed the instructions as I have with previous versions, on the same image I've been using for months.

If I do a ps -aux Tomcat isn't even there.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 11:03pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/16 "2015-06-10T23:03:32Z")

</div>

Hmm ok, might just be an environment variable.  
Why not just use a deb/rpm to install ES, that way you get the service to handle starting of the service?

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 11:08pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/17 "2015-06-10T23:08:45Z")

</div>

Having not used "Linux" since Unix SCO was all the rage I thought it'd be best to just follow the instructions on the site 😉

Okay - I'm just going to delete this server and create a new one - can you provide me a link to the 1.6 deb package?

Thank you for all your help!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 11:18pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/18 "2015-06-10T23:18:01Z")

</div>

You'd be best off using a repository - [https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html)

---

<div class="post-metadata">

**Author:** ![Trident50](https://avatars.discourse-cdn.com/v4/letter/t/9de053/32.png) [@Trident50](https://discuss.elastic.co/u/Trident50)\
**Post date:** [June 10, 2015, 11:19pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/19 "2015-06-10T23:19:14Z")

</div>

Will do…thanks again Mark!

---

<div class="post-metadata">

**Author:** ![dxm1825](https://avatars.discourse-cdn.com/v4/letter/d/a9a28c/32.png) [@dxm1825](https://discuss.elastic.co/u/dxm1825)\
**Post date:** [June 16, 2015, 11:02am UTC](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315/20 "2015-06-16T11:02:53Z")

</div>

Kibana 3 against ElasticSearch 1.4 throws an Connection Failed screen. The error text says to set `http.cors.allow-origin`, but it misses out the important `http.cors.enabled: true`

Working config:

```
$ grep cors elasticsearch-1.4.0.Beta1/config/elasticsearch.yml
http.cors.allow-origin: "/.*/"
http.cors.enabled: true

```

[Source](https://gist.github.com/rmoff/379e6ce46eb128110f38)

[Next page](https://discuss.elastic.co/t/cant-connect-to-es-1-6/2315.md?page=2)
