# Logstash cannot connect to ES on server using proxy settings. However, curl command works fine

**URL:** <https://discuss.elastic.co/t/logstash-cannot-connect-to-es-on-server-using-proxy-settings-however-curl-command-works-fine/205574>\
**Category:** Logstash\
**Created:** [October 29, 2019, 1:30am UTC](https://discuss.elastic.co/t/logstash-cannot-connect-to-es-on-server-using-proxy-settings-however-curl-command-works-fine/205574 "2019-10-29T01:30:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Charles\_MacKay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/charles_mackay/32/56744_2.png) [@Charles\_MacKay](https://discuss.elastic.co/u/Charles_MacKay)\
**Post date:** [October 29, 2019, 1:30am UTC](https://discuss.elastic.co/t/logstash-cannot-connect-to-es-on-server-using-proxy-settings-however-curl-command-works-fine/205574/1 "2019-10-29T01:30:44Z")

</div>

logstash on server A (using the below proxy settings) cannot connect to my ES instance (times out).

```
user@myserver:/usr/share/logstash$ env | grep -i proxy
http_proxy=http://my-proxy-server:80/
ftp_proxy=http://my-proxy-server:80/
https_proxy=http://my-proxy-server:80/
no_proxy=localhost,127.0.0.1,localaddress,.localdomain.com
NO_PROXY=localhost,127.0.0.1,localaddress,.localdomain.com
FTP_PROXY=http://my-proxy-server:80/
HTTPS_PROXY=http://my-proxy-server:80/
HTTP_PROXY=http://my-proxy-server:80/

```

gives the following error message:  
`[2019-10-28T19:17:36,574][WARN][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"https://elastic:xxxxxx@xxxxx.us-east-1.aws.found.io:9243/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [https://elastic:xxxxxx@xxxxxxxx.us-east-1.aws.found.io:9243/][Manticore::ConnectTimeout] connect timed out"}`

however, using the curl command  
curl [https://elastic:xxxx@mydeploymentid.us-east-1.aws.found.io:9243](https://elastic:xxxx@mydeploymentid.us-east-1.aws.found.io:9243)

returns a successful response, with the familar json  
{  
"tagline" : "You Know, for Search"  
}

I'm not sure what else to check here... From reading, logstash should follow the environmental proxy variables.

using logstash 7.4.1

---

<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:** [November 26, 2019, 1:30am UTC](https://discuss.elastic.co/t/logstash-cannot-connect-to-es-on-server-using-proxy-settings-however-curl-command-works-fine/205574/2 "2019-11-26T01:30:45Z")

</div>

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