Received plaintext traffic on an encrypted channel; closing connection – How to solve related issues

Average Read Time

2 Mins

Received plaintext traffic on an encrypted channel; closing connection – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Received plaintext traffic on an encrypted channel; closing connection ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Received plaintext traffic on an encrypted channel; closing connection {}” classname is SecurityNetty4Transport.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         } else if (SSLExceptionHelper.isNotSslRecordException(e)) {
            if (logger.isTraceEnabled()) {
                logger.trace(
                        new ParameterizedMessage("received plaintext traffic on an encrypted channel; closing connection {}"; channel); e);
            } else {
                logger.warn("received plaintext traffic on an encrypted channel; closing connection {}"; channel);
            }
            CloseableChannel.closeChannel(channel);
        } else if (SSLExceptionHelper.isCloseDuringHandshakeException(e)) {
            if (logger.isTraceEnabled()) {
                logger.trace(new ParameterizedMessage("connection {} closed during ssl handshake"; channel); e);




 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content