# Reindex remote-Received Error "socket\_exception" & "Connection reset"

**URL:** <https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538>\
**Category:** Elasticsearch\
**Tags:** reindex\
**Created:** [May 10, 2021, 6:13am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538 "2021-05-10T06:13:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ragul\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragul_r/32/80164_2.png) [@Ragul\_R](https://discuss.elastic.co/u/Ragul_R)\
**Post date:** [May 10, 2021, 6:13am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/1 "2021-05-10T06:13:37Z")

</div>

I'm Copying index remotely cluster1 to Cluster2.[Received Error "socket\_exception" & "Connection reset"]

i haved tried Type 1& 2 configuration, im facing same error

elasticsearch.yml

Type1:

```
reindex.remote.whitelist: ["*:*"]
reindex.ssl.certificate: pc1.crt
reindex.ssl.key: pc1.key
reindex.ssl.certificate_authorities: ca.crt
reindex.ssl.verification_mode: full

```

Type2:

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

```

please me help, how to overcome remotely Reindex SSL issue.

 ![Capture](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c5ff83168f2f62edfdd6717ef2855e4693f487d3.png)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 10, 2021, 6:14am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/2 "2021-05-10T06:14:34Z")

</div>

What is the response if you run that via curl? The 500 error should be reporting a log in the Elasticsearch logs as well.

---

<div class="post-metadata">

**Author:** ![Ragul\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragul_r/32/80164_2.png) [@Ragul\_R](https://discuss.elastic.co/u/Ragul_R)\
**Post date:** [May 10, 2021, 6:44am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/3 "2021-05-10T06:44:31Z")

</div>

Curl Command

`curl -XPOST "https://pc1.com:9200/_reindex" -H "Content-Type: application/json" -H "Authorization: Basic ZWxhc3RpYzpljAyMQ==" -k -v -d "{\"source\":{\"remote\":{\"host\":\"https://pc1:9200\",\"username\":\"elastic\",\"password\":\"elastic11\"},\"index\": \"testing\"},\"dest\": {\"index\": \"testing1\"}}"`

Output for Curl Command:

```
    Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 10.x.x.102...
* TCP_NODELAY set
* connect to 10.x.x.102 port 9200 failed: Connection refused
* Failed to connect to pc1.com port 9200: Connection refused
* Closing connection 0
curl: (7) Failed to connect to pc1.com port 9200: Connection refused
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 10, 2021, 6:45am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/4 "2021-05-10T06:45:49Z")

</div>

> [@Ragul\_R](#):
>
> ```auto
> * Failed to connect to pc1.com port 9200: Connection refused
> 
> ```

Ok so Elasticsearch isn't listening, or something is stopping it.  
What do the logs on the `pc1.com` node show?

---

<div class="post-metadata">

**Author:** ![Ragul\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragul_r/32/80164_2.png) [@Ragul\_R](https://discuss.elastic.co/u/Ragul_R)\
**Post date:** [May 10, 2021, 7:09am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/5 "2021-05-10T07:09:12Z")

</div>

I'm Copying index remotely cluster1 to Cluster2

Cluster1:

```
cluster.name: Cluster1
node.name: pc1.com
node.master: true 
node.data: true 
node.ingest: true 
path.data: E:\Elasticstorage-7x\data
path.logs: E:\Elasticstorage-7x\logs
bootstrap.memory_lock: true
network.host: pc1.com
http.port: 9200
discovery.type: single-node
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.key: pc1.key
xpack.security.transport.ssl.certificate: pc1.crt
xpack.security.transport.ssl.certificate_authorities: ca.crt
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key: pc1.key
xpack.security.http.ssl.certificate: pc1.crt
xpack.security.http.ssl.certificate_authorities: ca.crt

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

```

Cluster2:

```
cluster.name: Cluster1
node.name: pc1.com
node.master: true 
node.data: true 
node.ingest: true 
path.data: E:\Elasticstorage-7x\data
path.logs: E:\Elasticstorage-7x\logs
bootstrap.memory_lock: true
network.host: pc1.com
http.port: 80
discovery.type: single-node
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.key: pc1.key
xpack.security.transport.ssl.certificate: pc1.crt
xpack.security.transport.ssl.certificate_authorities: ca.crt
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key: pc1.key
xpack.security.http.ssl.certificate: pc1.crt
xpack.security.http.ssl.certificate_authorities: ca.crt

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

```

Im Running following in Cluster2:

```
POST _reindex?pretty
{
"source": {
"remote": {
"host": "https://pc1.com:9200",
"username": "elastic",
"password": "elastic11"
},
"index": "testing"
},
"conflicts": "proceed",
"dest": {
"index": "test1"
}
}
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 10, 2021, 7:19am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/6 "2021-05-10T07:19:51Z")

</div>

I can't see how this would work, as you can't run two nodes using the same data paths like that without an error. What do your Elasticsearch logs show?

---

<div class="post-metadata">

**Author:** ![Ragul\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ragul_r/32/80164_2.png) [@Ragul\_R](https://discuss.elastic.co/u/Ragul_R)\
**Post date:** [May 10, 2021, 10:55am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/7 "2021-05-10T10:55:54Z")

</div>

Hi warkolm,

Its 2 Different cluster.

I found the issue.

Cluster2 is not able to access the Cluster1 along with port, Bcz 9200 port is blocking.

Thank for your Supporting!!!

---

<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:** [June 7, 2021, 10:56am UTC](https://discuss.elastic.co/t/reindex-remote-received-error-socket-exception-connection-reset/272538/8 "2021-06-07T10:56:49Z")

</div>

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