# \[Error\]Remote reindex connect\_exception with Timeout

**URL:** <https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276>\
**Category:** Elasticsearch\
**Created:** [July 17, 2024, 11:33am UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276 "2024-07-17T11:33:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![unumed-umbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unumed-umbo/32/136092_2.png) [@unumed-umbo](https://discuss.elastic.co/u/unumed-umbo)\
**Post date:** [July 17, 2024, 11:33am UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/1 "2024-07-17T11:33:59Z")

</div>

I'm trying to reindex from a remote from Self Manged instance to an Elastic cloud instance.

But I'm getting a timeout error:

```auto
{"error":{"root_cause":[{"type":"connect_exception","reason":"Timeout connecting to [XXXX.elb.eu-north-1.amazonaws.com/XX.XX.XX.XXX:9200]","status":500}]

```

I have confirmed that connectivity to cluster to using the elb dns name can recieve a connection on the specified port but using curl, and this is succeding without any problem.

I have even disabled all authentication in case that the problem was originated by it. The connection setup is using http but regardless of this I also have disabled the ssl verification and whitelisted all incoming domains in an attempt to exclude some issues on that front applying.

`reindex.remote.whitelist: ["*:*"]`  
`reindex.ssl.verification_mode: none`

The error suggest that there is a connectivity problem from the Elastic cloud towards our instance. But I cannot see any connection error on the logs that give me any more details, and since I can stablish a connection succesfully from internet I'm a bit stuck.  
I have tried using different IP and locations to rule out we have some firewall that is blocking Internet access but this doesn't seem to be the case (as I expected).

Any suggestion on how to perform further connectivity tests originating from the Elastic Cloud would be highly appreciated, or perhaps a way to pull some detailed logs on the error apart of a 500.

Extra information:

- Origin request:

```auto
curl --location 'https://XXXXX.eu-north-1.aws.elastic-cloud.com:9243/_reindex' \ ─╯
--header 'Content-Type: application/json' \
--header 'Authorization: ApiKey XXXXXXX' \
--data '{
  "max_docs": 1,
  "source": {
    "remote": {
      "host": "http://XXXXXXX.elb.eu-north-1.amazonaws.com:9200"
    },
    "index": "test.staging"
  },
  "dest": {
    "index": "reindex.tes.dev"
  }
}'

```

- Curl request to validate connection to Self hosted:

```auto
curl -v -XGET http://XXXXX.elb.eu-north-1.amazonaws.com:9200

```

```auto
curl -v -XGET http://XXXXX.elb.eu-north-1.amazonaws.com:9200/_cluster/state

```

Both succesful

* * *

More data:

We have also validated that our self manage instance can connect directly by performing the same GET request to the ES Cloud, and the connectivity is indeed successful.

---

<div class="post-metadata">

**Author:** ![unumed-umbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unumed-umbo/32/136092_2.png) [@unumed-umbo](https://discuss.elastic.co/u/unumed-umbo)\
**Post date:** [July 17, 2024, 11:34am UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/2 "2024-07-17T11:34:39Z")

</div>

Removed #elastic-cloud

---

<div class="post-metadata">

**Author:** ![unumed-umbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unumed-umbo/32/136092_2.png) [@unumed-umbo](https://discuss.elastic.co/u/unumed-umbo)\
**Post date:** [July 17, 2024, 11:43am UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/3 "2024-07-17T11:43:33Z")

</div>

Removed #elastic-cloud

---

<div class="post-metadata">

**Author:** ![unumed-umbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/unumed-umbo/32/136092_2.png) [@unumed-umbo](https://discuss.elastic.co/u/unumed-umbo)\
**Post date:** [July 18, 2024, 8:59am UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/4 "2024-07-18T08:59:04Z")

</div>

Removed #elastic-cloud

---

<div class="post-metadata">

**Author:** ![nfeekery](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nfeekery/32/117349_2.png) [@nfeekery](https://discuss.elastic.co/u/nfeekery)\
**Post date:** [July 22, 2024, 1:28pm UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/5 "2024-07-22T13:28:18Z")

</div>

From #Elastic Search to #Elasticsearch

---

<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:** [August 19, 2024, 1:28pm UTC](https://discuss.elastic.co/t/error-remote-reindex-connect-exception-with-timeout/363276/6 "2024-08-19T13:28:29Z")

</div>

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