【已解答】云安全监控无法安装

为了能快速了解并处理您的问题，请提供以下基础信息：

面板、插件版本：云安全监控

系统版本：ubuntu22.04

问题描述：新安装的Ubuntu22.04，直接安装云安全监控后报错

相关截图（日志、错误）：

1. Created symlink /etc/systemd/system/multi-user.target.wants/btm.service → /lib/systemd/system/btm.service.
   
2. Starting BT-SQLITE-SERVER...    done
   
3. Starting Bt-Monitor...  done
   
4. 正在初始化云监控主控端...
   
5. 正在给本机安装云监控被控端,请等待...
   
6. 正在检测系统关键目录是否可写
   
7. 本机连接云监控主控端的状态码是: 000
   
8. ---------------------------------------------------
   
9. Error-错误: 本机与云监控主控端通信失败!
   
10. 
    
11. 尝试以下解决方法：
    
12. 1、检查主控服务是否正常启动，检查命令：btm status
    
13. 2、检查主控端口 806 防火墙/安全组是否是否已经放行
    
14. 3、检查主控端地址是否正确：https://127.0.0.1:806
    
15. 4、尝试执行命令检是否可以连接到主控端：curl -kv https://127.0.0.1:806
    
16. ---------------------------------------------------
    
17. 
    
18. root       31756  0.7  0.2 877120 17740 ?        Sl   06:47   0:00 /www/server/bt-monitor/pyenv/bin/python3 -u /www/server/bt-monitor/BT-SQLITE-SERVER
    
19. root       31777  0.4  0.5 160320 43648 ?        Sl   06:47   0:00 /www/server/bt-monitor/pyenv/bin/python3.7 /www/server/bt-monitor/BT-MONITOR
    
20. Stopping Bt-Monitor...  done
    
21. BT-SQLITE-SERVER(pid 31756) already running
    
22. Starting Bt-Monitor...  done
    
23. 安装云监控被控端失败，正在尝试重新安装！
    
24. 正在检测系统关键目录是否可写
    
25. 本机连接云监控主控端的状态码是: 000
    
26. ---------------------------------------------------
    
27. Error-错误: 本机与云监控主控端通信失败!
    
28. 
    
29. 尝试以下解决方法：
    
30. 1、检查主控服务是否正常启动，检查命令：btm status
    
31. 2、检查主控端口 806 防火墙/安全组是否是否已经放行
    
32. 3、检查主控端地址是否正确：https://127.0.0.1:806
    
33. 4、尝试执行命令检是否可以连接到主控端：curl -kv https://127.0.0.1:806
    
34. ---------------------------------------------------
    
35. =================================================
    
36. ERROR: 安装云监控被控端失败，请尝试重新安装！
    
37. Ubuntu 22.04.4 LTS
    
38. \l
    
39. Bit:64 Mem:7902M Core:8
    
40. 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
    
41. 请截图以上报错信息发帖至论坛www.bt.cn/bbs求助
    
42. root@monitor:~# curl -kv https://127.0.0.1:806
    
43. *   Trying 127.0.0.1:806...
    
44. * Connected to 127.0.0.1 (127.0.0.1) port 806 (#0)
    
45. * ALPN, offering h2
    
46. * ALPN, offering http/1.1
    
47. * TLSv1.0 (OUT), TLS header, Certificate Status (22):
    
48. * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    
49. * TLSv1.2 (IN), TLS header, Certificate Status (22):
    
50. * TLSv1.3 (IN), TLS handshake, Server hello (2):
    
51. * TLSv1.2 (IN), TLS header, Finished (20):
    
52. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
53. * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    
54. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
55. * TLSv1.3 (IN), TLS handshake, Certificate (11):
    
56. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
57. * TLSv1.3 (IN), TLS handshake, CERT verify (15):
    
58. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
59. * TLSv1.3 (IN), TLS handshake, Finished (20):
    
60. * TLSv1.2 (OUT), TLS header, Finished (20):
    
61. * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    
62. * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    
63. * TLSv1.3 (OUT), TLS handshake, Finished (20):
    
64. * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
    
65. * ALPN, server did not agree to a protocol
    
66. * Server certificate:
    
67. *  subject: CN=125.46.49.234
    
68. 
    
69. *  start date: Mar 11 06:49:26 2024 GMT
    
70. *  expire date: Mar  9 06:49:26 2034 GMT
    
71. *  issuer: CN=125.46.49.234
    
72. 
    
73. *  SSL certificate verify result: self-signed certificate (18), continuing anyway.
    
74. * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    
75. > GET / HTTP/1.1
    
76. > Host: 127.0.0.1:806
    
77. > User-Agent: curl/7.81.0
    
78. > Accept: */*
    
79. >
    
80. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
81. * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    
82. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
83. * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    
84. * old SSL session ID is stale, removing
    
85. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
86. * Mark bundle as not supporting multiuse
    
87. < HTTP/1.1 403 FORBIDDEN
    
88. < Content-Type: text/html
    
89. < Content-Length: 138
    
90. < Server: nginx
    
91. < Connection: keep-alive
    
92. < X-Frame-Options: SAMEORIGIN
    
93. < Date: Mon, 11 Mar 2024 09:15:21 GMT
    
94. <
    
95. * TLSv1.2 (IN), TLS header, Supplemental data (23):
    
96. <html>
    
97. <head><title>403 Forbidden</title></head>
    
98. <body>
    
99. <center><h1>403 Forbidden</h1></center>
    
100. <hr><center>nginx</center>
     
101. </body>
     
102. * Connection #0 to host 127.0.0.1 left intact
     
103. </html>root@monitor:~# ip addr
     
104. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
     
105.     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     
106.     inet 127.0.0.1/8 scope host lo
     
107.        valid_lft forever preferred_lft forever
     
108.     inet6 ::1/128 scope host
     
109.        valid_lft forever preferred_lft forever
     
110. 2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
     
111.     link/ether 00:0c:29:1f:14:f3 brd ff:ff:ff:ff:ff:ff
     
112.     altname enp2s0
     
113.     inet 192.168.0.25/24 metric 100 brd 192.168.0.255 scope global dynamic ens32
     
114.        valid_lft 6909sec preferred_lft 6909sec
     
115.     inet6 fe80::20c:29ff:fe1f:14f3/64 scope link
     
116.        valid_lft forever preferred_lft forever

复制代码

在同一台机器即安装主控又安装被控吗，地址怎么会是127.0.0.1
另外建议，云安全监控页面添加专属qq群

ESXI中新装的Ubuntu