vernesong / OpenClash

A Clash Client For OpenWrt
MIT License
16.55k stars 3.06k forks source link

[Bug] 节点正常,突然就无法访问外网。使用的默认配置。未进行修改 #3516

Closed xuanshao-zty closed 8 months ago

xuanshao-zty commented 11 months ago

Verify Steps

OpenClash Version

v0.45.141-beta

Bug on Environment

Official OpenWrt

Bug on Platform

Linux-arm64

To Reproduce

之前使用正常,然后使用过程中突然就无法正常访问。之前尝试过重装openwrt的系统,也无法解决。passwall可以正常使用,就好像访问的外网为走进openclash一样。

Describe the Bug

看了下debug一直在报dns错误。但是我未在yaml里设置dns。openclash也是直接使用的默认配置。就使用了Redir-host混合模式。其他都没改动。

OpenClash Log

OpenClash 调试日志

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


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

主机型号: FriendlyElec NanoPi R5S
固件版本: OpenWrt 23.05.0-rc2 r23228-cd17d8df2a
LuCI版本: git-23.051.66410-a505bb1
内核版本: 6.1.42
处理器架构: aarch64_generic

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

DNS劫持: Dnsmasq 转发
#DNS劫持为Dnsmasq时,此项结果应仅有配置文件的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: 已安装
kmod-nft-tproxy: 已安装

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

运行状态: 运行中
运行内核:TUN
进程pid: 25870
运行权限: 25870: cap_dac_override,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_ptrace,cap_sys_resource=eip
运行用户: 
已选择的架构: 未选择架构

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

Dev内核版本: v1.17.0-20-ga19a9fe
Dev内核文件: 存在
Dev内核运行权限: 正常

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

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

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

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

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

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

port: 7890
socks-port: 7891
redir-port: 7892
allow-lan: true
mode: rule
log-level: info
external-controller: 0.0.0.0:9090
tproxy-port: 7895
mixed-port: 7893
bind-address: "*"
external-ui: "/usr/share/openclash/ui"
ipv6: false
dns:
  enable: true
  ipv6: false
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  listen: 0.0.0.0:7874
  nameserver:
  - 114.114.114.114
  - 119.29.29.29
  - 223.5.5.5
  - https://doh.pub/dns-query
  - https://223.5.5.5/dns-query
  fallback:
  - https://dns.cloudflare.com/dns-query
  - https://public.dns.iij.jp/dns-query
  - https://jp.tiar.app/dns-query
  - https://jp.tiarap.org/dns-query
  fake-ip-filter:
  - "+.*"
experimental:
  sniff-tls-sni: true
tun:
  enable: true
  stack: system
  auto-route: false
  auto-detect-interface: false
  dns-hijack:
  - tcp://any:53
profile:
  store-selected: true

#===================== 自定义覆写设置 =====================#

#!/bin/sh
. /usr/share/openclash/ruby.sh
. /usr/share/openclash/log.sh
. /lib/functions.sh

# This script is called by /etc/init.d/openclash
# Add your custom overwrite scripts here, they will be take effict after the OpenClash own srcipts

LOG_OUT "Tip: Start Running Custom Overwrite Scripts..."
LOGTIME=$(echo $(date "+%Y-%m-%d %H:%M:%S"))
LOG_FILE="/tmp/openclash.log"
CONFIG_FILE="$1" #config path

#Simple Demo:
    #General Demo
    #1--config path
    #2--key name
    #3--value
    #ruby_edit "$CONFIG_FILE" "['redir-port']" "7892"
    #ruby_edit "$CONFIG_FILE" "['secret']" "123456"
    #ruby_edit "$CONFIG_FILE" "['dns']['enable']" "true"

    #Hash Demo
    #1--config path
    #2--key name
    #3--hash type value
    #ruby_edit "$CONFIG_FILE" "['experimental']" "{'sniff-tls-sni'=>true}"
    #ruby_edit "$CONFIG_FILE" "['sniffer']" "{'sniffing'=>['tls','http']}"

    #Array Demo:
    #1--config path
    #2--key name
    #3--position(start from 0, end with -1)
    #4--value
    #ruby_arr_insert "$CONFIG_FILE" "['dns']['nameserver']" "0" "114.114.114.114"

    #Array Add From Yaml File Demo:
    #1--config path
    #2--key name
    #3--position(start from 0, end with -1)
    #4--value file path
    #5--value key name in #4 file
    #ruby_arr_add_file "$CONFIG_FILE" "['dns']['fallback-filter']['ipcidr']" "0" "/etc/openclash/custom/openclash_custom_fallback_filter.yaml" "['fallback-filter']['ipcidr']"

#Ruby Script Demo:
    #ruby -ryaml -rYAML -I "/usr/share/openclash" -E UTF-8 -e "
    #   begin
    #      Value = YAML.load_file('$CONFIG_FILE');
    #   rescue Exception => e
    #      puts '${LOGTIME} Error: Load File Failed,【' + e.message + '】';
    #   end;

        #General
    #   begin
    #   Thread.new{
    #      Value['redir-port']=7892;
    #      Value['tproxy-port']=7895;
    #      Value['port']=7890;
    #      Value['socks-port']=7891;
    #      Value['mixed-port']=7893;
    #   }.join;

    #   rescue Exception => e
    #      puts '${LOGTIME} Error: Set General Failed,【' + e.message + '】';
    #   ensure
    #      File.open('$CONFIG_FILE','w') {|f| YAML.dump(Value, f)};
    #   end" 2>/dev/null >> $LOG_FILE

exit 0
#===================== 自定义防火墙设置 =====================#

#!/bin/sh
. /usr/share/openclash/log.sh
. /lib/functions.sh

# This script is called by /etc/init.d/openclash
# Add your custom firewall rules here, they will be added after the end of the OpenClash iptables rules

LOG_OUT "Tip: Start Add Custom Firewall Rules..."

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

#IPv4 NAT chain

# Generated by iptables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:DOCKER - [0:0]
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE
-A DOCKER -i docker0 -j RETURN
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#IPv4 Mangle chain

# Generated by iptables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#IPv4 Filter chain

# Generated by iptables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#IPv6 NAT chain

# Generated by ip6tables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#IPv6 Mangle chain

# Generated by ip6tables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#IPv6 Filter chain

# Generated by ip6tables-save v1.8.8 (nf_tables) on Tue Sep 19 09:44:18 2023
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT
# Completed on Tue Sep 19 09:44:18 2023

#===================== NFTABLES 防火墙设置 =====================#

table inet fw4 {
    chain input {
        type filter hook input priority filter; policy accept;
        iifname "eth0" ip saddr != @localnetwork counter packets 6856 bytes 3471496 jump openclash_wan_input
        iifname "lo" accept comment "!fw4: Accept traffic from loopback"
        ct state established,related accept comment "!fw4: Allow inbound established and related flows"
        tcp flags syn / fin,syn,rst,ack jump syn_flood comment "!fw4: Rate limit TCP syn packets"
        iifname "br-lan" jump input_lan comment "!fw4: Handle lan IPv4/IPv6 input traffic"
        iifname "eth0" jump input_wan comment "!fw4: Handle wan IPv4/IPv6 input traffic"
        iifname "docker0" jump input_docker comment "!fw4: Handle docker IPv4/IPv6 input traffic"
    }
}
table inet fw4 {
    chain forward {
        type filter hook forward priority filter; policy drop;
        oifname "utun" udp dport 443 ip daddr != @china_ip_route counter packets 0 bytes 0 reject with icmp port-unreachable comment "OpenClash QUIC REJECT"
        meta l4proto { tcp, udp } oifname "utun" counter packets 284 bytes 37228 accept comment "OpenClash TUN Forward"
        meta l4proto { tcp, udp } flow add @ft
        ct state established,related accept comment "!fw4: Allow forwarded established and related flows"
        iifname "br-lan" jump forward_lan comment "!fw4: Handle lan IPv4/IPv6 forward traffic"
        iifname "eth0" jump forward_wan comment "!fw4: Handle wan IPv4/IPv6 forward traffic"
        iifname "docker0" jump forward_docker comment "!fw4: Handle docker IPv4/IPv6 forward traffic"
        jump upnp_forward comment "Hook into miniupnpd forwarding chain"
        jump handle_reject
    }
}
table inet fw4 {
    chain dstnat {
        type nat hook prerouting priority dstnat; policy accept;
        meta nfproto ipv4 tcp dport 53 counter packets 0 bytes 0 accept comment "OpenClash TCP DNS Hijack"
        udp dport 53 counter packets 328 bytes 22082 redirect to :53 comment "OpenClash DNS Hijack"
        tcp dport 53 counter packets 0 bytes 0 redirect to :53 comment "OpenClash DNS Hijack"
        iifname "eth0" jump dstnat_wan comment "!fw4: Handle wan IPv4/IPv6 dstnat traffic"
        jump upnp_prerouting comment "Hook into miniupnpd prerouting chain"
        ip protocol tcp counter packets 214 bytes 11222 jump openclash
    }
}
table inet fw4 {
    chain srcnat {
        type nat hook postrouting priority srcnat; policy accept;
        oifname "eth0" jump srcnat_wan comment "!fw4: Handle wan IPv4/IPv6 srcnat traffic"
        jump upnp_postrouting comment "Hook into miniupnpd postrouting chain"
    }
}
table inet fw4 {
    chain nat_output {
        type nat hook output priority filter - 1; policy accept;
        ip protocol tcp counter packets 933 bytes 55980 jump openclash_output
    }
}
table inet fw4 {
    chain mangle_prerouting {
        type filter hook prerouting priority mangle; policy accept;
        ip protocol udp counter packets 2674 bytes 273139 jump openclash_mangle
        meta nfproto ipv4 tcp dport 53 counter packets 0 bytes 0 jump openclash_dns_hijack
    }
}
table inet fw4 {
    chain mangle_output {
        type route hook output priority mangle; policy accept;
        meta nfproto ipv4 meta l4proto { tcp, udp } counter packets 13560 bytes 6183630 jump openclash_mangle_output
    }
}
table inet fw4 {
    chain openclash {
        meta nfproto ipv4 tcp sport 1688 counter packets 0 bytes 0 return
        ip daddr @localnetwork counter packets 1 bytes 52 return
        ip protocol tcp counter packets 214 bytes 11222 redirect to :7892
    }
}
table inet fw4 {
    chain openclash_mangle {
        meta nfproto ipv4 udp sport 500 counter packets 0 bytes 0 return
        meta nfproto ipv4 udp sport 68 counter packets 0 bytes 0 return
        meta l4proto { tcp, udp } iifname "utun" counter packets 0 bytes 0 return
        ip daddr @localnetwork counter packets 2389 bytes 235843 return
        ip protocol udp counter packets 285 bytes 37296 jump openclash_upnp
        meta l4proto { tcp, udp } th dport 0-65535 meta mark set 0x00000162 counter packets 285 bytes 37296
    }
}
table inet fw4 {
    chain openclash_mangle_output {
        meta nfproto ipv4 udp sport 500 counter packets 0 bytes 0 return
        meta nfproto ipv4 udp sport 68 counter packets 0 bytes 0 return
        ip daddr @localnetwork counter packets 4514 bytes 5394699 return
    }
}
table inet fw4 {
    chain openclash_output {
        meta nfproto ipv4 tcp sport 1688 counter packets 0 bytes 0 return
        ip daddr @localnetwork counter packets 32 bytes 1920 return
        ip protocol tcp meta skuid != 65534 counter packets 0 bytes 0 redirect to :7892
    }
}
table inet fw4 {
    chain openclash_wan_input {
        udp dport { 7874, 7890, 7891, 7892, 7893, 7895, 9090 } counter packets 0 bytes 0 reject
        tcp dport { 7874, 7890, 7891, 7892, 7893, 7895, 9090 } counter packets 0 bytes 0 reject
    }
}
table inet fw4 {
    chain openclash_dns_hijack {
    }
}

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

Name: passwall_shuntlist
Type: hash:net
Revision: 7
Header: family inet hashsize 1024 maxelem 1048576 bucketsize 12 initval 0x33649dd5
Size in memory: 3480
References: 0
Number of entries: 64

Name: passwall_gfwlist
Type: hash:net
Revision: 7
Header: family inet hashsize 1024 maxelem 1048576 bucketsize 12 initval 0xb1057b9f
Size in memory: 12312
References: 0
Number of entries: 277

Name: passwall_chnroute
Type: hash:net
Revision: 7
Header: family inet hashsize 2048 maxelem 1048576 bucketsize 12 initval 0xb92add65
Size in memory: 232080
References: 0
Number of entries: 8609

Name: passwall_blacklist
Type: hash:net
Revision: 7
Header: family inet hashsize 1024 maxelem 1048576 bucketsize 12 initval 0xfd43c592
Size in memory: 5832
References: 0
Number of entries: 121

Name: passwall_shuntlist6
Type: hash:net
Revision: 7
Header: family inet6 hashsize 1024 maxelem 1048576 bucketsize 12 initval 0x27ffc201
Size in memory: 1888
References: 0
Number of entries: 9

Name: passwall_gfwlist6
Type: hash:net
Revision: 7
Header: family inet6 hashsize 1024 maxelem 1048576 bucketsize 12 initval 0x3e9417d4
Size in memory: 2032
References: 0
Number of entries: 11

Name: passwall_chnroute6
Type: hash:net
Revision: 7
Header: family inet6 hashsize 1024 maxelem 1048576 bucketsize 12 initval 0x6dec30a6
Size in memory: 89800
References: 0
Number of entries: 1974

Name: passwall_blacklist6
Type: hash:net
Revision: 7
Header: family inet6 hashsize 1024 maxelem 1048576 bucketsize 12 initval 0xfe3a6d80
Size in memory: 1600
References: 0
Number of entries: 5

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

#IPv4

#route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 br-lan
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
198.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 utun

#ip route list
default via 192.168.1.1 dev eth0 proto static src 192.168.1.2 
10.0.0.0/24 dev br-lan proto kernel scope link src 10.0.0.1 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 
198.18.0.0/16 dev utun proto kernel scope link src 198.18.0.1 

#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

#IPv6

#route -A inet6
Kernel IPv6 routing table
Destination                                 Next Hop                                Flags Metric Ref    Use Iface
::/0                                        ::                                      !n    -1     1        0 lo      
::/0                                        ::                                      !n    -1     1        0 lo      
fe80::/64                                   ::                                      U     256    1        0 br-lan  
fe80::/64                                   ::                                      U     256    1        0 eth0    
fe80::/64                                   ::                                      U     256    1        0 utun    
::/0                                        ::                                      !n    -1     1        0 lo      
::1/128                                     ::                                      Un    0      6        0 lo      
fe80::/128                                  ::                                      Un    0      6        0 br-lan  
fe80::/128                                  ::                                      Un    0      3        0 eth0    
fe80::/128                                  ::                                      Un    0      3        0 utun    
fe80::3c5f:e9ff:fe01:3aa4/128               ::                                      Un    0      2        0 eth0    
fe80::3c5f:e9ff:fe01:3aa5/128               ::                                      Un    0      3        0 br-lan  
fe80::5764:5ba1:2012:3521/128               ::                                      Un    0      2        0 utun    
ff00::/8                                    ::                                      U     256    5        0 br-lan  
ff00::/8                                    ::                                      U     256    5        0 eth0    
ff00::/8                                    ::                                      U     256    4        0 utun    
::/0                                        ::                                      !n    -1     1        0 lo      

#ip -6 route list
fe80::/64 dev br-lan proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev utun proto kernel metric 256 pref medium

#ip -6 rule show
0:  from all lookup local
32766:  from all lookup main

#===================== Tun设备状态 =====================#

utun: tun pi multi_queue filter

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

tcp        0      0 198.18.0.1:7777         0.0.0.0:*               LISTEN      25870/clash
tcp        0      0 :::9090                 :::*                    LISTEN      25870/clash
tcp        0      0 :::7890                 :::*                    LISTEN      25870/clash
tcp        0      0 :::7891                 :::*                    LISTEN      25870/clash
tcp        0      0 :::7895                 :::*                    LISTEN      25870/clash
tcp        0      0 :::7892                 :::*                    LISTEN      25870/clash
tcp        0      0 :::7893                 :::*                    LISTEN      25870/clash
udp        0      0 :::48314                :::*                                25870/clash
udp        0      0 :::56752                :::*                                25870/clash
udp        0      0 :::7874                 :::*                                25870/clash
udp        0      0 :::54981                :::*                                25870/clash
udp        0      0 :::7891                 :::*                                25870/clash
udp        0      0 :::7892                 :::*                                25870/clash
udp        0      0 :::7893                 :::*                                25870/clash
udp        0      0 :::7895                 :::*                                25870/clash
udp        0      0 :::49179                :::*                                25870/clash
udp        0      0 :::36909                :::*                                25870/clash
udp        0      0 :::51411                :::*                                25870/clash
udp        0      0 :::49389                :::*                                25870/clash
udp        0      0 :::55605                :::*                                25870/clash
udp        0      0 :::33079                :::*                                25870/clash
udp        0      0 :::47454                :::*                                25870/clash
udp        0      0 :::57774                :::*                                25870/clash
udp        0      0 :::37823                :::*                                25870/clash

#===================== 测试本机DNS查询(www.baidu.com) =====================#

Server:     127.0.0.1
Address:    127.0.0.1:53

www.baidu.com   canonical name = www.a.shifen.com
Name:   www.a.shifen.com
Address: 153.3.238.102
Name:   www.a.shifen.com
Address: 153.3.238.110

#===================== 测试内核DNS查询(www.instagram.com) =====================#

Dnsmasq 当前默认 resolv 文件:/tmp/resolv.conf.d/resolv.conf.auto

#===================== /tmp/resolv.conf.d/resolv.conf.auto =====================#

# Interface lan
nameserver 119.29.29.29
nameserver 8.8.8.8

#===================== 测试本机网络连接(www.baidu.com) =====================#

#===================== 测试本机网络下载(raw.githubusercontent.com) =====================#

#===================== 最近运行日志(自动切换为Debug模式) =====================#

09:44:32 INF [TCP] connected lAddr=10.0.0.220:57229 rAddr=connc.gj.qq.com:36688 mode=rule rule=DomainSuffix(qq.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:32 DBG [TCP] accept connection lAddr=10.0.0.220:4208 rAddr=img-xlppc-zhan.xunlei.com:80 inbound=Redir
09:44:32 DBG [Matcher] resolve success host=img-xlppc-zhan.xunlei.com ip=112.122.156.214
09:44:32 INF [TCP] connected lAddr=10.0.0.220:4208 rAddr=img-xlppc-zhan.xunlei.com:80 mode=rule rule=DomainSuffix(xunlei.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:33 DBG [TCP] accept connection lAddr=10.0.0.220:38928 rAddr=120.221.241.233:443 inbound=Redir
09:44:33 INF [TCP] connected lAddr=10.0.0.220:38928 rAddr=120.221.241.233:443 mode=rule rule=GeoIP(CN) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:33 DBG [TCP] accept connection lAddr=10.0.0.220:38944 rAddr=gchat.qpic.cn:443 inbound=Redir
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:33 INF [TCP] connected lAddr=10.0.0.220:38944 rAddr=gchat.qpic.cn:443 mode=rule rule=DomainSuffix(qpic.cn) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:33 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;aws-na-dr.intlgame.com.  IN   A
09:44:34 DBG [TCP] accept connection lAddr=10.0.0.220:4211 rAddr=zkapi.hexiny.com:80 inbound=Redir
09:44:34 DBG [Matcher] resolve success host=zkapi.hexiny.com ip=110.42.1.62
09:44:34 INF [TCP] connected lAddr=10.0.0.220:4211 rAddr=zkapi.hexiny.com:80 mode=rule rule=GeoIP(CN) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:34 DBG [TCP] accept connection lAddr=10.0.0.220:4212 rAddr=update.googleapis.com:443 inbound=Redir
09:44:34 DBG [Matcher] resolve success host=update.googleapis.com ip=58.254.137.226
09:44:34 INF [TCP] connected lAddr=10.0.0.220:4212 rAddr=update.googleapis.com:443 mode=rule rule=DomainSuffix(googleapis.com) proxy=通用 Proxy[慈善机场 | 🇯🇵 日本 | 09]
09:44:34 DBG [TCP] accept connection lAddr=10.0.0.220:4213 rAddr=update.googleapis.com:443 inbound=Redir
09:44:34 DBG [Matcher] resolve success host=update.googleapis.com ip=58.254.137.226
09:44:34 INF [TCP] connected lAddr=10.0.0.220:4213 rAddr=update.googleapis.com:443 mode=rule rule=DomainSuffix(googleapis.com) proxy=通用 Proxy[慈善机场 | 🇯🇵 日本 | 09]
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:34 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:35 DBG [TCP] accept connection lAddr=10.0.0.220:4215 rAddr=img-xlppc-zhan.xunlei.com:80 inbound=Redir
09:44:35 DBG [Matcher] resolve success host=img-xlppc-zhan.xunlei.com ip=112.122.156.216
09:44:35 INF [TCP] connected lAddr=10.0.0.220:4215 rAddr=img-xlppc-zhan.xunlei.com:80 mode=rule rule=DomainSuffix(xunlei.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:35 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:35 DBG [TCP] accept connection lAddr=10.0.0.220:4216 rAddr=masterconn2.qq.com:8081 inbound=Redir
09:44:35 DBG [Matcher] resolve success host=masterconn2.qq.com ip=111.206.148.116
09:44:35 DBG [TCP] accept connection lAddr=10.0.0.220:4217 rAddr=masterconn2.qq.com:8081 inbound=Redir
09:44:35 DBG [Matcher] resolve success host=masterconn2.qq.com ip=111.206.148.116
09:44:36 INF [TCP] connected lAddr=10.0.0.220:4216 rAddr=masterconn2.qq.com:8081 mode=rule rule=DomainSuffix(qq.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:36 INF [TCP] connected lAddr=10.0.0.220:4217 rAddr=masterconn2.qq.com:8081 mode=rule rule=DomainSuffix(qq.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:36 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;hub5pn.v6.sandai.net.    IN   A
09:44:37 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;gateway.discord.gg.  IN   A
09:44:37 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:37 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:37 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:37 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;raw.githubusercontent.com.   IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;client.wns.windows.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;client.wns.windows.com.  IN   A
09:44:39 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;client.wns.windows.com.  IN   A
09:44:40 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:40 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:40 DBG [TCP] accept connection lAddr=10.0.0.220:4223 rAddr=img-xlppc-zhan.xunlei.com:80 inbound=Redir
09:44:40 DBG [Matcher] resolve success host=img-xlppc-zhan.xunlei.com ip=112.122.156.217
09:44:40 INF [TCP] connected lAddr=10.0.0.220:4223 rAddr=img-xlppc-zhan.xunlei.com:80 mode=rule rule=DomainSuffix(xunlei.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:41 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:41 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;go.microsoft.com.    IN   A
09:44:41 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;go.microsoft.com.    IN   A
09:44:41 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;go.microsoft.com.    IN   A
09:44:42 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;gateway.discord.gg.  IN   A
09:44:42 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:42 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;github.com.  IN   A
09:44:42 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:42 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;content-autofill.googleapis.com. IN   A
09:44:43 DBG [TCP] accept connection lAddr=10.0.0.220:4227 rAddr=img-xlppc-zhan.xunlei.com:80 inbound=Redir
09:44:43 DBG [Matcher] resolve success host=img-xlppc-zhan.xunlei.com ip=112.122.156.213
09:44:43 INF [TCP] connected lAddr=10.0.0.220:4227 rAddr=img-xlppc-zhan.xunlei.com:80 mode=rule rule=DomainSuffix(xunlei.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge.microsoft.com.  IN   A
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;client.wns.windows.com.  IN   A
09:44:44 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;client.wns.windows.com.  IN   A
09:44:45 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;discord.com. IN   A
09:44:45 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;edge-mqtt.facebook.com.  IN   A
09:44:46 DBG [TCP] accept connection lAddr=10.0.0.220:4231 rAddr=img-xlppc-zhan.xunlei.com:80 inbound=Redir
09:44:46 DBG [Matcher] resolve success host=img-xlppc-zhan.xunlei.com ip=112.122.156.213
09:44:46 INF [TCP] connected lAddr=10.0.0.220:4231 rAddr=img-xlppc-zhan.xunlei.com:80 mode=rule rule=DomainSuffix(xunlei.com) proxy=Others[慈善机场 | 🇯🇵 日本 | 09]
09:44:46 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:46 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A
09:44:46 DBG [DNS Server] exchange failed error=all DNS requests failed, first error: dns: bad rdata question=;mainnet.infura.io.   IN   A

#===================== 最近运行日志获取完成(自动切换为silent模式) =====================#

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

1. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【119.147.32.178】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
2. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【112.90.140.46】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
3. SourceIP:【10.0.0.220】 - Host:【loc.map.baidu.com】 - DestinationIP:【153.37.235.69】 - Network:【tcp】 - RulePayload:【baidu】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
4. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【112.65.195.209】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
5. SourceIP:【10.0.0.220】 - Host:【accesshub-global.zego.im】 - DestinationIP:【139.224.198.146】 - Network:【tcp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
6. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【123.6.27.68】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
7. SourceIP:【10.0.0.220】 - Host:【beacons.gcp.gvt2.com】 - DestinationIP:【58.254.137.226】 - Network:【tcp】 - RulePayload:【gvt2.com】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
8. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【153.3.232.175】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
9. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【112.65.195.209】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
10. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【122.195.118.177】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
11. SourceIP:【10.0.0.220】 - Host:【zyx.qq.com】 - DestinationIP:【157.255.13.233】 - Network:【udp】 - RulePayload:【qq.com】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
12. SourceIP:【10.0.0.220】 - Host:【assets.msn.cn】 - DestinationIP:【218.58.102.48】 - Network:【tcp】 - RulePayload:【cn】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
13. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【113.108.1.110】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
14. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【112.90.142.140】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
15. SourceIP:【10.0.0.220】 - Host:【internal-api-lark-api.feishu.cn】 - DestinationIP:【140.207.195.70】 - Network:【tcp】 - RulePayload:【cn】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
16. SourceIP:【10.0.0.220】 - Host:【update.googleapis.com】 - DestinationIP:【58.254.137.226】 - Network:【tcp】 - RulePayload:【googleapis.com】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
17. SourceIP:【10.0.0.220】 - Host:【zyx.qq.com】 - DestinationIP:【157.255.13.233】 - Network:【udp】 - RulePayload:【qq.com】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
18. SourceIP:【10.0.0.220】 - Host:【gchat.qpic.cn】 - DestinationIP:【36.249.92.14】 - Network:【tcp】 - RulePayload:【qpic.cn】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】
19. SourceIP:【10.0.0.220】 - Host:【Empty】 - DestinationIP:【111.161.83.217】 - Network:【udp】 - RulePayload:【CN】 - Lastchain:【慈善机场 | 🇯🇵 日本 | 09】

OpenClash Config

这是yaml的配置。openclash使用的是默认配置。就改了个Redir-host混合模式。
# HTTP 代理端口
port: 7890 

# SOCKS5 代理端口
socks-port: 7891 

# Linux 和 macOS 的 redir 代理端口
redir-port: 7892 

# 允许局域网的连接
allow-lan: true

# 规则模式:Rule(规则) / Global(全局代理)/ Direct(全局直连)
mode: rule

# 设置日志输出级别 (默认级别:silent,即不输出任何内容,以避免因日志内容过大而导致程序内存溢出)。
# 5 个级别:silent / info / warning / error / debug。级别越高日志输出量越大,越倾向于调试,若需要请自行开启。
log-level: info
# Clash 的 RESTful API
external-controller: '0.0.0.0:9090'

# RESTful API 的口令
secret: ''

Expected Behavior

希望能正常使用

Screenshots

No response

kl79613 commented 11 months ago

加一 从昨晚开始就没法用了

SH-Wang123 commented 11 months ago

+1

janechaos commented 11 months ago

试试改成fake ip模式

xuanshao-zty commented 11 months ago

试试改成fake ip模式

改了。也一样是dns报错

kl79613 commented 11 months ago

我的莫名其妙又好了,啥都没改

janechaos commented 11 months ago

我在覆写里把dns除去114的都勾选掉就可以了

rltyty commented 11 months ago

+1

这两天突然不能访问外网. openclash报错的log都是访问代理域名时dns请求失败, 而在同一台电脑上用独立的Clash客户端使用相同的代理配置文件就访问正常.

2023-09-21 18:51:03 WRN [UDP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x: rAddr=fonts.gstatic.com:443 rule=DomainSuffix rulePayload=gstatic.com 2023-09-21 18:51:03 WRN [TCP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x:

xuanshao-zty commented 11 months ago

+1

这两天突然不能访问外网. openclash报错的log都是访问代理域名时dns请求失败, 而在同一台电脑上用独立的Clash客户端使用相同的代理配置文件就访问正常.

2023-09-21 18:51:03 WRN [UDP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x: rAddr=fonts.gstatic.com:443 rule=DomainSuffix rulePayload=gstatic.com 2023-09-21 18:51:03 WRN [TCP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x:

对的。一样的情况

rltyty commented 11 months ago

+1 这两天突然不能访问外网. openclash报错的log都是访问代理域名时dns请求失败, 而在同一台电脑上用独立的Clash客户端使用相同的代理配置文件就访问正常. 2023-09-21 18:51:03 WRN [UDP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x: rAddr=fonts.gstatic.com:443 rule=DomainSuffix rulePayload=gstatic.com 2023-09-21 18:51:03 WRN [TCP] dial failed error=: connect error: all DNS requests failed, first error: dns: bad rdata proxy=Proxy lAddr=192.168.x.x:

对的。一样的情况

可能还是和机场部分区域节点域名服务出问题有关, 我刚才做了一些尝试, 发现如果我把所有节点全部加入Proxy group, 是能找到连通的节点的. 但我通常使用的一个只有几个节点的小group不行, 所以我怀疑是部分区域节点域名无法访问. 然后又尝试了一会, 最后那个小group的也可以了.

super27036 commented 11 months ago

应该是订阅是选用规则的问题,你们试试用默认的规则,把Use Rule Provider disable试

Screen Shot 2023-09-22 at 12 19 23 AM

试吧

opalhair commented 11 months ago

我在覆写里把dns除去114的都勾选掉就可以了

我用这个方法可以

kuttakke commented 11 months ago

我在覆写里把dns除去114的都勾选掉就可以了

不知道发生了什么,但是it just works

kl79613 commented 11 months ago

我在覆写里把dns除去114的都勾选掉就可以了

不知道发生了什么,但是it just works

是只勾选114吗?

kl79613 commented 11 months ago
image

这样还是不行啊

xuanshao-zty commented 11 months ago

image 这样还是不行啊

他是说不勾选114,其他勾上

kl79613 commented 11 months ago

image 这样还是不行啊

他是说不勾选114,其他勾上

还是不行

kl79613 commented 11 months ago

2023-09-22 14:54:44 level=debug msg="[DNS] resolve www.youtube.com from https://public.dns.iij.jp:443/dns-query" 2023-09-22 14:54:44 level=debug msg="[DNS] resolve www.youtube.com from https://dns.cloudflare.com:443/dns-query" 2023-09-22 14:54:44 level=debug msg="[DNS] resolve dot.tiar.app from udp://119.28.28.28:53" 2023-09-22 14:54:44 level=debug msg="[DNS] resolve www.youtube.com from tls://dot.tiar.app:853" 2023-09-22 14:54:44 level=debug msg="[DNS] resolve www.youtube.com from https://jp.tiarap.org:443/dns-query" 2023-09-22 14:54:44 level=debug msg="[DNS Server] Exchange ;www.youtube.com.\tIN\t A failed: all DNS requests failed, first error: requesting https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": connect failed: dial tcp 103.2.57.6:443: i/o timeout\ndial tcp 103.2.57.5:443: i/o timeout" 2023-09-22 14:54:44 level=debug msg="[DNS Server] Exchange ;www.youtube.com.\tIN\t A failed: all DNS requests failed, first error: requesting https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": connect failed: dial tcp 103.2.57.6:443: i/o timeout\ndial tcp 103.2.57.5:443: i/o timeout" 2023-09-22 14:54:44 level=debug msg="[https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:44 level=debug msg="[https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:44 level=debug msg="re-creating the http client due to requesting https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": context deadline exceeded" 2023-09-22 14:54:44 level=debug msg="re-creating the http client due to requesting https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": context deadline exceeded" 2023-09-22 14:54:44 level=debug msg="[https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:44 level=debug msg="[https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:44 level=debug msg="re-creating the http client due to requesting https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2023-09-22 14:54:44 level=debug msg="re-creating the http client due to requesting https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" 2023-09-22 14:54:42 level=debug msg="[DNS] userprofile.mina.mi.com --> [123.125.102.113 111.202.0.131], from udp://114.114.114.114:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from udp://114.114.114.114:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from udp://223.5.5.5:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from https://doh.pub:443/dns-query" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from udp://119.29.29.29:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from udp://192.168.66.1:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from udp://119.28.28.28:53" 2023-09-22 14:54:42 level=debug msg="[DNS] resolve userprofile.mina.mi.com from https://dns.alidns.com:443/dns-query" 2023-09-22 14:54:42 level=debug msg="[DNS Server] Exchange ;v10.events.data.microsoft.com.\tIN\t A failed: all DNS requests failed, first error: requesting https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": read tcp 192.168.66.8:45290->103.2.57.5:443: read: connection reset by peer (resErr:<nil>)" 2023-09-22 14:54:42 level=debug msg="[DNS Server] Exchange ;v10.events.data.microsoft.com.\tIN\t A failed: all DNS requests failed, first error: requesting https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://public.dns.iij.jp:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": read tcp 192.168.66.8:45290->103.2.57.5:443: read: connection reset by peer (resErr:<nil>)" 2023-09-22 14:54:42 level=debug msg="[https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded" 2023-09-22 14:54:42 level=debug msg="[https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded" 2023-09-22 14:54:42 level=debug msg="[https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE: Get \"https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded" 2023-09-22 14:54:42 level=debug msg="[https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="[https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://dns.cloudflare.com:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded" 2023-09-22 14:54:42 level=debug msg="[https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB] using HTTP/2 for this upstream: <nil>" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://jp.tiarap.org:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded" 2023-09-22 14:54:42 level=debug msg="re-creating the http client due to requesting https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3d3dwd5b3V0dWJlA2NvbQAAAQAB: Get \"https://jp.tiar.app:443/dns-query?dns=AAABAAABAAAAAAAAA3YxMAZldmVudHMEZGF0YQltaWNyb3NvZnQDY29tAAABAAE\": context deadline exceeded"

duzefu commented 11 months ago

你试试删除fallback里面的所有国外dns服务器,从nameserver那边复制一个国内的dns服务器过来用就行. 这问题最近集中爆发.都是由于分流的国外dns导致的

kl79613 commented 11 months ago
image

@duzefu v2ex,谷歌能打开,youtube打不开是什么原因啊

duzefu commented 11 months ago

image @duzefu v2ex,谷歌能打开,youtube打不开是什么原因啊

cmd里面用命令nslookup www.youtube.com 看看能不能获取Youtube的dns. 也有一种可能是因为改成了国内DNS导致返回的服务器是靠近国内.你的VPS连不上....但是youtube这么大的体量应该不会出这种问题才对

kl79613 commented 11 months ago

image @duzefu v2ex,谷歌能打开,youtube打不开是什么原因啊

cmd里面用命令nslookup www.youtube.com 看看能不能获取Youtube的dns. 也有一种可能是因为改成了国内DNS导致返回的服务器是靠近国内.你的VPS连不上....但是youtube这么大的体量应该不会出这种问题才对

image

@duzefu 可以了,非常感谢!

Melody-Test commented 11 months ago

同样的问题

hao1196561270 commented 11 months ago

同样的问题

+1

gaoyuoppa commented 11 months ago

+1

guozijianjijiu commented 11 months ago

我和你有相同的问题。YouTube可以正常打开,但是不能播放视频,在主页视频封面,和进入视频后的留言都能加载,但视频就是加载不出来。包括现在上GitHub一样很多人的头像加载不出来。 翻阅日志是不是有关: 2023-09-23 20:39:18【/tmp/openclash_last_version】下载失败:【curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to raw.githubusercontent.com:443 】 2023-09-23 16:11:48【/tmp/clash_last_version】下载失败:【curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to ftp.jaist.ac.jp:443 】 2023-09-23 16:11:45【/tmp/clash_last_version】下载失败:【curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to raw.githubusercontent.com:443 】 2023-09-23 10:52:04【/tmp/clash_last_version】下载失败:【curl: (6) Could not resolve host: raw.githubusercontent.com】 2023-09-23 10:51:21 警告:OpenClash 启动成功,检测到您启用了IPv6的DHCP服务,可能会造成连接异常!

yang1010x commented 11 months ago

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

yang1010x commented 11 months ago

+1

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

yang1010x commented 11 months ago

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

yang1010x commented 11 months ago

同样的问题

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

Melody-Test commented 11 months ago

同样的问题

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

可以了 谢谢大佬指点

super27036 commented 11 months ago

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。 可以用,暂时解决

VantIer commented 11 months ago

经过测试,补充一条,只启用“*自定义上游 DNS 服务器”就可以解决问题了。我原本也是参照上面的兄弟的说法启用后去除fallback dns,可以正常使用了,然后突发奇想想看看是不是fallback的问题,又把fallback恢复成和之前默认状态一样的配置(其实就是再把几个勾选上),发现一样可以使用。也就是说只要开启自定义上游服务器即可,原因未知,供参考。

TGbus1 commented 11 months ago

经过测试,补充一条,只启用“*自定义上游 DNS 服务器”就可以解决问题了。我原本也是参照上面的兄弟的说法启用后去除fallback dns,可以正常使用了,然后突发奇想想看看是不是fallback的问题,又把fallback恢复成和之前默认状态一样的配置(其实就是再把几个勾选上),发现一样可以使用。也就是说只要开启自定义上游服务器即可,原因未知,供参考。

实测不行

VantIer commented 11 months ago

经过测试,补充一条,只启用“*自定义上游 DNS 服务器”就可以解决问题了。我原本也是参照上面的兄弟的说法启用后去除fallback dns,可以正常使用了,然后突发奇想想看看是不是fallback的问题,又把fallback恢复成和之前默认状态一样的配置(其实就是再把几个勾选上),发现一样可以使用。也就是说只要开启自定义上游服务器即可,原因未知,供参考。

实测不行

那就还是试试那个清空fallback的方案吧。我也不知道是更新版本解决了问题还是先取消再加上fallback解决了问题了。我只能说现在没有换配置文件+开启fallback的情况下我确实可以正常使用了

VantIer commented 11 months ago

经过测试,补充一条,只启用“*自定义上游 DNS 服务器”就可以解决问题了。我原本也是参照上面的兄弟的说法启用后去除fallback dns,可以正常使用了,然后突发奇想想看看是不是fallback的问题,又把fallback恢复成和之前默认状态一样的配置(其实就是再把几个勾选上),发现一样可以使用。也就是说只要开启自定义上游服务器即可,原因未知,供参考。

实测不行

我找了台平常不用的路由,重复了遍流程,试出来了。和网络有关的dns问题。我都移动网络可以正常使用原本的fallback中的dns(但是为什么之前不能用需要更新/开启自定义上游dns来激活,这个不清楚);而我测试用的路由是连接手机热点,联通网络,fallback dns全灭,手工从namegroup里弄个过来(最后一个那个doh.pub https的)就可以正常使用。TNND,这最近网络又在搞什么鬼?

gaoyuoppa commented 11 months ago

启用“*自定义上游 DNS 服务器”,把FallBack页里面所有的选项关闭掉。大意就是关闭FallBack DNS。

感谢。时好时坏,没发现规律。不过至少能凑合用了

iamjimmycheng commented 11 months ago

经过测试,补充一条,只启用“*自定义上游 DNS 服务器”就可以解决问题了。我原本也是参照上面的兄弟的说法启用后去除fallback dns,可以正常使用了,然后突发奇想想看看是不是fallback的问题,又把fallback恢复成和之前默认状态一样的配置(其实就是再把几个勾选上),发现一样可以使用。也就是说只要开启自定义上游服务器即可,原因未知,供参考。

的确,勾上就解决问题了,这个问题困扰了我一个月了,我都不知道哪里出问题,如何描述。

iamjimmycheng commented 11 months ago

我有另一个问题,同一个vless节点,在openclash中看YouTube只有几千,但用passwall就有8w,是什么原因呢?

yellowsavant commented 10 months ago

你配置的nameserver里有域名类的条目:

github-actions[bot] commented 8 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days