Briefly, this error occurs when Elasticsearch is configured to bind to any IP address (0.0.0.0), but it needs a specific IP to publish to other nodes. This can happen if the server has multiple network interfaces. To resolve this, you can specify a non-wildcard IP address in the Elasticsearch configuration file (elasticsearch.yml) for the network.publish_host setting. Alternatively, if you want Elasticsearch to choose an IP automatically, ensure that the server has only one non-loopback IP address.
This guide will help you check for common problems that cause the log ” publish address: {{}} is a wildcard address; falling back to first non-loopback: {{}} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: network.
Log Context
Log “publish address: {{}} is a wildcard address; falling back to first non-loopback: {{}}” classname is NetworkService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
// wildcard address; probably set by network.host
if (address.isAnyLocalAddress()) {
InetAddress old = address;
address = NetworkUtils.getFirstNonLoopbackAddresses()[0];
logger.warn("publish address: {{}} is a wildcard address; falling back to first non-loopback: {{}}";
NetworkAddress.format(old); NetworkAddress.format(address));
}
}
return address;
}
