Elastic Search Agent注册失败求助:Fleet Server主动拒绝连接
问题描述
尝试将Windows虚拟机上的Elastic Agent注册到Kali Purple虚拟机上的Fleet Server,服务器处于在线状态,但每次连接均失败。已尝试使用--insecure参数并以管理员身份运行注册命令,问题仍未解决。
错误日志
{"log.level":"warn","@timestamp":"2023-06-06T19:28:55.258+0100","log.logger":"tls","log.origin": {"file.name":"tlscommon/tls_config.go","file.line":104},"message":"SSL/TLS verifications disabled.","ecs.version":"1.6.0"} {"log.level":"info","@timestamp":"2023-06-06T19:28:55.564+0100","log.origin":{"file.name":"cmd/enroll_cmd.go","file.line":478},"message":"Starting enrollment to URL: https://10.0.2.15:443/","ecs.version":"1.6.0"} {"log.level":"warn","@timestamp":"2023-06-06T19:28:55.790+0100","log.logger":"tls","log.origin":{"file.name":"tlscommon/tls_config.go","file.line":104},"message":"SSL/TLS verifications disabled.","ecs.version":"1.6.0"} Error: fail to enroll: fail to execute request to fleet-server: dial tcp 10.0.2.15:443: connectex: No connection could be made because the target machine actively refused it. Error: enroll command failed with exit code: 1
排查与解决步骤
- 确认Fleet Server端口监听状态:在Kali Purple虚拟机执行
netstat -tulpn | grep 443,检查Fleet Server是否真的在监听443端口。如果无结果,说明Fleet Server未正常启动,或者配置的监听端口并非443。 - 测试虚拟机网络连通性:在Windows虚拟机上,先用
ping 10.0.2.15验证基础网络互通;再用PowerShell命令Test-NetConnection 10.0.2.15 -Port 443测试443端口是否可访问。若ping不通,先解决虚拟机间的网络互通问题;若ping通但端口无法访问,继续下一步排查。 - 检查Kali Purple防火墙规则:执行
ufw status查看防火墙状态,若处于开启状态,添加443端口的入站放行规则:ufw allow 443/tcp。若使用iptables,执行iptables -L -n检查是否存在拦截443端口的规则,必要时添加放行规则。 - 验证Fleet Server绑定地址:查看Fleet Server配置文件,确认其绑定的是
0.0.0.0或虚拟机实际IP(10.0.2.15),而非仅绑定127.0.0.1。若绑定本地回环地址,外部虚拟机无法建立连接。 - 检查虚拟机网络模式:若两台虚拟机使用NAT模式,确认端口转发规则是否配置正确;若使用桥接模式,确保二者处于同一网段且能互相访问。
内容的提问来源于stack exchange,提问作者Charnpreet Singh
相关产品推荐
相关产品推荐

