# Reindex from remote to cloud fails "Connection reset by peer"

**URL:** <https://discuss.elastic.co/t/reindex-from-remote-to-cloud-fails-connection-reset-by-peer/169459>\
**Category:** Elasticsearch\
**Created:** [February 21, 2019, 3:58pm UTC](https://discuss.elastic.co/t/reindex-from-remote-to-cloud-fails-connection-reset-by-peer/169459 "2019-02-21T15:58:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [February 21, 2019, 3:58pm UTC](https://discuss.elastic.co/t/reindex-from-remote-to-cloud-fails-connection-reset-by-peer/169459/1 "2019-02-21T15:58:32Z")

</div>

Hello,

I try to [reindex from a remote cluster to my elastic cloud cluster](https://www.elastic.co/blog/migrating-to-elastic-cloud) like this:

```auto
POST _reindex
{
  "conflicts": "proceed",
  "source": {
    "remote": {
      "host": "http://aaa.mysite.com:9200",
      "username": "elastic",
      "password": "XXXXX"
    },
    "index": ".reporting-2018.04.29"
  },
  "dest": {
    "index": ".reporting-2018.04.29",
    "version_type": "external"
  }
}

```

Here is the response:

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "i_o_exception",
        "reason": "Connection reset by peer"
      }
    ],
    "type": "i_o_exception",
    "reason": "Connection reset by peer"
  },
  "status": 500
}

```

I understand [here](https://www.elastic.co/guide/en/cloud/current/ec-add-user-settings.html#ec-es-elasticsearch-settings) that I do not need to set `reindex.remote.whitelist`. I tried, same effect anyway

On my on-premise cluster (the remote), I have added the cloud cluster in the

```auto
PUT /_cluster/settings
{
    "persistent" : {
        "xpack.security.transport.filter.allow" : 
        [
              "theclusterid.eu-west-1.aws.found.io"
            ]
    }
}

```

By the way the cluster is accessible:

```auto
> curl "http://elastic:XXXXX@aaa.mysite.com:9200"
{
  "name" : "XXXX",
  "cluster_name" : "XXXXX",
  "cluster_uuid" : "wK4ED2gSRpeytWzJPFbOhA",
  "version" : {
    "number" : "6.2.2",
    "build_hash" : "10b1edd",
    "build_date" : "2018-02-16T19:01:30.685723Z",
    "build_snapshot" : false,
    "lucene_version" : "7.2.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

```

Can anybody help me for that? is there some logs somewhere?

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [February 22, 2019, 1:08pm UTC](https://discuss.elastic.co/t/reindex-from-remote-to-cloud-fails-connection-reset-by-peer/169459/2 "2019-02-22T13:08:42Z")

</div>

Found that the problem is xpack transport filtering. When doing the reindex from the cloud, what is the IP address that will perform the reindex? seems not to be `theclusterid.eu-west-1.aws.found.io`

---

<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:** [March 22, 2019, 1:08pm UTC](https://discuss.elastic.co/t/reindex-from-remote-to-cloud-fails-connection-reset-by-peer/169459/3 "2019-03-22T13:08:50Z")

</div>

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