V2Ray windows客户端下载

求帮助 · 2021年1月13日 22:52

老师 最近 用V2ray 看油管很卡，什么原因？ 软件是3.18的，版本太低吗？升级吗

欧阳空空 · 2020年12月27日 22:28

v2rayn支持不支持vless

hehau · 2020年9月20日 19:25

2020/09/20 19:23:31 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://vps.helloword.info/1qaztest): 404 Not Found > websocket: bad handshake v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://vps.helloword.info/1qaztest): > write tcp 192.168.10.7:57022->112.213.108.48:443: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://vps.helloword.info/1qaztest): 404 Not Found > websocket: bad handshake] > v2ray.com/core/common/retry: all retry attempts failed

能帮忙看看这是咋回事么

hj · 2020年8月15日 14:09

配置成功
Vmess-(107***169:56789)
启动服务(2020/8/15 14:08:38)…
V2Ray 4.27.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.6 windows/386)
A unified platform for anti-censorship.
2020/08/15 14:08:38 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config: C:\Program Files (x86)\v2rayN-v3.21\config.json
2020/08/15 14:08:38 [Warning] v2ray.com/core: V2Ray 4.27.0 started
配置成功，域名伪装，但是翻墙不成功

yecher · 2020年7月28日 09:12

配置成功
Vmess-(45***170:16288)
启动服务(2020/7/28 9:10:54)…
V2Ray 4.23.4 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.1 windows/386)
A unified platform for anti-censorship.
2020/07/28 09:10:55 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config: C:\Users\Yecher\Desktop\v2rayN-Core (2)\v2rayN-Core\config.json
2020/07/28 09:10:55 [Warning] v2ray.com/core: V2Ray 4.23.4 started
这个怎么办啊，大大

alex · 2020年7月14日 10:37

配置成功
Vmess-搬瓦工(104***192:29776)
启动服务(2020/7/14 10:33:40)…
V2Ray 4.23.4 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.1 windows/386)
A unified platform for anti-censorship.
2020/07/14 10:33:43 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config: D:\v2rayN-Core\config.json
2020/07/14 10:33:43 [Warning] v2ray.com/core: V2Ray 4.23.4 started
2020/07/14 10:34:14 tcp:127.0.0.1:53361 accepted tcp:www.google.com:80 [proxy]

站长大大，这样算配置成功了吗？
访问谷歌，显示报错
500 Internal Privoxy Error
Privoxy encountered an error while processing your request:

Could not load template file no-server-data or one of its included components.

Please contact your proxy administrator.

If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It’s typically the Privoxy install directory).

lamente · 2020年6月25日 22:18

显示配置成功，但是还是上不了谷歌

hope · 2020年6月23日 12:31

配置成功
Vmess-myself(104***161:13393)
启动服务(2020/6/23 12:30:07)…
V2Ray 4.23.4 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.1 windows/386)
A unified platform for anti-censorship.
2020/06/23 12:30:07 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config: C:\Users\shine\Downloads\Compressed\v2rayN-v3.19\v2rayN-Core\config.json
2020/06/23 12:30:07 [Warning] v2ray.com/core: V2Ray 4.23.4 started

大佬。我这个算启动成功了么，访问不了外网啊

憧憬 · 2020年6月14日 16:43

大佬赐教,这个是哪里出错了，万分感谢，买的服务器
配置成功
Vmess-洛杉矶(176***155:27592)
启动服务(2020/6/14 16:33:30)…
V2Ray 4.23.4 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.1 windows/386)
A unified platform for anti-censorship.
2020/06/14 16:33:32 [Info] v2ray.com/core/common/platform/ctlcmd:
v2ctl> Read config: D:\v2rayN\v2rayN-Core\config.json
2020/06/14 16:33:32 [Warning] v2ray.com/core: V2Ray 4.23.4 started
2020/06/14 16:33:59 tcp:127.0.0.1:53176 accepted tcp:play.google.com:443 [proxy]
2020/06/14 16:34:00 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:02 tcp:127.0.0.1:53179 accepted tcp:www.google.com:443 [proxy]
2020/06/14 16:34:02 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:03 tcp:127.0.0.1:53184 accepted tcp:play.google.com:443 [proxy]
2020/06/14 16:34:03 tcp:127.0.0.1:53187 accepted tcp:static.xx.fbcdn.net:443 [proxy]
2020/06/14 16:34:03 tcp:127.0.0.1:53188 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:03 tcp:127.0.0.1:53189 accepted tcp:inputtools.google.com:443 [proxy]
2020/06/14 16:34:03 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:04 tcp:127.0.0.1:53193 accepted tcp:play.google.com:443 [proxy]
2020/06/14 16:34:04 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:05 tcp:127.0.0.1:53197 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:05 tcp:127.0.0.1:53198 accepted tcp:static.xx.fbcdn.net:443 [proxy]
2020/06/14 16:34:05 tcp:127.0.0.1:53201 accepted tcp:play.google.com:443 [proxy]
2020/06/14 16:34:05 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:09 tcp:127.0.0.1:53206 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:09 tcp:127.0.0.1:53208 accepted tcp:static.xx.fbcdn.net:443 [proxy]
2020/06/14 16:34:09 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:15 tcp:127.0.0.1:53211 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:15 tcp:127.0.0.1:53213 accepted tcp:static.xx.fbcdn.net:443 [proxy]
2020/06/14 16:34:16 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > tls: first record does not look like a TLS handshake
2020/06/14 16:34:19 tcp:127.0.0.1:53217 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:19 tcp:127.0.0.1:53218 accepted tcp:static.xx.fbcdn.net:443 [proxy]
2020/06/14 16:34:22 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > read tcp 192.168.0.105:53219->176.122.148.155:27592: wsarecv: An existing connection was forcibly closed by the remote host.
2020/06/14 16:34:53 tcp:127.0.0.1:53228 accepted tcp:www.facebook.com:443 [proxy]
2020/06/14 16:34:53 tcp:127.0.0.1:53229 accepted tcp:static.xx.fbcdn.net:443 [proxy]