连接测试：找不到任何连接日志！

[nianhuo5678]

今天连接测试显示如下，请问下一步如何排查问题：

找不到任何连接日志！

1. 可能是插件未在运行

2. 可能是缓存导致浏览直接使用 IP 地址进行访问

3. 可能是 DNS 未劫持成功，导致 Clash 无法正确反推出域名连接

4. 可能是所填地址无法进行解析和连接

OpenClash 调试日志

生成时间: 2022-11-12 14:40:20
插件版本: v0.45.70-beta
隐私提示: 上传此日志前请注意检查、屏蔽公网IP、节点、密码等相关敏感信息

#===================== 系统信息 =====================#

主机型号: Raspberry Pi 3 Model B Rev 1.2
固件版本: ImmortalWrt 18.06-k5.4-SNAPSHOT r12328-cfa5234f62
LuCI版本: git-22.312.35760-7afcfb2-1
内核版本: 5.4.203
处理器架构: 

#此项有值时,如不使用IPv6,建议到网络-接口-lan的设置中禁用IPV6的DHCP
IPV6-DHCP: 

#此项结果应仅有配置文件的DNS监听地址
Dnsmasq转发设置: 127.0.0.1#7874

#===================== 依赖检查 =====================#

dnsmasq-full: 已安装
coreutils: 已安装
coreutils-nohup: 已安装
bash: 已安装
curl: 已安装
ca-certificates: 已安装
ipset: 已安装
ip-full: 已安装
libcap: 已安装
libcap-bin: 已安装
ruby: 已安装
ruby-yaml: 已安装
ruby-psych: 已安装
ruby-pstore: 已安装
kmod-tun(TUN模式): 已安装
luci-compat(Luci >= 19.07): 已安装
kmod-inet-diag(PROCESS-NAME): 已安装
unzip: 已安装
iptables-mod-tproxy: 已安装
kmod-ipt-tproxy: 已安装
iptables-mod-extra: 已安装
kmod-ipt-extra: 已安装
kmod-ipt-nat: 已安装

#===================== 内核检查 =====================#

运行状态: 运行中
进程pid: 29476
运行权限: 29476: cap_dac_override,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_ptrace,cap_sys_resource=eip
运行用户: nobody
已选择的架构: linux-arm64

#下方无法显示内核版本号时请确认您的内核版本是否正确或者有无权限
Tun内核版本: 2022.08.26-16-gb4d832d
Tun内核文件: 存在
Tun内核运行权限: 正常

Dev内核版本: v1.11.12-1-gde264c4
Dev内核文件: 存在
Dev内核运行权限: 正常

Meta内核版本: alpha-g4c5853e
Meta内核文件: 存在
Meta内核运行权限: 正常

#===================== 插件设置 =====================#

当前配置文件: /etc/openclash/config/Windows_Clash.yaml
启动配置文件: /etc/openclash/Windows_Clash.yaml
运行模式: redir-host
默认代理模式: rule
UDP流量转发(tproxy): 启用
DNS劫持: 启用
自定义DNS: 停用
IPV6代理: 停用
IPV6-DNS解析: 停用
禁用Dnsmasq缓存: 停用
自定义规则: 停用
仅允许内网: 启用
仅代理命中规则流量: 停用
仅允许常用端口流量: 停用
绕过中国大陆IP: 停用
DNS远程解析: 启用
路由本机代理: 启用

#启动异常时建议关闭此项后重试
混合节点: 停用
保留配置: 停用

#启动异常时建议关闭此项后重试
第三方规则: 停用

#===================== 配置文件 =====================#

port: 7890
socks-port: 7891
allow-lan: true
mode: rule
log-level: silent
external-controller: 0.0.0.0:9090
dns:
  enable: true
  ipv6: false
  nameserver:
  - 1.2.4.8
  - 114.114.114.114
  - 223.5.5.5
  - tls://dns.rubyfish.cn:853
  - 192.168.50.1
  - 119.29.29.29
  - https://doh.pub/dns-query
  - https://dns.alidns.com/dns-query
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  listen: 0.0.0.0:7874
  default-nameserver:
  - 1.2.4.8
  - 114.114.114.114
  - 223.5.5.5
  - 192.168.50.1
  - 119.29.29.29
  fake-ip-filter:
  - "+.*"
proxy-groups:
- name: Proxy
  type: select
  proxies:

rules:
- DST-PORT,7895,REJECT



- GEOIP,CN,DIRECT
- MATCH,Proxy
redir-port: 7892
tproxy-port: 7895
mixed-port: 7893
bind-address: "*"
external-ui: "/usr/share/openclash/ui"
ipv6: false
profile:
  store-selected: true
  store-fake-ip: true
authentication:
- Clash:xxxx

#===================== IPTABLES 防火墙设置 =====================#

#IPv4 NAT chain

# Generated by iptables-save v1.8.7 on Sat Nov 12 14:40:24 2022
*nat
:PREROUTING ACCEPT [831:100639]
:INPUT ACCEPT [651:42115]
:OUTPUT ACCEPT [94:5783]
:POSTROUTING ACCEPT [100:6143]
:openclash - [0:0]
:openclash_output - [0:0]
:postrouting_lan_rule - [0:0]
:postrouting_rule - [0:0]
:postrouting_vpn_rule - [0:0]
:postrouting_wan_rule - [0:0]
:prerouting_lan_rule - [0:0]
:prerouting_rule - [0:0]
:prerouting_vpn_rule - [0:0]
:prerouting_wan_rule - [0:0]
:zone_lan_postrouting - [0:0]
:zone_lan_prerouting - [0:0]
:zone_vpn_postrouting - [0:0]
:zone_vpn_prerouting - [0:0]
:zone_wan_postrouting - [0:0]
:zone_wan_prerouting - [0:0]
-A PREROUTING -d 8.8.4.4/32 -p tcp -m comment --comment "OpenClash Google DNS Hijack" -m tcp --dport 53 -j REDIRECT --to-ports 7892
-A PREROUTING -d 8.8.8.8/32 -p tcp -m comment --comment "OpenClash Google DNS Hijack" -m tcp --dport 53 -j REDIRECT --to-ports 7892
-A PREROUTING -p tcp -m tcp --dport 53 -m comment --comment "OpenClash DNS Hijack" -j REDIRECT --to-ports 53
-A PREROUTING -p udp -m udp --dport 53 -m comment --comment "OpenClash DNS Hijack" -j REDIRECT --to-ports 53
-A PREROUTING -m comment --comment "!fw3: Custom prerouting rule chain" -j prerouting_rule
-A PREROUTING -i br-lan -m comment --comment "!fw3" -j zone_lan_prerouting
-A PREROUTING -i tun0 -m comment --comment "!fw3" -j zone_vpn_prerouting
-A PREROUTING -p udp -m comment --comment DNSMASQ -m udp --dport 53 -j REDIRECT --to-ports 53
-A PREROUTING -p tcp -j openclash
-A OUTPUT -j openclash_output
-A POSTROUTING -m comment --comment "!fw3: Custom postrouting rule chain" -j postrouting_rule
-A POSTROUTING -o br-lan -m comment --comment "!fw3" -j zone_lan_postrouting
-A POSTROUTING -o tun0 -m comment --comment "!fw3" -j zone_vpn_postrouting
-A openclash -p tcp -m tcp --sport 1194 -j RETURN
-A openclash -m set --match-set localnetwork dst -j RETURN
-A openclash -p tcp -j REDIRECT --to-ports 7892
-A openclash_output -p tcp -m tcp --sport 1194 -j RETURN
-A openclash_output -m set --match-set localnetwork dst -j RETURN
-A openclash_output -p tcp -m owner ! --uid-owner 65534 -j REDIRECT --to-ports 7892
-A zone_lan_postrouting -m comment --comment "!fw3: Custom lan postrouting rule chain" -j postrouting_lan_rule
-A zone_lan_prerouting -m comment --comment "!fw3: Custom lan prerouting rule chain" -j prerouting_lan_rule
-A zone_vpn_postrouting -m comment --comment "!fw3: Custom vpn postrouting rule chain" -j postrouting_vpn_rule
-A zone_vpn_postrouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_vpn_prerouting -m comment --comment "!fw3: Custom vpn prerouting rule chain" -j prerouting_vpn_rule
-A zone_vpn_prerouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_wan_postrouting -m comment --comment "!fw3: Custom wan postrouting rule chain" -j postrouting_wan_rule
-A zone_wan_postrouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_wan_prerouting -m comment --comment "!fw3: Custom wan prerouting rule chain" -j prerouting_wan_rule
-A zone_wan_prerouting -m comment --comment "!fw3" -j FULLCONENAT
COMMIT
# Completed on Sat Nov 12 14:40:24 2022

#IPv4 Mangle chain

# Generated by iptables-save v1.8.7 on Sat Nov 12 14:40:24 2022
*mangle
:PREROUTING ACCEPT [7013:903305]
:INPUT ACCEPT [6799:832195]
:FORWARD ACCEPT [2:656]
:OUTPUT ACCEPT [6441:3029578]
:POSTROUTING ACCEPT [6448:3030782]
:RRDIPT_FORWARD - [0:0]
:RRDIPT_INPUT - [0:0]
:RRDIPT_OUTPUT - [0:0]
:openclash - [0:0]
-A PREROUTING -p udp -j openclash
-A INPUT -j RRDIPT_INPUT
-A FORWARD -j RRDIPT_FORWARD
-A OUTPUT -j RRDIPT_OUTPUT
-A RRDIPT_FORWARD -s 192.168.50.152/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.50.152/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.50.194/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.50.194/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.50.1/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.50.1/32 -j RETURN
-A RRDIPT_INPUT -i eth0 -j RETURN
-A RRDIPT_INPUT -i br-lan -j RETURN
-A RRDIPT_OUTPUT -o eth0 -j RETURN
-A RRDIPT_OUTPUT -o br-lan -j RETURN
-A openclash -p udp -m udp --sport 1194 -j RETURN
-A openclash -p udp -m udp --sport 500 -j RETURN
-A openclash -p udp -m udp --sport 68 -j RETURN
-A openclash -m set --match-set localnetwork dst -j RETURN
-A openclash -p udp -m udp --dport 53 -j RETURN
-A openclash -p udp -j TPROXY --on-port 7895 --on-ip 0.0.0.0 --tproxy-mark 0x162/0xffffffff
COMMIT
# Completed on Sat Nov 12 14:40:24 2022

#IPv4 Filter chain

# Generated by iptables-save v1.8.7 on Sat Nov 12 14:40:24 2022
*filter
:INPUT ACCEPT [2:80]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:forwarding_lan_rule - [0:0]
:forwarding_rule - [0:0]
:forwarding_vpn_rule - [0:0]
:forwarding_wan_rule - [0:0]
:input_lan_rule - [0:0]
:input_rule - [0:0]
:input_vpn_rule - [0:0]
:input_wan_rule - [0:0]
:output_lan_rule - [0:0]
:output_rule - [0:0]
:output_vpn_rule - [0:0]
:output_wan_rule - [0:0]
:reject - [0:0]
:syn_flood - [0:0]
:zone_lan_dest_ACCEPT - [0:0]
:zone_lan_forward - [0:0]
:zone_lan_input - [0:0]
:zone_lan_output - [0:0]
:zone_lan_src_ACCEPT - [0:0]
:zone_vpn_dest_ACCEPT - [0:0]
:zone_vpn_forward - [0:0]
:zone_vpn_input - [0:0]
:zone_vpn_output - [0:0]
:zone_vpn_src_ACCEPT - [0:0]
:zone_wan_dest_ACCEPT - [0:0]
:zone_wan_dest_REJECT - [0:0]
:zone_wan_forward - [0:0]
:zone_wan_input - [0:0]
:zone_wan_output - [0:0]
:zone_wan_src_REJECT - [0:0]
-A INPUT -p udp -m udp --dport 443 -m comment --comment "OpenClash QUIC REJECT" -m set ! --match-set china_ip_route dst -j REJECT --reject-with icmp-port-unreachable
-A INPUT -i lo -m comment --comment "!fw3" -j ACCEPT
-A INPUT -m comment --comment "!fw3: Custom input rule chain" -j input_rule
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -m comment --comment "!fw3" -j ACCEPT
-A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m comment --comment "!fw3" -j syn_flood
-A INPUT -i br-lan -m comment --comment "!fw3" -j zone_lan_input
-A INPUT -i tun0 -m comment --comment "!fw3" -j zone_vpn_input
-A FORWARD -m comment --comment "!fw3: Custom forwarding rule chain" -j forwarding_rule
-A FORWARD -m comment --comment "!fw3: Traffic offloading" -m conntrack --ctstate RELATED,ESTABLISHED -j FLOWOFFLOAD --hw
-A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -m comment --comment "!fw3" -j ACCEPT
-A FORWARD -i br-lan -m comment --comment "!fw3" -j zone_lan_forward
-A FORWARD -i tun0 -m comment --comment "!fw3" -j zone_vpn_forward
-A FORWARD -m comment --comment "!fw3" -j reject
-A OUTPUT -o lo -m comment --comment "!fw3" -j ACCEPT
-A OUTPUT -m comment --comment "!fw3: Custom output rule chain" -j output_rule
-A OUTPUT -m conntrack --ctstate RELATED,ESTABLISHED -m comment --comment "!fw3" -j ACCEPT
-A OUTPUT -o br-lan -m comment --comment "!fw3" -j zone_lan_output
-A OUTPUT -o tun0 -m comment --comment "!fw3" -j zone_vpn_output
-A reject -p tcp -m comment --comment "!fw3" -j REJECT --reject-with tcp-reset
-A reject -m comment --comment "!fw3" -j REJECT --reject-with icmp-port-unreachable
-A syn_flood -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m limit --limit 25/sec --limit-burst 50 -m comment --comment "!fw3" -j RETURN
-A syn_flood -m comment --comment "!fw3" -j DROP
-A zone_lan_dest_ACCEPT -o br-lan -m comment --comment "!fw3" -j ACCEPT
-A zone_lan_forward -m comment --comment "!fw3: Custom lan forwarding rule chain" -j forwarding_lan_rule
-A zone_lan_forward -m comment --comment "!fw3: Zone lan to wan forwarding policy" -j zone_wan_dest_ACCEPT
-A zone_lan_forward -m comment --comment "!fw3: Zone lan to vpn forwarding policy" -j zone_vpn_dest_ACCEPT
-A zone_lan_forward -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port forwards" -j ACCEPT
-A zone_lan_forward -m comment --comment "!fw3" -j zone_lan_dest_ACCEPT
-A zone_lan_input -m comment --comment "!fw3: Custom lan input rule chain" -j input_lan_rule
-A zone_lan_input -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port redirections" -j ACCEPT
-A zone_lan_input -m comment --comment "!fw3" -j zone_lan_src_ACCEPT
-A zone_lan_output -m comment --comment "!fw3: Custom lan output rule chain" -j output_lan_rule
-A zone_lan_output -m comment --comment "!fw3" -j zone_lan_dest_ACCEPT
-A zone_lan_src_ACCEPT -i br-lan -m conntrack --ctstate NEW,UNTRACKED -m comment --comment "!fw3" -j ACCEPT
-A zone_vpn_dest_ACCEPT -o tun0 -m conntrack --ctstate INVALID -m comment --comment "!fw3: Prevent NAT leakage" -j DROP
-A zone_vpn_dest_ACCEPT -o tun0 -m comment --comment "!fw3" -j ACCEPT
-A zone_vpn_forward -m comment --comment "!fw3: Custom vpn forwarding rule chain" -j forwarding_vpn_rule
-A zone_vpn_forward -m comment --comment "!fw3: Zone vpn to wan forwarding policy" -j zone_wan_dest_ACCEPT
-A zone_vpn_forward -m comment --comment "!fw3: Zone vpn to lan forwarding policy" -j zone_lan_dest_ACCEPT
-A zone_vpn_forward -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port forwards" -j ACCEPT
-A zone_vpn_forward -m comment --comment "!fw3" -j zone_vpn_dest_ACCEPT
-A zone_vpn_input -m comment --comment "!fw3: Custom vpn input rule chain" -j input_vpn_rule
-A zone_vpn_input -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port redirections" -j ACCEPT
-A zone_vpn_input -m comment --comment "!fw3" -j zone_vpn_src_ACCEPT
-A zone_vpn_output -m comment --comment "!fw3: Custom vpn output rule chain" -j output_vpn_rule
-A zone_vpn_output -m comment --comment "!fw3" -j zone_vpn_dest_ACCEPT
-A zone_vpn_src_ACCEPT -i tun0 -m conntrack --ctstate NEW,UNTRACKED -m comment --comment "!fw3" -j ACCEPT
-A zone_wan_forward -m comment --comment "!fw3: Custom wan forwarding rule chain" -j forwarding_wan_rule
-A zone_wan_forward -p esp -m comment --comment "!fw3: Allow-IPSec-ESP" -j zone_lan_dest_ACCEPT
-A zone_wan_forward -p udp -m udp --dport 500 -m comment --comment "!fw3: Allow-ISAKMP" -j zone_lan_dest_ACCEPT
-A zone_wan_forward -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port forwards" -j ACCEPT
-A zone_wan_forward -m comment --comment "!fw3" -j zone_wan_dest_REJECT
-A zone_wan_input -m comment --comment "!fw3: Custom wan input rule chain" -j input_wan_rule
-A zone_wan_input -p udp -m udp --dport 68 -m comment --comment "!fw3: Allow-DHCP-Renew" -j ACCEPT
-A zone_wan_input -p icmp -m icmp --icmp-type 8 -m comment --comment "!fw3: Allow-Ping" -j ACCEPT
-A zone_wan_input -p igmp -m comment --comment "!fw3: Allow-IGMP" -j ACCEPT
-A zone_wan_input -p tcp -m tcp --dport 1194 -m comment --comment "!fw3: openvpn" -j ACCEPT
-A zone_wan_input -p udp -m udp --dport 1194 -m comment --comment "!fw3: openvpn" -j ACCEPT
-A zone_wan_input -m conntrack --ctstate DNAT -m comment --comment "!fw3: Accept port redirections" -j ACCEPT
-A zone_wan_input -m comment --comment "!fw3" -j zone_wan_src_REJECT
-A zone_wan_output -m comment --comment "!fw3: Custom wan output rule chain" -j output_wan_rule
-A zone_wan_output -m comment --comment "!fw3" -j zone_wan_dest_ACCEPT
COMMIT
# Completed on Sat Nov 12 14:40:24 2022

#IPv6 NAT chain


#IPv6 Mangle chain


#IPv6 Filter chain


#===================== IPSET状态 =====================#

Name: china_ip_route
Name: china_ip_route_pass
Name: localnetwork

#===================== 路由表状态 =====================#

#route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.50.1    0.0.0.0         UG    0      0        0 br-lan
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 br-lan
#ip route list
default via 192.168.50.1 dev br-lan proto static 
192.168.50.0/24 dev br-lan proto kernel scope link src 192.168.50.250 
#ip rule show
0:	from all lookup local
32765:	from all fwmark 0x162 lookup 354
32766:	from all lookup main
32767:	from all lookup default

#===================== 端口占用状态 =====================#

tcp        0      0 :::7890                 :::*                    LISTEN      29476/clash
tcp        0      0 :::7891                 :::*                    LISTEN      29476/clash
tcp        0      0 :::7892                 :::*                    LISTEN      29476/clash
tcp        0      0 :::7893                 :::*                    LISTEN      29476/clash
tcp        0      0 :::7895                 :::*                    LISTEN      29476/clash
tcp        0      0 :::9090                 :::*                    LISTEN      29476/clash
udp        0      0 :::7874                 :::*                                29476/clash
udp        0      0 :::7891                 :::*                                29476/clash
udp        0      0 :::7892                 :::*                                29476/clash
udp        0      0 :::7893                 :::*                                29476/clash
udp        0      0 :::7895                 :::*                                29476/clash

#===================== 测试本机DNS查询 =====================#

Server:		127.0.0.1
Address:	127.0.0.1:53

Non-authoritative answer:
www.baidu.com	canonical name = www.a.shifen.com
Name:	www.a.shifen.com
Address: 14.215.177.38
Name:	www.a.shifen.com
Address: 14.215.177.39



#===================== resolv.conf.auto =====================#

# Interface lan
nameserver 192.168.50.1

#===================== resolv.conf.d =====================#

# Interface lan
nameserver 192.168.50.1

#===================== 测试本机网络连接 =====================#

HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: private, no-cache, no-store, proxy-revalidate, no-transform
Connection: keep-alive
Content-Length: 277
Content-Type: text/html
Date: Sat, 12 Nov 2022 06:40:25 GMT
Etag: "575e1f72-115"
Last-Modified: Mon, 13 Jun 2016 02:50:26 GMT
Pragma: no-cache
Server: bfe/1.0.8.18


#===================== 测试本机网络下载 =====================#


#===================== 最近运行日志 =====================#

2022-11-12 14:35:10 Step 2: Delete OpenClash Firewall Rules...
2022-11-12 14:35:12 Step 3: Close The OpenClash Daemons...
2022-11-12 14:35:12 Step 4: Close The Clash Core Process...
2022-11-12 14:35:12 Step 5: Restart Dnsmasq...
2022-11-12 14:35:12 Step 6: Delete OpenClash Residue File...
2022-11-12 14:35:13 OpenClash Start Running...
2022-11-12 14:35:13 Step 1: Get The Configuration...
2022-11-12 14:35:13 Step 2: Check The Components...
2022-11-12 14:35:14 Tip: Because of the file【 /etc/config/openclash 】modificated, Pause quick start...
2022-11-12 14:35:14 Step 3: Modify The Config File...
2022-11-12 14:35:15 Tip: You have seted the authentication of SOCKS5/HTTP(S) proxy with【Clash:Y9HrshP0】
2022-11-12 14:35:16 Step 4: Start Running The Clash Core...
2022-11-12 14:35:16 Tip: No Special Configuration Detected, Use Dev Core to Start...
2022-11-12 14:35:17 Step 5: Check The Core Status...
time="2022-11-12T06:35:18Z" level=info msg="Start initial compatible provider Proxy"
time="2022-11-12T06:35:18Z" level=info msg="Authentication of local server updated"
2022-11-12 14:35:20 Step 6: Wait For The File Downloading...
2022-11-12 14:35:21 Step 7: Set Firewall Rules...
2022-11-12 14:35:22 Step 8: Restart Dnsmasq...
2022-11-12 14:35:22 Step 9: Add Cron Rules, Start Daemons...
2022-11-12 14:35:22 OpenClash Start Successful!
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【curl: (60) SSL certificate problem: self signed certificate】
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【More details here: https://curl.se/docs/sslcerts.html】
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【】
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【curl failed to verify the legitimacy of the server and therefore could not】
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【establish a secure connection to it. To learn more about this situation and】
2022-11-12 14:36:00【/tmp/Special.yaml】Download Failed:【how to fix it, please visit the web page mentioned above.】
2022-11-12 14:36:00 Rule File【Special.yaml】Download Error!
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【curl: (60) SSL certificate problem: self signed certificate】
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【More details here: https://curl.se/docs/sslcerts.html】
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【】
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【curl failed to verify the legitimacy of the server and therefore could not】
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【establish a secure connection to it. To learn more about this situation and】
2022-11-12 14:36:03【/tmp/UnBan.yaml】Download Failed:【how to fix it, please visit the web page mentioned above.】
2022-11-12 14:36:03 Rule File【UnBan.yaml】Download Error!
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【curl: (60) SSL certificate problem: self signed certificate】
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【More details here: https://curl.se/docs/sslcerts.html】
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【】
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【curl failed to verify the legitimacy of the server and therefore could not】
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【establish a secure connection to it. To learn more about this situation and】
2022-11-12 14:36:04【/tmp/Hijacking.yaml】Download Failed:【how to fix it, please visit the web page mentioned above.】
2022-11-12 14:36:04 Rule File【Hijacking.yaml】Download Error!
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【curl: (60) SSL certificate problem: self signed certificate】
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【More details here: https://curl.se/docs/sslcerts.html】
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【】
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【curl failed to verify the legitimacy of the server and therefore could not】
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【establish a secure connection to it. To learn more about this situation and】
2022-11-12 14:36:12【/tmp/Proxy.yaml】Download Failed:【how to fix it, please visit the web page mentioned above.】
2022-11-12 14:36:12 Rule File【Proxy.yaml】Download Error!
2022-11-12 14:36:23 Watchdog: Setting Firewall For Enabling Redirect...

#===================== 活动连接信息 =====================#