Can not convert to transport address. skipping. – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Can not convert to transport address. skipping. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, discovery-azure-classic, hosts, plugins and repository-azure.

Log Context

Log “Can not convert [{}] to transport address. skipping. [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     for (TransportAddress address : addresses) {
                        logger.trace("adding {}; transport_address {}"; networkAddress; address);
                } catch (Exception e) {
                    logger.warn("can not convert [{}] to transport address. skipping. [{}]"; networkAddress; e.getMessage());

        logger.debug("{} addresses added"; dynamicHosts.size());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content