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

Elastic Stack Logstash
1

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

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

2

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