V2ray-core: 移动端功能正常，PC端无法正常工作

Created on 29 Jul 2017  ·  10Comments  ·  Source: v2ray/v2ray-core

提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。

Please read the instruction and answer the following questions before submitting your issue. Thank you.

VPS系统:centos7 X64

[root@vultr v2ray]# cat /proc/version
Linux version 4.12.4-1.el7.elrepo.x86_64 (mockbuild@Build64R7) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Thu Jul 27 20:03:28 EDT 2017
[root@vultr v2ray]# uname -r
4.12.4-1.el7.elrepo.x86_64

服务端防火墙已关闭

1) 你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
· V2Ray v2.33 (One for all) 20170609 服务端
· v2ray-v2.33.1-windows-64 客户端
· v2rayN-1.11 第三方图形化界面
· proxifier

2) 你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
访问一切被墙的软件网站及服务

3) 你看到的不正常的现象是什么？
服务端设置完成后用同一份配置文件 可以在android（Actinium）及ios(shadowrocket)上运作
而电脑v2rayN配置完通过proxifier无法正常工作
4) 你期待看到的正确表现是怎样的？
能够正常访问被墙的网站及服务

---------------------------------附加proxifier日志------------------------------------------------------

[07.29 21:20:35] wv2ray.exe *64 - XXXXXXXXXXXXX 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:38] chrome.exe - www.google.com:80 打开通过代理 127.0.0.1:1080 SOCKS5

[07.29 21:20:38] chrome.exe - www.google.com:80 打开通过代理 127.0.0.1:1080 SOCKS5

5) 请附上你的配置文件（提交 Issue 前请隐藏服务器端IP地址）。

-------------------------------- （服务器端配置文件）--------------------------------------------

{
"log": {
"access": "/var/log/v2ray/access.log",
"error": "/var/log/v2ray/error.log",
"loglevel": "warning"
},
"inbound": {
"port": 20163,
"listen": null,
"protocol": "vmess",
"settings": {
"auth": null,
"udp": false,
"ip": null,
"clients": [
{
"id": "721b6e30-2432-489a-8169-807ce3556071",
"alterId": 66,
"security": null
}
]
},
"streamSettings": {
"network": "tcp",
"security": "",
"tcpSettings": null,
"kcpSettings": null,
"wsSettings": null
}
},
"outbound": {
"tag": null,
"protocol": "freedom",
"settings": null,
"streamSettings": null,
"mux": null
},
"inboundDetour": null,
"outboundDetour": [
{
"protocol": "blackhole",
"settings": null,
"tag": "blocked"
}
],
"dns": null,
"routing": {
"strategy": "rules",
"settings": {
"domainStrategy": null,
"rules": [
{
"type": "field",
"port": null,
"outboundTag": "blocked",
"ip": [
"0.0.0.0/8",
"10.0.0.0/8",
"100.64.0.0/10",
"127.0.0.0/8",
"169.254.0.0/16",
"172.16.0.0/12",
"192.0.0.0/24",
"192.0.2.0/24",
"192.168.0.0/16",
"198.18.0.0/15",
"198.51.100.0/24",
"203.0.113.0/24",
"::1/128",
"fc00::/7",
"fe80::/10"
],
"domain": null
}
]
}
}
}

------------------------------（客户端配置文件）-----------------------------------------------------------
{
"log": {
"access": "Vaccess.log",
"error": "Verror.log",
"loglevel": "warning"
},
"inbound": {
"port": 1080,
"listen": "127.0.0.1",
"protocol": "socks",
"settings": {
"auth": "noauth",
"udp": true,
"ip": "127.0.0.1",
"clients": null
},
"streamSettings": null
},
"outbound": {
"tag": "agentout",
"protocol": "vmess",
"settings": {
"vnext": [
{
"address": "XXXXXXXXXXXXXXX",
"port": 20163,
"users": [
{
"id": "721b6e30-2432-489a-8169-807ce3556071",
"alterId": 66,
"security": "aes-128-gcm"
}
]
}
]
},
"streamSettings": {
"network": "tcp",
"security": "",
"tcpSettings": null,
"kcpSettings": null,
"wsSettings": null
},
"mux": {
"enabled": true
}
},
"inboundDetour": null,
"outboundDetour": [
{
"protocol": "freedom",
"settings": {
"response": null
},
"tag": "direct"
},
{
"protocol": "blackhole",
"settings": {
"response": {
"type": "http"
}
},
"tag": "blockout"
}
],
"dns": {
"servers": [
"8.8.8.8",
"8.8.4.4",
"localhost"
]
},
"routing": {
"strategy": "rules",
"settings": {
"domainStrategy": "IPIfNonMatch",
"rules": [
{
"type": "field",
"port": null,
"outboundTag": "direct",
"ip": [
"0.0.0.0/8",
"10.0.0.0/8",
"100.64.0.0/10",
"127.0.0.0/8",
"169.254.0.0/16",
"172.16.0.0/12",
"192.0.0.0/24",
"192.0.2.0/24",
"192.168.0.0/16",
"198.18.0.0/15",
"198.51.100.0/24",
"203.0.113.0/24",
"::1/128",
"fc00::/7",
"fe80::/10"
],
"domain": null
}
]
}
}
}

6) 请附上出错时软件输出的日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

Server Log File（服务器端日志）:

```
// 在这里附上服务器端日志
2017/07/28 17:42:52 [Warning]Core: V2Ray started
2017/07/29 02:54:29 [Warning]Core: V2Ray started
2017/07/29 03:04:01 [Warning]Core: V2Ray started
2017/07/29 03:05:25 [Warning]Core: V2Ray started

Client Log File（客户端日志）:

2017/07/29 23:24:08 [Info]Transport|Internet|TCP: listening TCP on 127.0.0.1:1080
2017/07/29 23:24:08 [Info]Transport|Internet|UDP: listening UDP on 127.0.0.1:1080
2017/07/29 23:24:08 [Warning]Core: V2Ray started
2017/07/29 23:24:17 [Info]Transport|Internet|TCP: listening TCP on 127.0.0.1:1080
2017/07/29 23:24:17 [Info]Transport|Internet|UDP: listening UDP on 127.0.0.1:1080
2017/07/29 23:24:17 [Warning]Core: V2Ray started
2017/07/29 23:24:23 [Info]Proxy|Socks: TCP Connect request to tcp:93.46.8.89:80
2017/07/29 23:24:23 [Info]App|Dispatcher|Default: default route for tcp:93.46.8.89:80
2017/07/29 23:24:23 [Info]App|Proxyman|Mux: dispatching request to tcp:93.46.8.89:80
2017/07/29 23:24:23 [Info]Transport|Internet|TCP: dailing TCP to tcp:XXXXXXXXXXXXXXXX
2017/07/29 23:24:23 [Info]Proxy|Socks: TCP Connect request to tcp:XXXXXXXXXXXXXXXX
2017/07/29 23:24:23 [Info]App|Dispatcher|Default: default route for tcp:XXXXXXXXXXXXX
2017/07/29 23:24:23 [Info]App|Proxyman|Mux: dispatching request to tcp:XXXXXXXXXXX
2017/07/29 23:24:23 [Info]Proxy|VMess|Outbound: tunneling request to tcp:v1.mux.cool:9527 via tcp:104.207.158.201:20163
2017/07/29 23:24:27 [Info]Proxy|Socks: TCP Connect request to tcp:93.46.8.89:80
2017/07/29 23:24:27 [Info]App|Dispatcher|Default: default route for tcp:93.46.8.89:80
2017/07/29 23:24:27 [Info]App|Proxyman|Mux: dispatching request to tcp:93.46.8.89:80

picture fkdhhm

Most helpful comment

pc系统时间一定要正确，否则也会导致pc端无法正常工作。

picture piceone on 26 Feb 2020
👍4

All 10 comments

@fkdhhm Reply #1

仔细看 Proxifier 日志的第一行:

[07.29 21:20:35] wv2ray.exe *64 - XXXXXXXXXXXXX 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:35] chrome.exe - www.google.com:443 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:38] chrome.exe - www.google.com:80 打开通过代理 127.0.0.1:1080 SOCKS5
[07.29 21:20:38] chrome.exe - www.google.com:80 打开通过代理 127.0.0.1:1080 SOCKS5

我总觉得 Proxifier 把 wv2ray.exe 的连接也代理了，你可能得配置 Proxifier 把 wv2ray.exe 排除掉。

oing9179 picture oing9179 on 30 Jul 2017

@oing9179 我把wv2ray.exe添加直连后
还是不可以

fkdhhm picture fkdhhm on 30 Jul 2017

@fkdhhm Reply #3

你先试试不用 Proxifier 能否打开网页之类的。
如果能连上，那就把 wv2ray.exe 直连之后的 v2ray的日志 和 Proxifier的日志 都贴出来。

oing9179 picture oing9179 on 30 Jul 2017

@oing9179
switchyomega 设置为127.0.0.1：1080 可翻
使用proxifier 同时将switchyomega 设置为直连模式下可翻

-------------------------------------------------------------switchyomega直连状态下 proxifier日志----------------------------------------------------------------------

[2017.07.30 15:36:28] [2017.07.30 15:36:32] chrome.exe (4600) - resolve www.google.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve apis.google.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve ssl.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve csi.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve apis.google.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve www.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve ssl.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve csi.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - resolve www.google.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - apis.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - resolve www.gstatic.com : proxy
[2017.07.30 15:36:33] chrome.exe (4600) - ssl.gstatic.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - apis.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - ssl.gstatic.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.gstatic.com:443 [2017.07.30 15:36:33] wv2ray.exe (6268) *64 - 104.207.158.201:20163 [2017.07.30 15:36:33] chrome.exe (4600) - www.gstatic.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - apis.google.com:443 GetSockName : 127.0.0.1:51741
[2017.07.30 15:36:33] chrome.exe (4600) - ssl.gstatic.com:443 GetSockName : 127.0.0.1:51744
[2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 GetSockName : 127.0.0.1:51748
[2017.07.30 15:36:33] chrome.exe (4600) - www.gstatic.com:443 GetSockName : 127.0.0.1:51751
[2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 GetSockName : 127.0.0.1:51754
[2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 GetSockName : 127.0.0.1:51757
[2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 GetSockName : 127.0.0.1:51760
[2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:33] chrome.exe (4600) - www.google.com:443 GetSockName : 127.0.0.1:51763

[2017.07.30 15:36:33] wv2ray.exe (6268) *64 - 104.207.158.201:20163 [2017.07.30 15:36:34] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:36:34] chrome.exe (4600) - www.google.com:443

-------------------------------------------------------------switchyomega直连状态下 v2rayN verror日志-------------------------------------------------------------------
2017/07/30 15:36:17 [Warning]Core: V2Ray started
2017/07/30 15:36:32 [Info]Proxy|Socks: TCP Connect request to tcp:apis.google.com:443
2017/07/30 15:36:32 [Info]App|Router: looking up IP for tcp:apis.google.com:443
2017/07/30 15:36:32 [Debug]App|DNS|Server: add pending request id 29143
2017/07/30 15:36:32 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]Transport|Internet|UDP: establishing new connection for udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]App|Dispatcher|Default: default route for udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]App|Proxyman|Mux: dispatching request to udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]Transport|Internet|TCP: dailing TCP to tcp:104.207.158.201:20163
2017/07/30 15:36:32 [Info]Proxy|Socks: TCP Connect request to tcp:ssl.gstatic.com:443
2017/07/30 15:36:32 [Info]App|Router: looking up IP for tcp:ssl.gstatic.com:443
2017/07/30 15:36:32 [Debug]App|DNS|Server: add pending request id 35814
2017/07/30 15:36:32 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]Proxy|Socks: TCP Connect request to tcp:www.google.com:443
2017/07/30 15:36:32 [Info]App|Router: looking up IP for tcp:www.google.com:443
2017/07/30 15:36:32 [Debug]App|DNS|Server: add pending request id 14041
2017/07/30 15:36:32 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:32 [Info]Proxy|Socks: TCP Connect request to tcp:www.gstatic.com:443
2017/07/30 15:36:33 [Info]App|Router: looking up IP for tcp:www.gstatic.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: add pending request id 7291
2017/07/30 15:36:33 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:33 [Info]Proxy|Socks: TCP Connect request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Router: looking up IP for tcp:www.google.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: add pending request id 47312
2017/07/30 15:36:33 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:33 [Info]Proxy|Socks: TCP Connect request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Router: looking up IP for tcp:www.google.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: add pending request id 6247
2017/07/30 15:36:33 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:36:33 [Info]Proxy|VMess|Outbound: tunneling request to tcp:v1.mux.cool:9527 via tcp:104.207.158.201:20163
2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 7291 content: ;; opcode: QUERY, status: NOERROR, id: 7291
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.gstatic.com. IN A

;; ANSWER SECTION:
www.gstatic.com. 23 IN A 216.58.195.227

2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 35814 content: ;; opcode: QUERY, status: NOERROR, id: 35814
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ssl.gstatic.com. IN A

;; ANSWER SECTION:
ssl.gstatic.com. 208 IN A 216.58.194.195

2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain ssl.gstatic.com.
2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain www.gstatic.com.
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:ssl.gstatic.com:443
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.gstatic.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:ssl.gstatic.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.gstatic.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 6247 content: ;; opcode: QUERY, status: NOERROR, id: 6247
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com. IN A

;; ANSWER SECTION:
www.google.com. 82 IN A 216.58.192.4

2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 14041 content: ;; opcode: QUERY, status: NOERROR, id: 14041
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com. IN A

;; ANSWER SECTION:
www.google.com. 75 IN A 216.58.192.4

2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 47312 content: ;; opcode: QUERY, status: NOERROR, id: 47312
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com. IN A

;; ANSWER SECTION:
www.google.com. 75 IN A 216.58.192.4

2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain www.google.com.
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.google.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: handling response for id 29143 content: ;; opcode: QUERY, status: NOERROR, id: 29143
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;apis.google.com. IN A

;; ANSWER SECTION:
apis.google.com. 86399 IN CNAME plus.l.google.com.
plus.l.google.com. 299 IN A 216.58.194.206

2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain www.google.com.
2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain apis.google.com.
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:apis.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:apis.google.com:443
2017/07/30 15:36:33 [Debug]App|DNS|Server: returning 1 IPs for domain www.google.com.
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]Proxy|Socks: TCP Connect request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Router: looking up IP for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]Proxy|Socks: TCP Connect request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Router: looking up IP for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Dispatcher|Default: default route for tcp:www.google.com:443
2017/07/30 15:36:33 [Info]App|Proxyman|Mux: dispatching request to tcp:www.google.com:443
2017/07/30 15:36:33 [Info]Transport|Internet|TCP: dailing TCP to tcp:104.207.158.201:20163

2017/07/30 15:36:34 [Info]Proxy|VMess|Outbound: tunneling request to tcp:v1.mux.cool:9527 via tcp:104.207.158.201:20163

--------------------------------------------------------------switchyomega系统代理状态下 proxifier日志---------------------------------------------------------------------
[2017.07.30 15:37:28] chrome.exe (4600) - apis.google.com:443 [2017.07.30 15:37:28] chrome.exe (4600) - ssl.gstatic.com:443 [2017.07.30 15:37:28] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:37:28] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:37:28] chrome.exe (4600) - www.google.com:443 [2017.07.30 15:37:28] chrome.exe (4600) - www.gstatic.com:443 [2017.07.30 15:38:09] chrome.exe (4600) - resolve wpad : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve wpad : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve wpad : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve wpad : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - wpad:80 [2017.07.30 15:38:09] chrome.exe (4600) - wpad:80 [2017.07.30 15:38:09] chrome.exe (4600) - wpad:80 GetSockName : 127.0.0.1:51775
[2017.07.30 15:38:09] wv2ray.exe (7756) *64 - 104.207.158.201:20163 [2017.07.30 15:38:09] chrome.exe (4600) - resolve apis.google.com : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve csi.gstatic.com : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve apis.google.com : proxy
[2017.07.30 15:38:09] chrome.exe (4600) - resolve csi.gstatic.com : proxy
[2017.07.30 15:38:13] chrome.exe (4600) - resolve ssl.gstatic.com : proxy
[2017.07.30 15:38:13] chrome.exe (4600) - resolve ssl.gstatic.com : proxy
[2017.07.30 15:38:19] [2017.07.30 15:38:21] chrome.exe (4600) - resolve www.gstatic.com : proxy
[2017.07.30 15:38:21] chrome.exe (4600) - resolve www.gstatic.com : proxy

-------------------------------------------------------------switchyomega系统代理状态下 v2rayN verror日志----------------------------------------------------------------------

2017/07/30 15:37:39 [Warning]Core: V2Ray started
2017/07/30 15:37:56 [Info]Transport|Internet|TCP: listening TCP on 127.0.0.1:1080
2017/07/30 15:37:56 [Info]Transport|Internet|UDP: listening UDP on 127.0.0.1:1080
2017/07/30 15:37:56 [Warning]Core: V2Ray started
2017/07/30 15:38:04 [Warning]Core: V2Ray started
2017/07/30 15:38:09 [Info]Proxy|Socks: TCP Connect request to tcp:wpad:80
2017/07/30 15:38:09 [Info]App|Router: looking up IP for tcp:wpad:80
2017/07/30 15:38:09 [Debug]App|DNS|Server: add pending request id 27642
2017/07/30 15:38:09 [Debug]Transport|Internet|UDP: dispatch request to: udp:8.8.8.8:53
2017/07/30 15:38:09 [Info]Transport|Internet|UDP: establishing new connection for udp:8.8.8.8:53
2017/07/30 15:38:09 [Info]App|Dispatcher|Default: default route for udp:8.8.8.8:53
2017/07/30 15:38:09 [Info]App|Proxyman|Mux: dispatching request to udp:8.8.8.8:53
2017/07/30 15:38:09 [Info]Transport|Internet|TCP: dailing TCP to tcp:104.207.158.201:20163
2017/07/30 15:38:09 [Info]Proxy|VMess|Outbound: tunneling request to tcp:v1.mux.cool:9527 via tcp:104.207.158.201:20163
2017/07/30 15:38:09 [Debug]App|DNS|Server: handling response for id 27642 content: ;; opcode: QUERY, status: NXDOMAIN, id: 27642
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;wpad. IN A

;; AUTHORITY SECTION:
. 69487 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017072901 1800 900 604800 86400

2017/07/30 15:38:09 [Debug]App|DNS|Server: returning 0 IPs for domain wpad.
2017/07/30 15:38:09 [Info]App|Dispatcher|Default: default route for tcp:wpad:80
2017/07/30 15:38:09 [Info]App|Proxyman|Mux: dispatching request to tcp:wpad:80

fkdhhm picture fkdhhm on 30 Jul 2017

既然 "使用proxifier 同时将switchyomega 设置为直连模式下可翻"：

  1. 已经可以访问网页了，好像已经解决了你的问题吧?
  2. 如果没有解决的话，可否再详细的描述一下问题，并贴出 你是如何配置 wv2ray.exe 直连的
oing9179 picture oing9179 on 30 Jul 2017

@oing9179
加了个switchyomega就可以用了，虽然不太明白原理
很感谢你对我的帮助！
再次感谢！

fkdhhm picture fkdhhm on 30 Jul 2017

pc系统时间一定要正确，否则也会导致pc端无法正常工作。

piceone picture piceone on 26 Feb 2020
👍4

pc系统时间一定要正确，否则也会导致pc端无法正常工作。

就是这个系统时间差错，解决了困扰我很久的问题！

Litangren picture Litangren on 15 Mar 2020

pc系统时间一定要正确，否则也会导致pc端无法正常工作。

这个才是真理，哈哈哈

qiuqiran picture qiuqiran on 7 Jun 2020

pc系统时间一定要正确，否则也会导致pc端无法正常工作。
虽然一直在强调，但还是短路了，找了半天不知道啥情况

ouzc12358 picture ouzc12358 on 10 Jul 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

vonhezhou picture vonhezhou  ·  4Comments
sunsan05 picture sunsan05  ·  3Comments
qnxsgwy picture qnxsgwy  ·  3Comments
limaofu picture limaofu  ·  3Comments
pingma picture pingma  ·  4Comments