雷池专业版是否支持将配置导出为单独的文件，满足管理需要？
luoli
更新于 17 小时前
不支持。可打包整个雷池目录，但文件可能过大，不推荐。
0
2
如何使用CURL命令排查使用雷池碰到的网络问题
张华杰
更新于 1 天前
curl（CommandLine Uniform Resource Locator），是一个利用 URL 语法，在命令行终端下使用的网络请求工具，支持 HTTP、HTTPS、FTP 等协议。
大多数系统都默认有curl工具，直接可以在终端使用，演示用的环境为ubuntu20
输入curl -V 就能看到，当前机是否可以使用curl，且会输出当前版本
用于排查当前雷池环境是否正常启动9443监听
在雷池机器上执行：curl -k -v https://127.0.0.1:9443
关注点：
这里把9443改成了9444，是一个未被使用的端口，看到请求就会报错无法连接
常用于确认非雷池机器与雷池管理端的网络环境
curl -k -v https://121.199.46.182:9443
curl -k -v https://jaryn.top:9443
其他curl的用法可以自行百度或者问AI了解
0
1
建议增加 URL 上下文白名单机制
紫东来
更新于 2 天前
对于站点的 api 接口，通常需要暴露给外部调用，但是如果开启等候室、人机认证以及机器人识别规则会导致接口不可用。但接口仍然有防攻击的需求。建议增加白名单机制。
举例 在站点 www.abcd.com 添加 白名单 /api/* 则 www.abcd.com/api/* 路径下的请求不受 等候室、人机认证以及机器人识别规则等影响。
1
2
微信小程序访问问题
普罗米修斯
更新于 3 天前
没有安装雷池之前，所有请求通过nginx，现在安装雷池之后，用雷池订阅域名+443端口，代理到上游服务器的一个端口，然后通过nginx监听这个端口，所有应用都好着，就是微信小程序无法正常请求接口。这是为什么
0
10
docker部署safeline-detector容器无法启动
黑曜帝制
更新于 3 天前
RT：
故障日志如下
1'/detector/snserver.yml' -> '/detector/detector.yml' 2/resources/detector/detector.yml 3no /resources/detector/detector.yml file 4'/detector/libfusion2.so' -> '/detector/config/libfusion2.so' 5worker exit error: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } 6Error: "the child start failed" 7[2025-02-18 16:12:00.117] [1] [INFO ] all thread shutdown 8[2025-02-18 16:12:00.117] [0] [ERROR] parent receive None from child 9worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 10Error: "the child start failed" 11worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 12worker send shutdown error: SendError(WorkerShutdown) 13[2025-02-18 16:12:20.234] [1] [INFO ] all thread shutdown 14[2025-02-18 16:12:20.234] [0] [ERROR] parent receive None from child 15[2025-02-18 16:12:20.234] [0] [ERROR] handle the child error: the child start failed 16worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 17worker send shutdown error: SendError(WorkerShutdown) 18worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 19Error: "the child start failed" 20thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 21note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 22[2025-02-18 16:12:40.310] [1] [INFO ] all thread shutdown 23[2025-02-18 16:12:40.310] [0] [ERROR] parent receive None from child 24worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 25Error: "the child start failed" 26[2025-02-18 16:13:00.384] [1] [INFO ] all thread shutdown 27thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 28note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 29[2025-02-18 16:13:00.384] [0] [ERROR] parent receive None from child 30[2025-02-18 16:13:00.384] [0] [ERROR] handle the child error: the child start failed 31worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 32Error: "the child start failed" 33thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: hyper::Error(Listen, Custom { kind: Other, error: "failed to find event loop" })', src/thread/monitor.rs:54:82 34note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 35[2025-02-18 16:13:20.459] [1] [INFO ] all thread shutdown 36[2025-02-18 16:13:20.459] [0] [ERROR] parent receive None from child 37worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 38Error: "the child start failed" 39thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 40note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 41[2025-02-18 16:13:40.542] [1] [INFO ] all thread shutdown 42[2025-02-18 16:13:40.542] [0] [ERROR] parent receive None from child 432025/02/18 16:13:50 ERROR init config failed err="detector http request failed" 44chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 45chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 46chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 47chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 48chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 49chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 50chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 51chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 52chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory
0
3
当前 IP
雷池专业版是否支持将配置导出为单独的文件，满足管理需要？
luoli
更新于 17 小时前
不支持。可打包整个雷池目录，但文件可能过大，不推荐。
0
2
如何使用CURL命令排查使用雷池碰到的网络问题
张华杰
更新于 1 天前
curl（CommandLine Uniform Resource Locator），是一个利用 URL 语法，在命令行终端下使用的网络请求工具，支持 HTTP、HTTPS、FTP 等协议。
大多数系统都默认有curl工具，直接可以在终端使用，演示用的环境为ubuntu20
输入curl -V 就能看到，当前机是否可以使用curl，且会输出当前版本
用于排查当前雷池环境是否正常启动9443监听
在雷池机器上执行：curl -k -v https://127.0.0.1:9443
关注点：
这里把9443改成了9444，是一个未被使用的端口，看到请求就会报错无法连接
常用于确认非雷池机器与雷池管理端的网络环境
curl -k -v https://121.199.46.182:9443
curl -k -v https://jaryn.top:9443
其他curl的用法可以自行百度或者问AI了解
0
1
建议增加 URL 上下文白名单机制
紫东来
更新于 2 天前
对于站点的 api 接口，通常需要暴露给外部调用，但是如果开启等候室、人机认证以及机器人识别规则会导致接口不可用。但接口仍然有防攻击的需求。建议增加白名单机制。
举例 在站点 www.abcd.com 添加 白名单 /api/* 则 www.abcd.com/api/* 路径下的请求不受 等候室、人机认证以及机器人识别规则等影响。
1
2
微信小程序访问问题
普罗米修斯
更新于 3 天前
没有安装雷池之前，所有请求通过nginx，现在安装雷池之后，用雷池订阅域名+443端口，代理到上游服务器的一个端口，然后通过nginx监听这个端口，所有应用都好着，就是微信小程序无法正常请求接口。这是为什么
0
10
docker部署safeline-detector容器无法启动
黑曜帝制
更新于 3 天前
RT：
故障日志如下
1'/detector/snserver.yml' -> '/detector/detector.yml' 2/resources/detector/detector.yml 3no /resources/detector/detector.yml file 4'/detector/libfusion2.so' -> '/detector/config/libfusion2.so' 5worker exit error: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } 6Error: "the child start failed" 7[2025-02-18 16:12:00.117] [1] [INFO ] all thread shutdown 8[2025-02-18 16:12:00.117] [0] [ERROR] parent receive None from child 9worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 10Error: "the child start failed" 11worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 12worker send shutdown error: SendError(WorkerShutdown) 13[2025-02-18 16:12:20.234] [1] [INFO ] all thread shutdown 14[2025-02-18 16:12:20.234] [0] [ERROR] parent receive None from child 15[2025-02-18 16:12:20.234] [0] [ERROR] handle the child error: the child start failed 16worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 17worker send shutdown error: SendError(WorkerShutdown) 18worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 19Error: "the child start failed" 20thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 21note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 22[2025-02-18 16:12:40.310] [1] [INFO ] all thread shutdown 23[2025-02-18 16:12:40.310] [0] [ERROR] parent receive None from child 24worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 25Error: "the child start failed" 26[2025-02-18 16:13:00.384] [1] [INFO ] all thread shutdown 27thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 28note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 29[2025-02-18 16:13:00.384] [0] [ERROR] parent receive None from child 30[2025-02-18 16:13:00.384] [0] [ERROR] handle the child error: the child start failed 31worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 32Error: "the child start failed" 33thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: hyper::Error(Listen, Custom { kind: Other, error: "failed to find event loop" })', src/thread/monitor.rs:54:82 34note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 35[2025-02-18 16:13:20.459] [1] [INFO ] all thread shutdown 36[2025-02-18 16:13:20.459] [0] [ERROR] parent receive None from child 37worker exit error: Os { code: 95, kind: Uncategorized, message: "Operation not supported" } 38Error: "the child start failed" 39thread 'monitor' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to find event loop" }', src/thread/monitor.rs:53:65 40note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 41[2025-02-18 16:13:40.542] [1] [INFO ] all thread shutdown 42[2025-02-18 16:13:40.542] [0] [ERROR] parent receive None from child 432025/02/18 16:13:50 ERROR init config failed err="detector http request failed" 44chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 45chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 46chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 47chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 48chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 49chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 50chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 51chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory 52chown: changing ownership of '/resources/detector/snserver.sock.new': No such file or directory
0
3
