# Logstash adds 9200 port to elastic host during healthcheck

**URL:** <https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974>\
**Category:** Logstash\
**Created:** [June 7, 2018, 11:55am UTC](https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974 "2018-06-07T11:55:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tatiana\_Koroleva](https://avatars.discourse-cdn.com/v4/letter/t/a8b319/32.png) [@Tatiana\_Koroleva](https://discuss.elastic.co/u/Tatiana_Koroleva)\
**Post date:** [June 7, 2018, 11:55am UTC](https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974/1 "2018-06-07T11:55:29Z")

</div>

I run elastic cluster in aws (as a service) , so its https endpoint does not have a 9200 ending. But logstash still adds :9200 at the end during healthcheck -

```auto
[2018-06-07T11:46:38,218][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>vpc-elasticsearch-internal-..........amazonaws.com:9200/, :path=>"/"}
[2018-06-07T11:47:08,364][WARN][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"vpc-elasticsearch-internal-..........amazonaws.com:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [https://vpc-elasticsearch-internal-..........amazonaws.com:9200/][Manticore::ConnectTimeout] connect timed out"} 

```

of course the connection fails. Keep in mind that I already have XPACK\_MONITORING\_ENABLED set to false. Is there any setting I can change to work around this?  
Running logstash in k8s - image: [docker.elastic.co/logstash/logstash:6.2.4](http://docker.elastic.co/logstash/logstash:6.2.4)

Thank you in advance!

Tatyana K

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 7, 2018, 12:21pm UTC](https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974/2 "2018-06-07T12:21:57Z")

</div>

Have you tried setting the port number explicitly in the URL?

---

<div class="post-metadata">

**Author:** ![Tatiana\_Koroleva](https://avatars.discourse-cdn.com/v4/letter/t/a8b319/32.png) [@Tatiana\_Koroleva](https://discuss.elastic.co/u/Tatiana_Koroleva)\
**Post date:** [June 7, 2018, 1:15pm UTC](https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974/3 "2018-06-07T13:15:08Z")

</div>

Magnus, you are a genius =) added 443 at the end and it worked. I guess it's a good idea to add this detail to [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html)  
Thank you!

---

<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:** [July 5, 2018, 1:15pm UTC](https://discuss.elastic.co/t/logstash-adds-9200-port-to-elastic-host-during-healthcheck/134974/4 "2018-07-05T13:15:09Z")

</div>

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