"not whitelisted in reindex.remote.whitelist" Revived

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"
"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:


---------------------------------- 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


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 ["", "[::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.



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