# Unable to connect remotely to elastic search 6.3.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 20, 2019, 10:49am UTC](https://discuss.elastic.co/t/unable-to-connect-remotely-to-elastic-search-6-3-2/181795 "2019-05-20T10:49:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Mahadevappa\_M\_Utagi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahadevappa_m_utagi/32/46467_2.png) [@Mahadevappa\_M\_Utagi](https://discuss.elastic.co/u/Mahadevappa_M_Utagi)\ **Post date:** [May 20, 2019, 10:49am UTC](https://discuss.elastic.co/t/unable-to-connect-remotely-to-elastic-search-6-3-2/181795/1 "2019-05-20T10:49:03Z")
I am trying to ingest data into remote elastic search 6.3.2 with index [es\_historic\_dev] like es.net.proxy.http.host - [https://xyz.com](https://xyz.com) es.net.proxy.http.port - 443 (port for https endpoint) I am facing below issue: ERROR NetworkClient: Node [[https://xyz.com:9200](https://xyz.com:9200)] failed (Connection timed out: connect); no other nodes left - aborting... Exception in thread "main" org.elasticsearch.hadoop.EsHadoopIllegalArgumentException: Cannot detect ES version - typically this happens if the network/Elasticsearch cluster is not accessible or when targeting a WAN/Cloud instance without the proper setting 'es.nodes.wan.only' at org.elasticsearch.hadoop.rest.InitializationUtils.discoverEsVersion(InitializationUtils.java:327) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2019, 10:49am UTC](https://discuss.elastic.co/t/unable-to-connect-remotely-to-elastic-search-6-3-2/181795/2 "2019-06-17T10:49:07Z")
Closed on June 17, 2019, 10:49am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.