Shadowsocks-windows: Win7 64位ss无法连接问题
shadowsocks-csharp日志里出现“System.Net.Sockets.SocketException: 由于目标计算机积极拒绝，无法连接。fe80::5930:665f:1428:d786%11:8388System.Net.Sockets.SocketException: 由于目标计算机积极拒绝，无法连接。 fe80::5930:665f:1428:d786%11:8388
在 System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
在 Shadowsocks.Controller.Handler.ConnectCallback(IAsyncResult ar)
[2015-07-25 21:06:08] System.Reflection.TargetInvocationException: 操作过程中出现异常，结果无效。有关异常的详细信息，请查看 InnerException。 ---> System.Net.WebException: 远程服务器返回错误: (504) 网关超时。
在 System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
在 System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
在 System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- 内部异常堆栈跟踪的结尾 ---
在 System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
在 System.Net.DownloadStringCompletedEventArgs.get_Result()
在 Shadowsocks.Controller.UpdateChecker.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)”
而同样的设置在另外一台32位win7笔记本上就可以连接，求问大大怎么解决，求帮助！！！
jessetoo
All 42 comments
可以把配置文件从好的机器上拷过去覆盖再测一下。
clowwindy
on 25 Jul 2015
@clowwindy 经过测试，没有用
jessetoo
on 25 Jul 2015
[误报，已解决]
同样无法连接，win7sp1x64，vps是搬瓦工。
[2015-07-26 03:05:56] System.Reflection.TargetInvocationException: 操作过程中出现异常，结果无效。有关异常的详细信息，请查看 InnerException。 ---> System.Net.WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 由于远程方已关闭传输流，身份验证失败。
在 System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
在 System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)
在 System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
在 System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
在 System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- 内部异常堆栈跟踪的结尾 ---
在 System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
在 System.Net.DownloadStringCompletedEventArgs.get_Result()
在 Shadowsocks.Controller.UpdateChecker.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
同一服务器win8.1的dotnet4版本就没有问题。
wingtsubasa
on 25 Jul 2015
可以试试一些老版本
https://sourceforge.net/projects/shadowsocksgui/files/dist/
如果用老版本也没有用，应该还是防火墙或者网络问题。
clowwindy
on 26 Jul 2015
现在已回退到2.4版本，正常使用中。
2015年7月26日 上午9:13于 "clowwindy" [email protected]写道：
可以试试一些老版本
https://sourceforge.net/projects/shadowsocksgui/files/dist/如果用老版本也没有用，应该还是防火墙或者网络问题。
—
Reply to this email directly or view it on GitHub
https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-124924680
.
wingtsubasa
on 26 Jul 2015
@wingtsubasa 2.5 是如何设置的呢？有几个服务器？有没有设置负载均衡或者高可用？
clowwindy
on 26 Jul 2015
能否把完整的配置文件贴出来看看？IP 可以打码。
clowwindy
on 26 Jul 2015
@clowwindy 大大，我换了好多客户端，依然无解，还是会自动连接到那个fe80::5930:665f:1428:d786%11:8388，经排查这是ipv6地址……而同样的错误，一位网友也出现过 http://bbs.byr.cn/#!article/Linux/148334
jessetoo
on 26 Jul 2015
@clowwindy 配置文件如下
{
"configs" : [
{
"server" : "_._.com",
"server_port" : 19627,
"password" : "**326",
"method" : "aes-128-cfb",
"remarks" : ""}
],
"strategy" : null,
"index" : 0,
"global" : false,
"enabled" : false,
"shareOverLan" : false,
"isDefault" : false,
"localPort" : 1080,
"pacUrl" : null,
"useOnlinePac" : false}
jessetoo
on 26 Jul 2015
👓[image: 内嵌图片 1]
2015-07-26 11:17 GMT+08:00 clowwindy [email protected]:
能否把完整的配置文件贴出来看看？IP 可以打码。
—
Reply to this email directly or view it on GitHub
https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-124936215
.
chenping2015
on 26 Jul 2015
如果在菜单里再手动选一下服务器，或者选高可用呢？
clowwindy
on 26 Jul 2015
@clowwindy 已排除故障，问题出在防火墙上，可执行文件及子进程加入白名单后一切正常了。由于win8使用相同防火墙但是没有出现问题，win7用之前的版本也不存在问题，所以没有往这方面想。这是误报了，抱歉！
wingtsubasa
on 26 Jul 2015
@wingtsubasa 执行文件及子进怎么加入白名单?
jessetoo
on 26 Jul 2015
这要看防火墙的具体设置了，各软件不同。以我用的迈克菲为例，在防火墙>程序的Internet连接，将主进程shadowsocks.exe和子进程ss_polipo.exe设置为“不保护”，即全面放行。通常友好的防火墙界面会更直白的表述为白名单，加入的进程即不受拦截。
2015年7月26日 下午12:37于 "jessetoo" [email protected]写道：
@wingtsubasa https://github.com/wingtsubasa 执行文件及子进怎么加入白名单?
—
Reply to this email directly or view it on GitHub
https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-124945129
.
wingtsubasa
on 26 Jul 2015
@wingtsubasa windows7 自带的防火墙怎么设置？
jessetoo
on 26 Jul 2015
更新到 2.5.1，再贴一下完整的日志，从更新以后的第一行开始，每一行前面有日期时间。
clowwindy
on 26 Jul 2015
@clowwindy [2015-07-26 12:52:22] HA switching to server: _._.com:19627
[2015-07-26 12:52:22] Shadowsocks started
[2015-07-26 12:52:26] System.Net.Sockets.SocketException: 请求的名称有效，但是找不到请求的类型的数据。
在 System.Net.Dns.GetAddrInfo(String name)
在 System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
在 System.Net.Dns.GetHostEntry(String hostNameOrAddress)
在 Shadowsocks.Controller.Handler.StartConnect()
[2015-07-26 12:52:28] System.Net.Sockets.SocketException: 请求的名称有效，但是找不到请求的类型的数据。
在 System.Net.Dns.GetAddrInfo(String name)
在 System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
在 System.Net.Dns.GetHostEntry(String hostNameOrAddress)
在 Shadowsocks.Controller.Handler.StartConnect()
[2015-07-26 12:52:28] System.Reflection.TargetInvocationException: 操作过程中出现异常，结果无效。有关异常的详细信息，请查看 InnerException。 ---> System.Net.WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 由于远程方已关闭传输流，身份验证失败。
在 System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
在 System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)
在 System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
在 System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
在 System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- 内部异常堆栈跟踪的结尾 ---
在 System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
在 System.Net.DownloadStringCompletedEventArgs.get_Result()
在 Shadowsocks.Controller.UpdateChecker.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
[2015-07-26 12:53:22] Shadowsocks started
[2015-07-26 12:53:22] System.ArgumentException: No server configured
在 Shadowsocks.Controller.Handler.CreateRemote()
在 Shadowsocks.Controller.Handler.StartConnect()
[2015-07-26 12:53:22] System.ArgumentException: No server configured
在 Shadowsocks.Controller.Handler.CreateRemote()
在 Shadowsocks.Controller.Handler.StartConnect()
[2015-07-26 12:53:39] Shadowsocks started
[2015-07-26 12:54:16] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:24] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:54:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:10] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:10] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:21] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:23] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:24] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:27] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:27] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:31] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:57] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:56:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:56:03] failed to recv data in handshakeReceive2Callback
依然不行
jessetoo
on 26 Jul 2015
@jessetoo 控制面板〉windows防火墙〉高级设置〉入站规则/出站规则〉新建规则，之后按照提示做下去就行了。还是不明白的话谷歌一下相关操作教程，数不清。
wingtsubasa
on 26 Jul 2015
win10 64bit pro 下有同样问题
ubuntu中用vmware装的win10 , 也会有如下log, chrome+ Proxy SwitchyOmega 用socks5会出现, 用http可以正常使用.
Log是复制的上面的, 和这个log一样的
[2015-07-26 12:55:26] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:27] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:27] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:28] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:31] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:55:57] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:56:01] failed to recv data in handshakeReceive2Callback
[2015-07-26 12:56:03] failed to recv data in handshakeReceive2Callback
zh0122
on 3 Aug 2015
clowwindy
on 11 Aug 2015
我的win10也这样，把迅雷卸了就好了
geyunfei
on 3 Nov 2015
妈蛋..楼上所言即是...最新版迅雷卸载就好了.....
cloudinsky
on 19 Nov 2015
不需要卸载，停用迅雷基础服务XLServicePlatform，不要自启动即可。
xFelino
on 19 Nov 2015
我又没用了..停用/卸载迅雷都没法了...
不过系统代理pac还可以.....
cloudinsky
on 20 Nov 2015
GangZhuo
on 20 Nov 2015
- 卸迅雷/停用XLSP都没用了
迅雷简直毒瘤
fisherwise
on 24 Nov 2015
我这也是最近出的这个问题，我把迅雷极速版卸载了，目前没问题，
mcdona1d
on 26 Nov 2015
就是迅雷这逼！今天下午升级迅雷，然后就出问题了，我还以为gfw终于出必杀了
firedent
on 29 Nov 2015
卸载迅雷，ok了。
earthday
on 8 Dec 2015
win10 64bit 企业版，卸载迅雷极速版，关闭防火墙，然后一直没断过线！
Atenze
on 4 Jan 2016
同win10 64bit 企业版，迅雷毒瘤
renzhn
on 16 Feb 2016
迅雷已经在2016年01月份发布的版本中修正了该问题：http://yangtai.xunlei.com/?p=10120
请尝试更新迅雷然后再试。
chenshaoju
on 16 Feb 2016
@jessetoo 我的问题日志和你一样 ，也关闭设置了防火墙允许，依然没效果，搬瓦工VPS,请问你有解决么，卸载了迅雷也没用
breeze1988
on 8 Apr 2016
我这里去掉网卡的IPV6协议后正常。
realgz
on 19 May 2016
迅雷7.9.43版本主要修正了与SS的兼容性问题，你们懂的。。。
可怜的迅雷……
awguo
on 28 May 2016
中文 win10 64bit / 无迅雷/没有杀毒软件/关闭了内置防火墙
一样的服务器配置墙外的主机连接服务器OK的/客户端版本是 win7版
ss版本: shadowsocks-win-dotnet4.0-2.5.2 /
[2016-10-08 16:47:10] Shadowsocks started
[2016-10-08 16:50:33] Shadowsocks started
(要在线更新PAC的时候，报以下错)
[2016-10-08 16:50:48] System.Reflection.TargetInvocationException: 操作过程中出现异常，结果无效。 有关异常的详细信息，请查看 InnerException。 ---> System.Net.WebException: 远程服务器返回错误: (404) 未找到。
在 System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
在 System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
在 System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- 内部异常堆栈跟踪的结尾 ---
在 System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
在 Shadowsocks.Controller.GFWListUpdater.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
liguangxun
on 8 Oct 2016
请使用最新版的SS。
chenshaoju
on 8 Oct 2016
@chenshaoju 谢谢
liguangxun
on 9 Oct 2016
看来这个问题无解啊~~~
jillojill
on 9 Oct 2016
@jillojill 按上面@chenshaoju 说的，使用最新版可能是可以吧
同一个版本再墙内和墙外结果好像是不一样的
liguangxun
on 9 Oct 2016
用的是最新版本
Sent from my Samsung device
-------- Original message --------
From: liguangxun [email protected]
Date: 2016/10/09 11:12 (GMT+08:00)
To: shadowsocks/shadowsocks-windows [email protected]
Cc: jill [email protected], Mention [email protected]
Subject: Re: [shadowsocks/shadowsocks-windows] Win7 64位ss无法连接问题 (#234)
@jillojill 按上面@chenshaoju 说的，使用最新版可能是可以吧
同一个版本再墙内和墙外结果好像是不一样的
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/shadowsocks/shadowsocks-windows","title":"shadowsocks/shadowsocks-windows","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/shadowsocks/shadowsocks-windows"}},"updates":{"snippets":[{"icon":"PERSON","message":"@liguangxun in #234: @jillojill 按上面@chenshaoju 说的，使用最新版可能是可以吧rn同一个版本再墙内和墙外结果好像是不一样的"}],"action":{"name":"View Issue","url":"https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-252461650"}}}
jillojill
on 9 Oct 2016
开始-->搜索 防火墙-->添加入站、出站规则：将程序shadowsocks.exe和ss_polipo.exe设置为全部允许通过
beckyxu
on 11 Oct 2017
Related issues
happybear88
·
3Comments
lmshao
·
4Comments
imba-tjd
·
3Comments
venusbahar
·
3Comments
xmha97
·
3Comments
Most helpful comment
请使用最新版的SS。