shadowsocks / shadowsocks-windows

A C# port of shadowsocks
Other
58.29k stars 16.4k forks source link

Win7 64位ss无法连接问题 #234

Closed jessetoo closed 9 years ago

jessetoo commented 9 years ago

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笔记本上就可以连接,求问大大怎么解决,求帮助!!!

clowwindy commented 9 years ago

可以把配置文件从好的机器上拷过去覆盖再测一下。

jessetoo commented 9 years ago

@clowwindy 经过测试,没有用

wingtsubasa commented 9 years ago

[误报,已解决] 同样无法连接,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版本就没有问题。

clowwindy commented 9 years ago

可以试试一些老版本 https://sourceforge.net/projects/shadowsocksgui/files/dist/

如果用老版本也没有用,应该还是防火墙或者网络问题。

wingtsubasa commented 9 years ago

现在已回退到2.4版本,正常使用中。 2015年7月26日 上午9:13于 "clowwindy" notifications@github.com写道:

可以试试一些老版本 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 .

clowwindy commented 9 years ago

@wingtsubasa 2.5 是如何设置的呢?有几个服务器?有没有设置负载均衡或者高可用?

clowwindy commented 9 years ago

能否把完整的配置文件贴出来看看?IP 可以打码。

jessetoo commented 9 years ago

@clowwindy 大大,我换了好多客户端,依然无解,还是会自动连接到那个fe80::5930:665f:1428:d786%11:8388,经排查这是ipv6地址……而同样的错误,一位网友也出现过 http://bbs.byr.cn/#!article/Linux/148334

jessetoo commented 9 years ago

@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}

chenping2015 commented 9 years ago

👓[image: 内嵌图片 1]

2015-07-26 11:17 GMT+08:00 clowwindy notifications@github.com:

能否把完整的配置文件贴出来看看?IP 可以打码。

— Reply to this email directly or view it on GitHub https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-124936215 .

clowwindy commented 9 years ago

如果在菜单里再手动选一下服务器,或者选高可用呢?

wingtsubasa commented 9 years ago

@clowwindy 已排除故障,问题出在防火墙上,可执行文件及子进程加入白名单后一切正常了。由于win8使用相同防火墙但是没有出现问题,win7用之前的版本也不存在问题,所以没有往这方面想。这是误报了,抱歉!

jessetoo commented 9 years ago

@wingtsubasa 执行文件及子进怎么加入白名单?

wingtsubasa commented 9 years ago

这要看防火墙的具体设置了,各软件不同。以我用的迈克菲为例,在防火墙>程序的Internet连接,将主进程shadowsocks.exe和子进程ss_polipo.exe设置为“不保护”,即全面放行。通常友好的防火墙界面会更直白的表述为白名单,加入的进程即不受拦截。 2015年7月26日 下午12:37于 "jessetoo" notifications@github.com写道:

@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 .

jessetoo commented 9 years ago

@wingtsubasa windows7 自带的防火墙怎么设置?

clowwindy commented 9 years ago

更新到 2.5.1,再贴一下完整的日志,从更新以后的第一行开始,每一行前面有日期时间。

jessetoo commented 9 years ago

@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 依然不行

wingtsubasa commented 9 years ago

@jessetoo 控制面板〉windows防火墙〉高级设置〉入站规则/出站规则〉新建规则,之后按照提示做下去就行了。还是不明白的话谷歌一下相关操作教程,数不清。

zh0122 commented 9 years ago

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
clowwindy commented 9 years ago

https://github.com/shadowsocks/shadowsocks-windows/issues/247

geyunfei commented 8 years ago

我的win10也这样,把迅雷卸了就好了

cloudinsky commented 8 years ago

妈蛋..楼上所言即是...最新版迅雷卸载就好了.....

xFelino commented 8 years ago

不需要卸载,停用迅雷基础服务XLServicePlatform,不要自启动即可。

cloudinsky commented 8 years ago

我又没用了..停用/卸载迅雷都没法了... 不过系统代理pac还可以.....

GangZhuo commented 8 years ago

下载 https://ci.appveyor.com/project/icylogic/shadowsocks-windows-l9mwe/build/job/c5ffptxey2ole5fu/artifacts 试看看。

mylylyl commented 8 years ago
mcdona1d commented 8 years ago

我这也是最近出的这个问题,我把迅雷极速版卸载了,目前没问题,

firedent commented 8 years ago

就是迅雷这逼!今天下午升级迅雷,然后就出问题了,我还以为gfw终于出必杀了

earthday commented 8 years ago

卸载迅雷,ok了。

Atenze commented 8 years ago

win10 64bit 企业版,卸载迅雷极速版,关闭防火墙,然后一直没断过线!

j67678 commented 8 years ago

同win10 64bit 企业版,迅雷毒瘤

chenshaoju commented 8 years ago

迅雷已经在2016年01月份发布的版本中修正了该问题:http://yangtai.xunlei.com/?p=10120

请尝试更新迅雷然后再试。

breeze1988 commented 8 years ago

@jessetoo 我的问题日志和你一样 ,也关闭设置了防火墙允许,依然没效果,搬瓦工VPS,请问你有解决么,卸载了迅雷也没用

realgz commented 8 years ago

我这里去掉网卡的IPV6协议后正常。

ahbox commented 8 years ago

 迅雷7.9.43版本主要修正了与SS的兼容性问题,你们懂的。。。

可怜的迅雷……

liguangxun commented 7 years ago

中文 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)

chenshaoju commented 7 years ago

请使用最新版的SS。

liguangxun commented 7 years ago

@chenshaoju 谢谢

liujiaojill commented 7 years ago

看来这个问题无解啊~~~

liguangxun commented 7 years ago

@jillojill 按上面@chenshaoju 说的,使用最新版可能是可以吧 同一个版本再墙内和墙外结果好像是不一样的

liujiaojill commented 7 years ago

用的是最新版本

Sent from my Samsung device

-------- Original message -------- From: liguangxun notifications@github.com Date: 2016/10/09 11:12 (GMT+08:00) To: shadowsocks/shadowsocks-windows shadowsocks-windows@noreply.github.com Cc: jill liujiaojill@163.com, Mention mention@noreply.github.com 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 说的,使用最新版可能是可以吧\r\n同一个版本再墙内和墙外结果好像是不一样的"}],"action":{"name":"View Issue","url":"https://github.com/shadowsocks/shadowsocks-windows/issues/234#issuecomment-252461650"}}}

beckyxu commented 6 years ago

开始-->搜索 防火墙-->添加入站、出站规则:将程序shadowsocks.exe和ss_polipo.exe设置为全部允许通过