# Reindex from Remote

**URL:** <https://discuss.elastic.co/t/reindex-from-remote/78583>\
**Category:** Elasticsearch\
**Created:** [March 14, 2017, 7:18pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583 "2017-03-14T19:18:24Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [March 14, 2017, 7:18pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/1 "2017-03-14T19:18:24Z")

</div>

I'm trying to perform [Reindex from Remote](https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-reindex.html#reindex-from-remote) and I'm getting following error:

@dest:

```
# curl --request POST 0:9200/_reindex?pretty -d @reindex.json 
{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "[X:X] not whitelisted in reindex.remote.whitelist"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "[X:X] not whitelisted in reindex.remote.whitelist"
  },
  "status" : 400
}
# cat reindex.json 
{
   "dest" : {
      "index" : "index1"
   },
   "source" : {
      "query" : {
         "match_all" : {}
      },
      "remote" : {
         "password" : "password",
         "username" : "username",
         "host" : "https://URL:443"
      },
      "index" : "index1"
   }
}
# 

```

@source: _reindex.remote.whitelist_:

```
# grep ^reindex.remote.whitelist elasticsearch.yml 
reindex.remote.whitelist: *:*
# 

```

Please advise.

---

<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:** [March 14, 2017, 10:57pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/2 "2017-03-14T22:57:47Z")

</div>

Is there a space in front of `reindex.remote.whitelist` in the config file? yaml is sensitive to that.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [March 15, 2017, 12:08am UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/3 "2017-03-15T00:08:20Z")

</div>

no, there is no space...

is there way to see `reindex.remote.whitelist` variable through `curl` somehow? I tried without square braces, but with same result(

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [March 29, 2017, 12:25pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/4 "2017-03-29T12:25:43Z")

</div>

Has this since been resolved?

Something along the lines of _reindex.remote.whitelist: localhost:\*_ works well in the elasticsearch.yml  
And for multiples, a comma delimited list of allowed remote host and port combinations is suffice.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 3, 2017, 3:47pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/5 "2017-04-03T15:47:01Z")

</div>

No, I'm still experiencing issue even with wildcard for host and port:

```
# tail -1 elasticsearch.yml 
reindex.remote.whitelist: *:*
#

```

* * *

I _may_ have found my issue...

```
elk | Caused by: while scanning an alias
elk | in 'reader', line 100, column 27:
elk | reindex.remote.whitelist: *:*
elk | ^
elk | expected alphabetic or numeric character, but found but found :
elk | in 'reader', line 100, column 28:
elk | reindex.remote.whitelist: *:*
elk | ^

```

* * *

I tried changing syntax to following:

```
root@166ac979a194:/# tail -1 /etc/elasticsearch/elasticsearch.yml 
reindex.remote.whitelist: '*:*'
root@166ac979a194:/# 

```

and even like following:

```
root@166ac979a194:/# tail -1 /etc/elasticsearch/elasticsearch.yml 
reindex.remote.whitelist: ["*:*"]
root@166ac979a194:/# 

```

neither resolve my issue(

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [April 3, 2017, 4:26pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/6 "2017-04-03T16:26:58Z")

</div>

We test reindex-from-remote with an elasticsearch.yml file like this:

```auto
reindex.remote.whitelist: 127.0.0.1:*

```

and it works. You probably don't want to whitelist 127.0.0.1 though. Not too useful.

It looks like you can see the settings with `curl -s 'localhost:9200/_cluster/settings?pretty&include_defaults'`.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 3, 2017, 4:30pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/8 "2017-04-03T16:30:09Z")

</div>

thank you for that `curl` command, that's useful)

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 3, 2017, 4:31pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/9 "2017-04-03T16:31:01Z")

</div>

I've gotten a little further and now I'm getting following error instead:

```
{
  "error" : {
    "root_cause" : [
      {
        "type" : "s_s_l_handshake_exception",
        "reason" : "General SSLEngine problem"
      }
    ],
    "type" : "s_s_l_handshake_exception",
    "reason" : "General SSLEngine problem",
    "caused_by" : {
      "type" : "s_s_l_handshake_exception",
      "reason" : "General SSLEngine problem",
      "caused_by" : {
        "type" : "validator_exception",
        "reason" : "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
        "caused_by" : {
          "type" : "sun_cert_path_builder_exception",
          "reason" : "unable to find valid certification path to requested target"
        }
      }
    }
  },
  "status" : 500
}

```

I'm using _letsencrypt_ certificate.

Please advise.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [April 3, 2017, 5:08pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/10 "2017-04-03T17:08:53Z")

</div>

Something like this ought to work:

> **[Will the cross root cover trust by the default list in the JDK/JRE?](https://community.letsencrypt.org/t/will-the-cross-root-cover-trust-by-the-default-list-in-the-jdk-jre/134/13)**
>
> I’ve just hit this issue my self. Whilst beta testing I found maven wouldn’t accept the cert (I have proxied Nexus on a whitelisted domain) & maven was failing with: sun.security.validator.ValidatorException: PKIX path building failed:...

---

<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:** [May 1, 2017, 5:09pm UTC](https://discuss.elastic.co/t/reindex-from-remote/78583/11 "2017-05-01T17:09:27Z")

</div>

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