Elasticsearch踩坑：received plaintext http traffic on an https channel, closing connection Netty4HttpCh

最新推荐文章于 2024-10-22 21:24:34 发布
原创 最新推荐文章于 2024-10-22 21:24:34 发布 · 1.9k 阅读 · 5 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#elasticsearch #java #大数据

访问Elasticsearch时遇到HTTPtrafficonanHTTPSchannel错误，原因是Elasticsearch启用了安全认证。为解决此问题，需编辑config目录下的elasticsearch.yml配置文件，将安全认证选项由true改为false，从而实现无密码访问。

踩坑：

当我们访问ip+9200 验证是否启动成功时报错

received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/172.16.5.10:9200,
remoteAddress=/172.16.11.68:11111}

如图：
在这里插入图片描述
原因：Elasticsearch开启了安全认证
解决：在config/目录下面的elasticsearch.yml配置文件，把安全认证开关从原先的true改成false，实现免密登录访问即可，修改如图：
在这里插入图片描述

Elasticsearch报错：received plaintext http traffic on an https channel, closing connection
SiChuLiuDa_的博客
05-15 2618
笔者使用的是Windows版elasticsearch，但笔者觉得linux上的解决方法也是相通的，相信聪明的读者很快就能找到解决的办法（看好你哟，加油！Fight）。1.问题："Win+R"，然后键入"cmd"打开命令窗口，进入elasticsearch安装目录，进入bin目录，使用"elasticsearch.bat"命令启动elasticsearch，然后输入网址：http://localhost:9200，网页却显示：“当前无法使用此页面”，网页显示如图1所示：图1 网页显示。
Spring Boot+Netty
m0_54854484的博客
12-05 982
因工作中需要给第三方屏幕厂家下发广告，音频，图片等内容，对方提供TCP接口于是我使用Netty长链接进行数据传输。
[转](1条消息) ElasticSearch 启动失败无法访问9200
jiaoqi6132的博客
12-15 1022
是因为开启了认证。在文件中把设置成false即可windows 下直接启动，见到 started 为成功启动，访问 htttp://localhost:9200 需要输入密码，是因为开启了密码验证模式。找了一轮没看到有账号密码，干脆就设置免密登录就好。找到文件， 把属性设置为false即可。
Elasticsearch报错： received plaintext http traffic on an https channel, closing connection ...
雨中深巷的油纸伞
05-13 5801
Elasticsearch报错：received plaintext http traffic on an https channel, closing connection Netty4HttpChannel。 现象，当启动Elasticsearch后，在浏览器输入地址 http://localhost:9200/ 后，报错 received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{l
Elasticsearch报错：received plaintext http traffic on an https channel, closing connection Netty4HttpCh
qq_32379229的博客
04-22 4088
原因: ES8默认开启了ssl认证，导致无法访问9200端口 修改 elasticsearch.yml配置:xpack.security.enabled:把true改成false
[2025-07-09T16:11:52,075][WARN ][o.e.h.n.Netty4HttpServerTransport] [node-1] received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/[0:0:0:0:0:0:0:1]:9200, remoteAddress=/[0:0:0:0:0:0:0:1]:62848}
07-10
> `received plaintext http traffic on an https channel, closing connection` 该信息表明客户端尝试通过 HTTP 协议访问了一个配置为 HTTPS 的 Elasticsearch 节点，导致连接被终止。这种行为通常发生在启用了 ...
[2025-11-01T19:51:56,272][WARN ][o.e.h.n.Netty4HttpServerTransport] [LAPTOP-P7N1D4LQ] received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/[0:0:0:0:0:0:0:1]:9200, remoteAddress=/[0:0:0:0:0:0:0:1]:58365}
最新发布
11-02
```plaintext http.type: ssl http.ssl.enabled: true http.ssl.key: /path/to/your/private.key http.ssl.certificate: /path/to/your/certificate.crt http.ssl.certificate_authorities: [ "/path/to/your/ca.crt...
{"@timestamp":"2025-03-31T13:45:02.132Z", "log.level": "WARN", "message":"This node is a fully-formed single-node cluster with cluster UUID [2TJKMZR1TNKLU5kjkpihFA], but it is configured as if to discover other nodes and form a multi-node cluster via the [discovery.seed_hosts=[elasticsearch-master-headless]] setting. Fully-formed clusters do not attempt to discover other nodes, and nodes with different cluster UUIDs cannot belong to the same cluster. The cluster UUID persists across restarts and can only be changed by deleting the contents of the node's data path(s). Remove the discovery configuration to suppress this message.", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][scheduler][T#1]","log.logger":"org.elasticsearch.cluster.coordination.Coordinator","elasticsearch.cluster.uuid":"2TJKMZR1TNKLU5kjkpihFA","elasticsearch.node.id":"mtYdBdhQRLW1Fe7ebdHtrA","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch"} {"@timestamp":"2025-03-31T13:45:03.995Z", "log.level": "WARN", "message":"received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/127.0.0.1:9200, remoteAddress=/127.0.0.1:48954}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][transport_worker][T#1]","log.logger":"org.elasticsearch.xpack.security.transport.netty4.SecurityNetty4HttpServerTransport","elasticsearch.cluster.uuid":"2TJKMZR1TNKLU5kjkpihFA","elasticsearch.node.id":"mtYdBdhQRLW1Fe7ebdHtrA","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch"} {"@timestamp":"2025-03-31T13:45:11.239Z", "log.level": "WARN", "message":"received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/127.0.0.1:9200, remoteAddress=/127.0.0.1:48958}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch-master-0][transport_worker][T#1]","log.logger":"org.elasticsearch.xpack.security.transport.netty4.SecurityNetty4HttpServerTransport","elasticsearch.cluster.uuid":"2TJKMZR1TNKLU5kjkpihFA","elasticsearch.node.id":"mtYdBdhQRLW1Fe7ebdHtrA","elasticsearch.node.name":"elasticsearch-master-0","elasticsearch.cluster.name":"elasticsearch"}
04-01
好的，我现在需要处理用户提供的三个Elasticsearch日志条目，并解释其中存在的问题和解决方法。首先，我要逐一分析每条日志的内容，理解它们的警告信息，然后找出根本原因，最后给出解决建议。 首先看第一条日志。...
docker安装Elasticsearch8.2.3
weixin_56432168的博客
12-30 441
docker安装Elasticsearch8.2.3
[2025-07-01T18:31:34,851][WARN ][o.e.t.OutboundHandler ] [node-3] send message failed [channel: Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:44976, remoteAddress=null, profile=default}] io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 485454502f312e30203430302042616420526571756573740d0a582d656c61737469632d70726f647563743a20456c61737469637365617263680d0a636f6e74656e742d747970653a206170706c69636174696f6e2f6a736f6e3b20636861727365743d5554462d380d0a636f6e74656e742d6c656e6774683a203436390d0a0d0a7b226572726f72223a7b22726f6f745f6361757365223a5b7b2274797065223a22696c6c6567616c5f617267756d656e745f657863657074696f6e222c22726561736f6e223a22696e76616c69642076657273696f6e20666f726d61743a20c3895c753030303145c29cc2a35c7530303031c398c282c2b7c2b8415d5c75303031445c7530303137ce9c7e455c75303031315c753030314556555c75303030335c5c57c2a7c39a60c392584d5c7530303132c28e5c7530303030285c75303031335c75303030325c75303031335c7530303031c3802cc3802bc38030c3802fc38024c38023c38028c38027c380227d5d2c2274797065223a22696c6c6567616c5f617267756d656e745f657863657074696f6e222c22726561736f6e223a22696e76616c69642076657273696f6e20666f726d61743a20c3895c753030303145c29cc2a35c7530303031c398c282c2b7c2b8415d5c75303031445c7530303137ce9c7e455c75303031315c753030314556555c75303030335c5c57c2a7c39a60c392584d5c7530303132c28e5c7530303030285c75303031335c75303030325c75303031335c7530303031c3802cc3802bc38030c3802fc38024c38023c38028c38027c380227d2c22737461747573223a3430307d at io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1216) [netty-handler-4.1.66.Final.jar:4.1.66.Final] at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1286) [netty-handler-4.1.66.Final.jar:4.1.66.Final] at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:507) [netty-codec-4.1.66.Final.jar:4.1.66.Final] at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:446) [netty-codec-4.1.66.Final.jar:4.1.66.Final] at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) [netty-codec-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:620) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:583) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-transport-4.1.66.Final.jar:4.1.66.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) [netty-common-4.1.66.Final.jar:4.1.66.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.66.Final.jar:4.1.66.Final] at java.lang.Thread.run(Thread.java:834) [?:?] [2025-07-01T18:31:34,853][WARN ][o.e.x.c.s.t.n.SecurityNetty4Transport] [node-3] received plaintext traffic on an encrypted channel, closing connection Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:53988, remoteAddress=null, profile=default} [2025-07-01T18:31:34,853][WARN ][o.e.x.c.s.t.n.SecurityNetty4Transport] [node-3] received plaintext traffic on an encrypted channel, closing connection Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:44976, remoteAddress=null, profile=default} [2025-07-01T18:31:34,853][WARN ][o.e.x.c.s.t.n.SecurityNetty4Transport] [node-3] received plaintext traffic on an encrypted channel, closing connection Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:41996, remoteAddress=null, profile=default}
07-02
2. **`received plaintext traffic on an encrypted channel`**: - 这表明客户端尝试通过加密通道（如 HTTPS）发送明文数据（如 HTTP），导致服务器拒绝连接。 ### 可能的原因 1. **客户端配置错误**: - 客户端...
ElasticSearch~received plaintext http traffic on an https channel, closing connection Netty4HttpChan
feizuiku0116的博客
12-29 3449
ElasticSearch默认开启了安全认证，需要将安全认证关掉。ElasticSearch服务正常启动，但是在浏览器上无法访问。
Elasticsearch 8.0报错：received plaintext http traffic on an https channel, closing connection
热门推荐
换条路吧，编程没意思的~
02-24 4万+
ES配置启动成功了，就是客户端访问服务端出现这个错误 原因：是因为ES8默认开启了 ssl 认证。 修改elasticsearch.yml配置文件 将xpack.security.enabled设置为false xpack.security.enabled: false 修改完毕，重启，解决问题！！！ ...
【ElasticSearch】received plaintext http traffic on an https channel, closing connection Netty4HttpCha
杜小舟的博客
08-24 617
解决received plaintext http traffic on an https channel, closing connection Netty4HttpChannel 问题
elasticsearch8.0 client提示 received plaintext http traffic on an https channel
2301_80826391的博客
10-22 546
一劳永逸的解决办法是关闭安全认证，在config/elasticsearch.yml里。从es8.0开始，开启了安全机制，我们要访问https://ip+port才能访问到。，因为kibana默认是通过https连接的。如果用http访问，会出现以下错误。所以还需要修改kibana的配置。内容在配置文件的最底下。
ES 服务启动访问9200无反应 报错 received plaintext http traffic on an https channel, closing connection解决方案
weixin_45966674的博客
01-26 1617
Elasticsearch服务器收到了明文的HTTP流量，但该通道应该是用于HTTPS的。因此，服务器关闭了这个连接。找到里面的 xpack.security.enabled 这个是控制是否开启https格式的配置项。然后 找到 elasticsearch.yml 打开它进行编辑。我们可以打开ES目录下的 config 配置文件存储目录。今天第一次装ES 出师不利 直接先来了一个警告。如果是true 那确实会有这个问题。然后 再次运行服务 它就起来啦。我们改成 false。
启动ElasticSecrch无法访问问题： received plaintext http traffic on an https channel, closing connection Netty
世上哪有什么岁月静好,不过是有人替你负重前行
01-13 872
原因是Elasticsearch在Windows下开启了安全认证，虽然started成功，但访问http://localhost:9200/解决方法就是修改ElasticSecrch.yml的配置文件，位置在哪就不用多说了叭，修改安全认证的地方。当启动Elasticsearch后，在浏览器输入地址 http://localhost:9200/标红框框的地方true改为false就好了，再去访问浏览器：9200。
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值