[Bug] Error occurred during requsting "http://www.google.com" ; Error: QNetworkReply::OperationCanceledError #103
Description
感谢你向 V2Ray Desktop 提交 issue！
在提交之前，请确认：
- 我已经在 Issue Tracker 中找过我要提出的问题
- 如果你可以自己 Debug 并解决的话，提交 PR 吧！
请注意，如果你并没有遵照这个 issue template 填写内容，我们将直接关闭这个 issue。
我都确认过了，我要继续提交。
请附上任何可以帮助我们解决这个问题的信息，如果我们收到的信息不足，我们将对这个 issue 加上 details needed 标记并在收到更多资讯之前关闭 issue。
V2Ray Desktop Config
{
"allow-lan": true,
"bind-address": "127.0.0.1",
"dns": {
"enable": false,
"listen": "0.0.0.0:53",
"nameserver": [
"8.8.8.8",
"4.4.4.4"
]
},
"log-level": "info",
"mode": "rule",
"port": 8088,
"proxies": [
{
"alterId": 0,
"cipher": "auto",
"name": "ArshVPN",
"network": "tcp",
"port": 52816,
"server": "arshiaconn.online",
"skip-cert-verify": true,
"tls": true,
"type": "vmess",
"udp": false,
"uuid": "e969c2e7-7ee0-4924-fac0-948f7dd07fb1"
}
],
"proxy-groups": [
{
"interval": 300,
"name": "PROXY",
"proxies": [
"ArshVPN"
],
"type": "load-balance",
"url": "http://www.gstatic.com/generate_204"
}
],
"rules": [
"MATCH, PROXY"
],
"socks-port": 8086
}
...
V2Ray Desktop Log
2023/02/17 17:52:08 [info] clash: Start initial compatible provider PROXY
2023/02/17 17:52:08 [info] clash: SOCKS proxy listening at: 127.0.0.1:8086
2023/02/17 17:52:08 [info] clash: HTTP proxy listening at: 127.0.0.1:8088
2023/02/17 17:52:08 [error] clash: Start DNS server error: missing port in address
2023/02/17 17:52:08 [Info] v2ray-desktop: Connected to "ArshVPN"
2023/02/17 17:52:07 [Warning] v2ray-desktop: QIODevice::read (QProcess): WriteOnly device
2023/02/17 17:52:07 [Info] v2ray-desktop: Disconnected from "ArshVPN"
2023/02/17 17:52:07 [Critical] v2ray-desktop: Failed to start Clash.
2023/02/17 17:52:07 [Critical] v2ray-desktop: ""
2023/02/17 17:51:46 [Info] v2ray-desktop: Connected to "ArshVPN"
2023/02/17 17:51:43 [Info] v2ray-desktop: Start to get url: "http://www.google.com"
2023/02/17 17:51:42 [Info] v2ray-desktop: Start to get url: "http://www.baidu.com"
2023/02/17 17:51:40 [Warning] v2ray-desktop: QIODevice::read (QProcess): WriteOnly device
2023/02/17 17:51:40 [Info] v2ray-desktop: Disconnected from "ArshVPN"
2023/02/17 17:51:40 [Critical] v2ray-desktop: Failed to start Clash.
2023/02/17 17:51:40 [Critical] v2ray-desktop: ""
2023/02/17 17:51:32 [Warning] v2ray-desktop: Timed out when requesting "http://www.google.com"
2023/02/17 17:51:32 [Critical] v2ray-desktop: Error occurred during requsting "http://www.google.com" ; Error: QNetworkReply::OperationCanceledError
2023/02/17 17:51:29 [Info] v2ray-desktop: Start to get url: "http://www.google.com"
2023/02/17 17:51:28 [Info] v2ray-desktop: Start to get url: "http://www.baidu.com"
2023/02/17 17:51:27 [Warning] v2ray-desktop: Timed out when requesting "http://www.google.com"
2023/02/17 17:51:27 [Critical] v2ray-desktop: Error occurred during requsting "http://www.google.com" ; Error: QNetworkReply::OperationCanceledError
...
环境 Environment
- 操作系统 (the OS for running the client)
Arch-Linux 64-bit
...
说明 Description
The proxy is connectable using other v2ray platforms but when connecting to the proxy and turning on clash, it will still say that system proxy isn't connected and also it is not connected in practice too (blocked sites don't appear)
重现问题的具体布骤 Steps to Reproduce
- Add a vmess connection
- Connect to said proxy
- ...
我预期会发生……？
Connection to the proxy and blocked websites being unlocked
实际上发生了什麽？
As you can see, it says: System proxy: disabled even tho it's supposed to be enabled.
System proxy has been set to both HTTP and SOCKS and the different Rule/Direct/Global modes have been tested.