Log Received plaintext traffic on an encrypted channel; closing connection – How To Solve Related Issues



Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Received plaintext traffic on an encrypted channel; closing connection” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

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









Find Configuration Errors

Try The Tool