+0000 2023-12-23 18:47:56 ERROR dns: exchange failed for content-autofill.googleapis.com. IN HTTPS: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:47:56 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:47:59 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:47:59 ERROR dns: exchange failed for content-autofill.googleapis.com. IN HTTPS: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:01 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:01 ERROR [2922652564 4ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64804: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:01 ERROR [1669462189 4ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64805: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [1062723673 5ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64806: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [2284856066 4ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64807: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [29933215 5ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64808: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [98617540 3ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64809: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [3600971929 4ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64810: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR [2037347543 4ms] inbound/redirect[redirect_tcp]: process connection from 192.168.6.184:64811: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:02 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:03 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:03 ERROR dns: exchange failed for content-autofill.googleapis.com. IN HTTPS: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:04 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:04 ERROR dns: exchange failed for google.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:04 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:04 ERROR dns: exchange failed for content-autofill.googleapis.com. IN HTTPS: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:05 ERROR dns: exchange failed for content-autofill.googleapis.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused +0000 2023-12-23 18:48:05 ERROR dns: exchange failed for google.com. IN A: dial tcp 127.0.0.1:2082: connect: connection refused
节点日志,订阅了节点别的都是默认的没动,
采用了全局方式还是不行,全局下国内国外都无法访问,是 ssr 模式
1 Fucter 2023-12-24 03:49:26 +08:00 via Android 2 很不好用,还是用 1 吧 |
3 swxk521 2023-12-24 05:02:29 +08:00 via Android 节点能连通吗?我在用 2 ,不过没用 ssr 协议,都正常 |
![]() | 5 300 2023-12-24 08:18:26 +08:00 还可能死循环,CPU 100%,唯一解决方法就是抓开机它还没启动的 timing ,设置成禁用。 我不知道是不是我配置问题 |
![]() | 6 Goooooos 2023-12-24 09:10:13 +08:00 看错误日志,是 dns 配置有问题吧 |
![]() | 7 yyzh 2023-12-24 09:11:42 +08:00 via Android |
8 xiaohantx OP @winterbells 好像没有…因为就走节点时候不行,不走节点就正常 100%理论上会占用系统所有都不行 |
9 xiaohantx OP @Goooooos dns 用的默认的 tcp 模式,然后 1.1.1.1pw1 正常 2 的不走节点直连就正常 |
10 xiaohantx OP @yyzh 因为我选的全局,试了下节点走不通,但是这个节点 pw1 和纸飞机或者别的都正常,最后我用 openclash 算了没办法… |
![]() | 12 xpn282 2023-12-24 23:30:45 +08:00 @xiaohantx 这些代理工具都用了个遍,对我而言,竟然最稳定、最不容易出错、最灵活的是 OpenClash Meta ,前提是理解 clash 的机制,自己能撸规则 |
![]() | 14 UXha45veSNpWCwZR 2024-01-31 21:50:26 +08:00 dns: exchange failed 我遇到,是因有置.保能的情下,再查有打密端口之的,就可以了. |