【已解答】云安全监控无法安装
为了能快速了解并处理您的问题，请提供以下基础信息：面板、插件版本：云安全监控系统版本：ubuntu22.04
问题描述：新安装的Ubuntu22.04，直接安装云安全监控后报错
相关截图（日志、错误）：
Created symlink /etc/systemd/system/multi-user.target.wants/btm.service → /lib/systemd/system/btm.service.
Starting BT-SQLITE-SERVER... done
Starting Bt-Monitor...done
正在初始化云监控主控端...
正在给本机安装云监控被控端,请等待...
正在检测系统关键目录是否可写
本机连接云监控主控端的状态码是: 000
---------------------------------------------------
Error-错误: 本机与云监控主控端通信失败!
尝试以下解决方法：
1、检查主控服务是否正常启动，检查命令：btm status
2、检查主控端口 806 防火墙/安全组是否是否已经放行
3、检查主控端地址是否正确：https://127.0.0.1:806
4、尝试执行命令检是否可以连接到主控端：curl -kv https://127.0.0.1:806
---------------------------------------------------
root 317560.70.2 877120 17740 ? Sl 06:47 0:00 /www/server/bt-monitor/pyenv/bin/python3 -u /www/server/bt-monitor/BT-SQLITE-SERVER
root 317770.40.5 160320 43648 ? Sl 06:47 0:00 /www/server/bt-monitor/pyenv/bin/python3.7 /www/server/bt-monitor/BT-MONITOR
Stopping Bt-Monitor...done
BT-SQLITE-SERVER(pid 31756) already running
Starting Bt-Monitor...done
安装云监控被控端失败，正在尝试重新安装！
正在检测系统关键目录是否可写
本机连接云监控主控端的状态码是: 000
---------------------------------------------------
Error-错误: 本机与云监控主控端通信失败!
尝试以下解决方法：
1、检查主控服务是否正常启动，检查命令：btm status
2、检查主控端口 806 防火墙/安全组是否是否已经放行
3、检查主控端地址是否正确：https://127.0.0.1:806
4、尝试执行命令检是否可以连接到主控端：curl -kv https://127.0.0.1:806
---------------------------------------------------
=================================================
ERROR: 安装云监控被控端失败，请尝试重新安装！
Ubuntu 22.04.4 LTS
\l
Bit:64 Mem:7902M Core:8
Linux monitor 5.15.0-100-generic #110-Ubuntu SMP Wed Feb 7 13:27:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
请截图以上报错信息发帖至论坛www.bt.cn/bbs求助
root@monitor:~# curl -kv https://127.0.0.1:806
* Trying 127.0.0.1:806...
* Connected to 127.0.0.1 (127.0.0.1) port 806 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*subject: CN=125.46.49.234
*start date: Mar 11 06:49:26 2024 GMT
*expire date: Mar9 06:49:26 2034 GMT
*issuer: CN=125.46.49.234
*SSL certificate verify result: self-signed certificate (18), continuing anyway.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/1.1
> Host: 127.0.0.1:806
> User-Agent: curl/7.81.0
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 403 FORBIDDEN
< Content-Type: text/html
< Content-Length: 138
< Server: nginx
< Connection: keep-alive
< X-Frame-Options: SAMEORIGIN
< Date: Mon, 11 Mar 2024 09:15:21 GMT
<
* TLSv1.2 (IN), TLS header, Supplemental data (23):
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
* Connection #0 to host 127.0.0.1 left intact
</html>root@monitor:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:1f:14:f3 brd ff:ff:ff:ff:ff:ff
altname enp2s0
inet 192.168.0.25/24 metric 100 brd 192.168.0.255 scope global dynamic ens32
valid_lft 6909sec preferred_lft 6909sec
inet6 fe80::20c:29ff:fe1f:14f3/64 scope link
valid_lft forever preferred_lft forever
在同一台机器即安装主控又安装被控吗，地址怎么会是127.0.0.1
另外建议，云安全监控页面添加专属qq群
ESXI中新装的Ubuntu
页:
[1]