# "not whitelisted in reindex.remote.whitelist" Revived

**URL:** <https://discuss.elastic.co/t/not-whitelisted-in-reindex-remote-whitelist-revived/235630>\
**Category:** Elasticsearch\
**Created:** [June 3, 2020, 8:05pm UTC](https://discuss.elastic.co/t/not-whitelisted-in-reindex-remote-whitelist-revived/235630 "2020-06-03T20:05:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davehatma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davehatma/32/29322_2.png) [@davehatma](https://discuss.elastic.co/u/davehatma)\
**Post date:** [June 3, 2020, 8:05pm UTC](https://discuss.elastic.co/t/not-whitelisted-in-reindex-remote-whitelist-revived/235630/1 "2020-06-03T20:05:17Z")

</div>

Attempting to reindex from a 6.4 to 7.6 version using the \_reindex API. We believe we have set everything up correctly, albeit this setup seems to be and should be very simple. However, we cannot get the POST to the \_reindex resource to connect to the remote host.

Here is the request body from the POST:

(Note: the actual server names and ip addresses have been changed to protect the innocent. However, the message and yaml file structures are the same)

{  
"source": {  
"remote": {  
"host": "[http://essvr1:9200](http://essvr1:9200)"  
},  
"index": "pymsa::agreements::transactions::\*"  
},  
"dest": {  
"index": "pymsa\_\_agreements\_\_transactions\_\_dev\_\_"  
},  
"script": {  
"lang": "painless",  
"source": "ctx._index = 'pymsa\_\_agreements\_\_transactions\_\_dev_\_' + (ctx._index.substring('pymsa\_\_agreements\_\_transactions::dev_\_'.length(), ctx.\_index.length()))"  
}  
}

Here's the response:  
{  
"error": {  
"root\_cause": [  
{  
"type": "illegal\_argument\_exception",  
"reason": "[essvr1:9200] not whitelisted in reindex.remote.whitelist"  
}  
],  
"type": "illegal\_argument\_exception",  
"reason": "[essvr1:9200] not whitelisted in reindex.remote.whitelist"  
},  
"status": 400  
}

Here's the yml file who's contents have been verified via a CURL GET of the cluster's settings:

# ======================== Elasticsearch Configuration =========================

# 

# NOTE: Elasticsearch comes with reasonable defaults for most settings.

# Before you set out to tweak and tune the configuration, make sure you

# understand what are you trying to accomplish and the consequences.

# 

# The primary way of configuring a node is via this file. This template lists

# the most important settings you may want to configure for a production cluster.

# 

# Please consult the documentation for further information on configuration options:

# [https://www.elastic.co/guide/en/elasticsearch/reference/index.html](https://www.elastic.co/guide/en/elasticsearch/reference/index.html)

# 

# ---------------------------------- Cluster -----------------------------------

# 

# Use a descriptive name for your cluster:

# 

cluster.name: es76  
cluster.max\_shards\_per\_node: 3000

# 

# ------------------------------------ Node ------------------------------------

# 

# Use a descriptive name for the node:

# 

node.name: es76-node00

# 

# Add custom attributes to the node:

# 

#node.attr.rack: r1  
node.master: true  
node.data: false  
node.ingest: false

# 

# ----------------------------------- Paths ------------------------------------

# 

# Path to directory where to store the data (separate multiple locations by comma):

# 

path.data: /var/lib/elasticsearch

# 

# Path to log files:

# 

path.logs: /var/log/elasticsearch

# 

# ----------------------------------- Memory -----------------------------------

# 

# Lock the memory on startup:

# 

bootstrap.memory\_lock: true

# 

# Make sure that the heap size is set to about half the memory available

# on the system and that the owner of the process is allowed to use this

# limit.

# 

# Elasticsearch performs poorly when the system is swapping the memory.

# 

# ---------------------------------- Network -----------------------------------

# 

# Set the bind address to a specific IP (IPv4 or IPv6):

# 

network.host: ["localhost", "xxx.xxx.xxx.xxx"]  
network.bind\_host: ["localhost", "xxx.xxx.xxx.xxx"]  
network.publish\_host: xxx.xxx.xxx.xxx

# 

# Set a custom port for HTTP:

# 

#http.port: 9200

# 

# For more information, consult the network module documentation.

# 

# --------------------------------- Discovery ----------------------------------

# 

# Pass an initial list of hosts to perform discovery when this node is started:

# The default list of hosts is ["127.0.0.1", "[::1]"]

# 

discovery.zen.ping.unicast.hosts: ["xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx"]  
#discovery.seed\_hosts: ["xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx"]  
cluster.initial\_master\_nodes: ["xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx", "xxx.xxx.xxx.xxx"]

# 

# Bootstrap the cluster using an initial set of master-eligible nodes:

# 

discovery.zen.minimum\_master\_nodes: 3

# 

# For more information, consult the discovery and cluster formation module documentation.

# 

# ---------------------------------- Gateway -----------------------------------

# 

# Block initial recovery after a full cluster restart until N nodes are started:

# 

#gateway.recover\_after\_nodes: 3

# 

# For more information, consult the gateway module documentation.

# 

# ---------------------------------- Various -----------------------------------

# 

# Require explicit names when deleting indices:

# 

#action.destructive\_requires\_name: true  
reindex.remote.whitelist: "essvr1:9200, essvr2:9200"

Any help in overcoming this roadblock is most appreciated.

Thanks.

Dave

---

<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:** [July 1, 2020, 8:10pm UTC](https://discuss.elastic.co/t/not-whitelisted-in-reindex-remote-whitelist-revived/235630/2 "2020-07-01T20:10:31Z")

</div>

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