New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SwitchyOmega+Chrome+Win10 环境下 SOCKS5 协议问题(影响 Shadowsocks) #557

Closed
zzfnuaa opened this Issue Aug 12, 2015 · 126 comments

Comments

Projects
None yet
@zzfnuaa

zzfnuaa commented Aug 12, 2015

最近升级到win10后SwitchyOmega+SS翻墙不稳定了,经常网页打不开。一开始认为是ss的问题,后来在SS论坛看到该帖shadowsocks/shadowsocks-windows#247 (请仔细看下这个帖子)。目前在SwitchyOmega中选择系统代理,配合ss,翻墙正常。是哪出问题了,请指导,谢谢!

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 15, 2015

Owner

请先读我

以下内容为 @FelisCatus 在问题解决后追加,总结了问题、原因和解决方案:

长话短说: 使用 Shadowsocks 的用户如果遇到 Chrome + Windows 10 环境下 SOCKS5 不稳定的问题, 请在代理设置中换成 HTTP 代理协议。 原因已经确定,是迅雷组件修改系统连接参数所致,卸载迅雷并重启也能修复。此问题与 SwitchyOmega 无关,其他代理设置软件或者手动设置代理也会导致 Chrome 发生此问题。

或者, 请升级迅雷到版本 7.9.43 以上。 关于该版本迅雷的说明见此,迅雷官方声称修正了此问题。

以下为整个发现问题到讨论到解决的全过程,可供大家参考。接近讨论最下方有一些其他的解决方案(禁用迅雷组件或者修改参数等),也许能帮上您的忙。 如果某种解决方法有用,请点击评论右上角笑脸按钮,然后点个赞 👍 来表达感谢。请勿回复“我也是!”或者“+1”等无意义内容,否则参与讨论的所有人都会被邮件轰炸。

Owner

FelisCatus commented Aug 15, 2015

请先读我

以下内容为 @FelisCatus 在问题解决后追加,总结了问题、原因和解决方案:

长话短说: 使用 Shadowsocks 的用户如果遇到 Chrome + Windows 10 环境下 SOCKS5 不稳定的问题, 请在代理设置中换成 HTTP 代理协议。 原因已经确定,是迅雷组件修改系统连接参数所致,卸载迅雷并重启也能修复。此问题与 SwitchyOmega 无关,其他代理设置软件或者手动设置代理也会导致 Chrome 发生此问题。

或者, 请升级迅雷到版本 7.9.43 以上。 关于该版本迅雷的说明见此,迅雷官方声称修正了此问题。

以下为整个发现问题到讨论到解决的全过程,可供大家参考。接近讨论最下方有一些其他的解决方案(禁用迅雷组件或者修改参数等),也许能帮上您的忙。 如果某种解决方法有用,请点击评论右上角笑脸按钮,然后点个赞 👍 来表达感谢。请勿回复“我也是!”或者“+1”等无意义内容,否则参与讨论的所有人都会被邮件轰炸。

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 15, 2015

Owner

请打开地址chrome://net-internals/#proxy,并将页面上显示的文本粘贴到这里。我看一下是否是代理设置相关的问题。

相关信息,供各位参考:

  • SwitchyOmega 支持的代理模式是 HTTP, HTTPS, SOCKS4, SOCKS5 共四种。出现问题的各位请先检查一下代理协议,如果错误地设置成HTTPS或SOCKS4了,请改为SOCKS5。
    • 此外,ShadowSocks 也支持 HTTP 方式, 可以试试看切换到 HTTP。 有不少人反馈HTTP方式仍然可以正常工作。
  • SwitchyOmega 最近并未更新代理设置相关的内容,不太像是代码问题。关于这一点,按照上述方法确认一下实际有效的代理设置就知道了。
  • 根据用户反馈 SwitchySharp 也有类似问题,猜想所有设置代理的扩展均会有这种情况,甚至命令行参数设置的代理也会有这种情况。
    • 然而有用户反馈使用系统代理就没有问题,暂时还不清楚原因。各位可以试试看使用系统代理,然后再确认chrome://net-internals/#proxy页面上的内容,就知道有何差异。
    • 有条件的话各位也可以试试看命令行参数或者其他代理设置扩展,看看问题是否存在,这样对定位问题很有帮助。
  • 目前我比较怀疑是 Chrome 的网络底层实现有所更新,或者 Windows 10 的协议实现与之前不同,甚至是打的安全补丁导致协议实现出现差异。
    • 之前有用户在不同环境测试过,似乎只有 Windows 10 操作系统有此问题。
    • 更新:有用户提出了一个和Windows协议实现有关的解决方案,暂时未证实是否有效,但这加重了对于Windows协议问题的怀疑。
    • 我自己在 Linux 4.0.1 内核的系统上无法复现此问题。
    • 不妨试试看去 Chromium 项目提交一些报告,并且说明一下情况,或者附带一些 wireshark 等信息,看看那边是否能发现问题。如果真的是最近代码修改导致的话,那边也可以注意到。

以上这些,希望有用。因为这次我自己没有遇到此问题,也无法复现,且我自己对于网络协议细节了解比较少,所以没办法直接定位或者解决问题。遇到问题的各位可以先说明一下自己的浏览器版本,按照上面的说明,多提供一些信息,看看众人的智慧能否解决。

Owner

FelisCatus commented Aug 15, 2015

请打开地址chrome://net-internals/#proxy,并将页面上显示的文本粘贴到这里。我看一下是否是代理设置相关的问题。

相关信息,供各位参考:

  • SwitchyOmega 支持的代理模式是 HTTP, HTTPS, SOCKS4, SOCKS5 共四种。出现问题的各位请先检查一下代理协议,如果错误地设置成HTTPS或SOCKS4了,请改为SOCKS5。
    • 此外,ShadowSocks 也支持 HTTP 方式, 可以试试看切换到 HTTP。 有不少人反馈HTTP方式仍然可以正常工作。
  • SwitchyOmega 最近并未更新代理设置相关的内容,不太像是代码问题。关于这一点,按照上述方法确认一下实际有效的代理设置就知道了。
  • 根据用户反馈 SwitchySharp 也有类似问题,猜想所有设置代理的扩展均会有这种情况,甚至命令行参数设置的代理也会有这种情况。
    • 然而有用户反馈使用系统代理就没有问题,暂时还不清楚原因。各位可以试试看使用系统代理,然后再确认chrome://net-internals/#proxy页面上的内容,就知道有何差异。
    • 有条件的话各位也可以试试看命令行参数或者其他代理设置扩展,看看问题是否存在,这样对定位问题很有帮助。
  • 目前我比较怀疑是 Chrome 的网络底层实现有所更新,或者 Windows 10 的协议实现与之前不同,甚至是打的安全补丁导致协议实现出现差异。
    • 之前有用户在不同环境测试过,似乎只有 Windows 10 操作系统有此问题。
    • 更新:有用户提出了一个和Windows协议实现有关的解决方案,暂时未证实是否有效,但这加重了对于Windows协议问题的怀疑。
    • 我自己在 Linux 4.0.1 内核的系统上无法复现此问题。
    • 不妨试试看去 Chromium 项目提交一些报告,并且说明一下情况,或者附带一些 wireshark 等信息,看看那边是否能发现问题。如果真的是最近代码修改导致的话,那边也可以注意到。

以上这些,希望有用。因为这次我自己没有遇到此问题,也无法复现,且我自己对于网络协议细节了解比较少,所以没办法直接定位或者解决问题。遇到问题的各位可以先说明一下自己的浏览器版本,按照上面的说明,多提供一些信息,看看众人的智慧能否解决。

@FelisCatus FelisCatus changed the title from win10 X64 chrome 44.0.2403.130 m 出现异常情况 to SwitchyOmega+Chrome+Win10 环境下 SOCKS5 协议问题(影响 Shadowsocks) Aug 15, 2015

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 15, 2015

@FelisCatus Effective proxy settings

PAC script: data:application/x-ns-proxy-autoconfig;base64,LypPbWVnYVByb2ZpbGUqInNzLWF1dG8iKjE0ZjFiYmMzNWI1Ki92YXIgRm
整个太长了,超过规定的字数不让发,因此就复制了开始的这一段。另外,我QQ739073061,方便的话加下我,这样沟通更方便快捷。谢谢你

zzfnuaa commented Aug 15, 2015

@FelisCatus Effective proxy settings

PAC script: data:application/x-ns-proxy-autoconfig;base64,LypPbWVnYVByb2ZpbGUqInNzLWF1dG8iKjE0ZjFiYmMzNWI1Ki92YXIgRm
整个太长了,超过规定的字数不让发,因此就复制了开始的这一段。另外,我QQ739073061,方便的话加下我,这样沟通更方便快捷。谢谢你

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 15, 2015

@FelisCatus 此外,当前系统是win10 X64,chrome是Version 44.0.2403.155 m,附上我ss的部分日志:
[2015-08-15 21:07:40] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:15:08] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:16:07] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:17:33] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:19:21] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:20:03] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:29:39] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:47:46] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:49] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:47:49] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalBind(EndPoint localEP)
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-15 21:47:49] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:51:40] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:51:40] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:20] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:23] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:28] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:52:30] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:52:36] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:36] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:39] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:39] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:53:36] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:55:08] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:55:11] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)

zzfnuaa commented Aug 15, 2015

@FelisCatus 此外,当前系统是win10 X64,chrome是Version 44.0.2403.155 m,附上我ss的部分日志:
[2015-08-15 21:07:40] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:15:08] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:16:07] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:17:33] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:19:21] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:20:03] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:29:39] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:47:46] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:49] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:47:49] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalBind(EndPoint localEP)
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-15 21:47:49] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:47:52] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:51:40] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:51:40] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:20] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:23] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:28] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:52:30] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:52:36] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:36] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:52:39] Y站- DO San Francisco2 (104.236..8:5_90) timed out
[2015-08-15 21:52:39] Y站- DO San Francisco2 (104.236.
.8:5_90) timed out
[2015-08-15 21:53:36] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:55:08] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-15 21:55:11] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 16, 2015

Owner

@zzfnuaa 自动切换模式的设置实在是太长了,而且用于测试代理很不方便。建议直接选中 shadowsocks 所用的那个情景模式,这样可以全局应用代理,然后试试看问题是否仍然存在。如果是的话,请再次检查一下chrome://net-internals/#proxy页面的内容。麻烦您了。

Owner

FelisCatus commented Aug 16, 2015

@zzfnuaa 自动切换模式的设置实在是太长了,而且用于测试代理很不方便。建议直接选中 shadowsocks 所用的那个情景模式,这样可以全局应用代理,然后试试看问题是否仍然存在。如果是的话,请再次检查一下chrome://net-internals/#proxy页面的内容。麻烦您了。

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 16, 2015

@FelisCatus 您太客气了,你帮我解决问题,是我麻烦你了,谢谢!刚才使用的时候能打开youtube,这几天的使用过程中无法翻墙的情况时不时出现。内容如下:
Effective proxy settings

Proxy server for everything else: socks5://127.0.0.1:1080
Bypass list:
127.0.0.1
[::1]
localhost

同时间ss的日志如下:
[2015-08-16 15:46:23] Shadowsocks started
[2015-08-16 15:47:03] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:47:07] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:47:10] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:20] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:20] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-16 15:50:23] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:23] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:25] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:39] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:39] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalBind(EndPoint localEP)
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-16 15:50:42] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:42] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:31] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:36] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:39] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:41] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:52:04] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)

zzfnuaa commented Aug 16, 2015

@FelisCatus 您太客气了,你帮我解决问题,是我麻烦你了,谢谢!刚才使用的时候能打开youtube,这几天的使用过程中无法翻墙的情况时不时出现。内容如下:
Effective proxy settings

Proxy server for everything else: socks5://127.0.0.1:1080
Bypass list:
127.0.0.1
[::1]
localhost

同时间ss的日志如下:
[2015-08-16 15:46:23] Shadowsocks started
[2015-08-16 15:47:03] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:47:07] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:47:10] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:20] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:20] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-16 15:50:23] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:23] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:25] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:39] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:39] System.Net.Sockets.SocketException (0x80004005): An invalid argument was supplied
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalBind(EndPoint localEP)
at System.Net.Sockets.Socket.BeginConnectEx(EndPoint remoteEP, Boolean flowContext, AsyncCallback callback, Object state)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
at Shadowsocks.Controller.Handler.StartConnect()
[2015-08-16 15:50:42] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:50:42] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:31] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:36] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:39] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:51:41] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 15:52:04] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 16, 2015

@FelisCatus 重启电脑后,又翻不了墙了。内容如下
Effective proxy settings

Proxy server for everything else: socks5://127.0.0.1:1080
Bypass list:
127.0.0.1
[::1]
localhost

同时间的ss日志[2015-08-16 16:12:56] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:10] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-16 16:13:10] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-16 16:13:12] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:26] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:29] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:41] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:42] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:06] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:13] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:43] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:44] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:15:05] failed to recv data in handshakeReceive2Callback

zzfnuaa commented Aug 16, 2015

@FelisCatus 重启电脑后,又翻不了墙了。内容如下
Effective proxy settings

Proxy server for everything else: socks5://127.0.0.1:1080
Bypass list:
127.0.0.1
[::1]
localhost

同时间的ss日志[2015-08-16 16:12:56] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:10] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-16 16:13:10] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Shadowsocks.Controller.Handler.PipeRemoteReceiveCallback(IAsyncResult ar)
[2015-08-16 16:13:12] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:24] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:26] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:29] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:41] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:13:42] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:06] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:13] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:43] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:14:44] failed to recv data in handshakeReceive2Callback
[2015-08-16 16:15:05] failed to recv data in handshakeReceive2Callback

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 16, 2015

@FelisCatus 切换到系统代理后,youtube可以打开了,内容如下
Effective proxy settings

PAC script: http://127.0.0.1:1080/pac?t=201508161609214414
Source: SYSTEM
Original proxy settings

(1) Auto-detect
(2) PAC script: http://127.0.0.1:1080/pac?t=201508161609214414
Source: SYSTEM

同时间ss日志
[2015-08-16 16:16:24] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:16:59] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:05] Y站- DO San Francisco2 (104.236..8:51490) timed out

zzfnuaa commented Aug 16, 2015

@FelisCatus 切换到系统代理后,youtube可以打开了,内容如下
Effective proxy settings

PAC script: http://127.0.0.1:1080/pac?t=201508161609214414
Source: SYSTEM
Original proxy settings

(1) Auto-detect
(2) PAC script: http://127.0.0.1:1080/pac?t=201508161609214414
Source: SYSTEM

同时间ss日志
[2015-08-16 16:16:24] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:16:59] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:02] Y站- DO San Francisco2 (104.236..8:51490) timed out
[2015-08-16 16:17:05] Y站- DO San Francisco2 (104.236..8:51490) timed out

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 17, 2015

Owner

@zzfnuaa 看看PAC里的内容(shadowsock运行的时候,直接点那个连接打开),使用的代理协议是SOCKS5吗?

此外,还可以试试看创建一个PAC情景模式,URL填写http://127.0.0.1:1080/pac?t=201508161609214414之类的。这样效果如何?理论上来说,这样就会直接使用shadowsocks提供的PAC文件,和使用系统代理效果应该类似。

Owner

FelisCatus commented Aug 17, 2015

@zzfnuaa 看看PAC里的内容(shadowsock运行的时候,直接点那个连接打开),使用的代理协议是SOCKS5吗?

此外,还可以试试看创建一个PAC情景模式,URL填写http://127.0.0.1:1080/pac?t=201508161609214414之类的。这样效果如何?理论上来说,这样就会直接使用shadowsocks提供的PAC文件,和使用系统代理效果应该类似。

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 17, 2015

@FelisCatus PAC里的内容如下

// Generated by gfwlist2pac in precise mode
// https://github.com/clowwindy/gfwlist2pac

var proxy = "PROXY 127.0.0.1:1080;";

// ...

zzfnuaa commented Aug 17, 2015

@FelisCatus PAC里的内容如下

// Generated by gfwlist2pac in precise mode
// https://github.com/clowwindy/gfwlist2pac

var proxy = "PROXY 127.0.0.1:1080;";

// ...
@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 17, 2015

@FelisCatus 附上我的SwitchyOmega设置
1
2

zzfnuaa commented Aug 17, 2015

@FelisCatus 附上我的SwitchyOmega设置
1
2

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 17, 2015

Owner

@zzfnuaa 可以看到shadowsocks中生成的是PROXY 127.0.0.1:1080;,用的是HTTP协议,而非 SOCKS5 协议。

如果使用 SwitchyOmega 的话,可以将设置也改成 HTTP 协议,就应该能正常使用了。

至于为什么SOCKS5不能用嘛……至少SwitchyOmega的嫌疑可以排除了,接下去我觉得就应该怀疑Chrome或者Windows10了。

Owner

FelisCatus commented Aug 17, 2015

@zzfnuaa 可以看到shadowsocks中生成的是PROXY 127.0.0.1:1080;,用的是HTTP协议,而非 SOCKS5 协议。

如果使用 SwitchyOmega 的话,可以将设置也改成 HTTP 协议,就应该能正常使用了。

至于为什么SOCKS5不能用嘛……至少SwitchyOmega的嫌疑可以排除了,接下去我觉得就应该怀疑Chrome或者Windows10了。

@langxuan

This comment has been minimized.

Show comment
Hide comment
@langxuan

langxuan Aug 17, 2015

在shadowsocks client不启用系统代理的情况下,无论使用SwitchyOmega、SwitchySharp、firefox直接设置socks5代理都无法正常使用,谨慎怀疑是win10作大死啦┑( ̄Д  ̄)┍

langxuan commented Aug 17, 2015

在shadowsocks client不启用系统代理的情况下,无论使用SwitchyOmega、SwitchySharp、firefox直接设置socks5代理都无法正常使用,谨慎怀疑是win10作大死啦┑( ̄Д  ̄)┍

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 17, 2015

Owner

@langxuan 等等, Firefox 也不行?最好到shadowsocks那边相关的issue说一下这种情况,然后再抓点包什么的,看看是否能有帮助。

Owner

FelisCatus commented Aug 17, 2015

@langxuan 等等, Firefox 也不行?最好到shadowsocks那边相关的issue说一下这种情况,然后再抓点包什么的,看看是否能有帮助。

@Tback1

This comment has been minimized.

Show comment
Hide comment
@Tback1

Tback1 Aug 19, 2015

@zzfnuaa 建议你看看你已经更新了新的累计补丁没,尽快更新一下试试.我的系统环境和你类似,刚安装的时候的确有这个问题,不过更新之后就没出现了,

@FelisCatus 这个问题应该是shadowsocks新版使用4.0的.Net框架后因为套接字协议本身字长发生变化造成的,不过在win10 64位 第三个集合补丁之后,似乎这个兼容性问题已经解决

Tback1 commented Aug 19, 2015

@zzfnuaa 建议你看看你已经更新了新的累计补丁没,尽快更新一下试试.我的系统环境和你类似,刚安装的时候的确有这个问题,不过更新之后就没出现了,

@FelisCatus 这个问题应该是shadowsocks新版使用4.0的.Net框架后因为套接字协议本身字长发生变化造成的,不过在win10 64位 第三个集合补丁之后,似乎这个兼容性问题已经解决

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 19, 2015

@FelisCatus 我使用wireshark v1.12.7抓了些数据,上传到百度云,http://pan.baidu.com/s/1eQpoHUE,http://pan.baidu.com/s/1dDlmU21。系统win10 pro X64 英文版,chrome 44.0.2403.155 m,shadowsocks 2.5.5。

zzfnuaa commented Aug 19, 2015

@FelisCatus 我使用wireshark v1.12.7抓了些数据,上传到百度云,http://pan.baidu.com/s/1eQpoHUE,http://pan.baidu.com/s/1dDlmU21。系统win10 pro X64 英文版,chrome 44.0.2403.155 m,shadowsocks 2.5.5。

@zzfnuaa

This comment has been minimized.

Show comment
Hide comment
@zzfnuaa

zzfnuaa Aug 19, 2015

@Tback1 我今天上午安装了最新的KB3081444,但是还是有这问题。。。。

zzfnuaa commented Aug 19, 2015

@Tback1 我今天上午安装了最新的KB3081444,但是还是有这问题。。。。

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 20, 2015

Owner

那边 Issue 已经关掉了,具体可以看这里的说明{链接已经失效!}。如果您的情况和之前的结论不相符,建议去那边汇报并提供相关信息。
由于暂时的结论是这并不是一个问题,所以我这边也先关掉好了。关闭Issue不等于关闭评论,只是标记此问题已经解决/不存在而已。如果有任何内容仍然可以继续回复讨论,欢迎继续对协议细节进行探讨。

Owner

FelisCatus commented Aug 20, 2015

那边 Issue 已经关掉了,具体可以看这里的说明{链接已经失效!}。如果您的情况和之前的结论不相符,建议去那边汇报并提供相关信息。
由于暂时的结论是这并不是一个问题,所以我这边也先关掉好了。关闭Issue不等于关闭评论,只是标记此问题已经解决/不存在而已。如果有任何内容仍然可以继续回复讨论,欢迎继续对协议细节进行探讨。

@FelisCatus FelisCatus closed this Aug 20, 2015

@oe77

This comment has been minimized.

Show comment
Hide comment
@oe77

oe77 Aug 25, 2015

xshot-0015
我本身用的是Shadowsocks-QT5+win10+SwitchyOmega+chome+SOCKS5,能正常使用,但今天用了shadowsocks2.5.6+win10+SwitchyOmega+chome+SOCKS5,就不能正常使用,改用http虽然能用但比较慢,无奈之下再重装一下系统,换回原来的Shadowsocks-QT5+win10+SwitchyOmega+chome+SOCKS5,正常使用中.....

oe77 commented Aug 25, 2015

xshot-0015
我本身用的是Shadowsocks-QT5+win10+SwitchyOmega+chome+SOCKS5,能正常使用,但今天用了shadowsocks2.5.6+win10+SwitchyOmega+chome+SOCKS5,就不能正常使用,改用http虽然能用但比较慢,无奈之下再重装一下系统,换回原来的Shadowsocks-QT5+win10+SwitchyOmega+chome+SOCKS5,正常使用中.....

@wudimenghuan

This comment has been minimized.

Show comment
Hide comment
@wudimenghuan

wudimenghuan Aug 26, 2015

我也是同样情况,升级win10就不好使了

wudimenghuan commented Aug 26, 2015

我也是同样情况,升级win10就不好使了

@yymyyy

This comment has been minimized.

Show comment
Hide comment
@yymyyy

yymyyy Aug 27, 2015

windows10正式版刚发布就使用chrome+switchyomega+shadowsocks的方案,一直正常,今天突然发现自动切换与使用代理的方案不能正常google。因为天天使用google,所以确信昨天还是正常的。仔细看了才发现其他软件都正常,Edge上网dropbox同步都正常,然后试试使用switchyomega的系统代理,确实也是正常,如楼上所说。然后上网搜索才发现这里有人讨论。水平有限只能这样反馈一下了。

yymyyy commented Aug 27, 2015

windows10正式版刚发布就使用chrome+switchyomega+shadowsocks的方案,一直正常,今天突然发现自动切换与使用代理的方案不能正常google。因为天天使用google,所以确信昨天还是正常的。仔细看了才发现其他软件都正常,Edge上网dropbox同步都正常,然后试试使用switchyomega的系统代理,确实也是正常,如楼上所说。然后上网搜索才发现这里有人讨论。水平有限只能这样反馈一下了。

@wudimenghuan

This comment has been minimized.

Show comment
Hide comment
@wudimenghuan

wudimenghuan Aug 27, 2015

我发现好像是升级win10之后是有一些问题的,但是在另一个电脑上是正常的,区别好像是因为另一个电脑重置过。推测是重置过或者全新安装的win10是没问题的

wudimenghuan commented Aug 27, 2015

我发现好像是升级win10之后是有一些问题的,但是在另一个电脑上是正常的,区别好像是因为另一个电脑重置过。推测是重置过或者全新安装的win10是没问题的

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Aug 27, 2015

Owner

那边的 Issue 不在了,所以我再说一下之前的讨论结果。

长话短说: 使用 Shadowsocks 的用户如果遇到 Chrome + Windows 10 环境下 SOCKS5 不稳定的问题, 请在代理设置中换成 HTTP 代理协议。

有些用户反映SOCKS5不稳定或者没法用,也有用户没有遇到任何问题的。至于是为什么,我也不知道。SS那边之前的讨论结果是错误信息不影响使用,但也许是其他问题呢?总之暂时而言用 HTTP 比较保险。

Owner

FelisCatus commented Aug 27, 2015

那边的 Issue 不在了,所以我再说一下之前的讨论结果。

长话短说: 使用 Shadowsocks 的用户如果遇到 Chrome + Windows 10 环境下 SOCKS5 不稳定的问题, 请在代理设置中换成 HTTP 代理协议。

有些用户反映SOCKS5不稳定或者没法用,也有用户没有遇到任何问题的。至于是为什么,我也不知道。SS那边之前的讨论结果是错误信息不影响使用,但也许是其他问题呢?总之暂时而言用 HTTP 比较保险。

@celeron533

This comment has been minimized.

Show comment
Hide comment
@celeron533

celeron533 Aug 28, 2015

Contributor

协议换成http应该能解决问题。在shadowsocks Issue board 关闭之前,clowwindy发现最新版chrome在socks5行为上有变化,导致提前关闭连接。采用http方式后,ss先把http传送到ss_polipo翻译成socks5,然后ss重新把socks5加密收发。

Contributor

celeron533 commented Aug 28, 2015

协议换成http应该能解决问题。在shadowsocks Issue board 关闭之前,clowwindy发现最新版chrome在socks5行为上有变化,导致提前关闭连接。采用http方式后,ss先把http传送到ss_polipo翻译成socks5,然后ss重新把socks5加密收发。

@webbbbb

This comment has been minimized.

Show comment
Hide comment
@webbbbb

webbbbb Apr 11, 2016

迅雷卸载掉就好了!

webbbbb commented Apr 11, 2016

迅雷卸载掉就好了!

@luc9

This comment has been minimized.

Show comment
Hide comment
@luc9

luc9 Apr 28, 2016

关闭迅雷浏览器监视即可解决(迅雷极速版下测试可用)。

luc9 commented Apr 28, 2016

关闭迅雷浏览器监视即可解决(迅雷极速版下测试可用)。

@FelisCatus

This comment has been minimized.

Show comment
Hide comment
@FelisCatus

FelisCatus Apr 28, 2016

Owner

关于此问题的总结已经更新在沙发位置的评论内,如果还搞不清状况可以前往阅读。

如果某种解决方法有用,请点击评论右上角笑脸按钮,然后点个赞 👍 来表达感谢。请勿回复“我也是!”或者“+1”等无意义内容,否则参与讨论的所有人都会被邮件轰炸。

在下方发表评论前,请确定您提出了一种新的解决方案、新的问题或者新的信息,为这个 Issue 的讨论创造了价值。尤其注意不要抱怨某公司或者某产品,这没有任何意义。

Owner

FelisCatus commented Apr 28, 2016

关于此问题的总结已经更新在沙发位置的评论内,如果还搞不清状况可以前往阅读。

如果某种解决方法有用,请点击评论右上角笑脸按钮,然后点个赞 👍 来表达感谢。请勿回复“我也是!”或者“+1”等无意义内容,否则参与讨论的所有人都会被邮件轰炸。

在下方发表评论前,请确定您提出了一种新的解决方案、新的问题或者新的信息,为这个 Issue 的讨论创造了价值。尤其注意不要抱怨某公司或者某产品,这没有任何意义。

@Phincle

This comment has been minimized.

Show comment
Hide comment
@Phincle

Phincle May 11, 2016

迅雷极速版的问题,换成迅雷7.9.43.5054就好了。

Phincle commented May 11, 2016

迅雷极速版的问题,换成迅雷7.9.43.5054就好了。

@bugparty

This comment has been minimized.

Show comment
Hide comment
@bugparty

bugparty May 11, 2016

快把这个问题close吧

On Wed, May 11, 2016 at 9:42 AM, Phincle notifications@github.com wrote:

迅雷极速版的问题,换成迅雷7.9.43.5054就好了。


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#557 (comment)

bugparty commented May 11, 2016

快把这个问题close吧

On Wed, May 11, 2016 at 9:42 AM, Phincle notifications@github.com wrote:

迅雷极速版的问题,换成迅雷7.9.43.5054就好了。


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#557 (comment)

@pickView

This comment has been minimized.

Show comment
Hide comment
@pickView

pickView Jun 10, 2016

@FelisCatus 我的ss3.0不能用了,装了下迅雷极速版,就不能用了,把迅雷删掉还是不行,求助

pickView commented Jun 10, 2016

@FelisCatus 我的ss3.0不能用了,装了下迅雷极速版,就不能用了,把迅雷删掉还是不行,求助

@pickView

This comment has been minimized.

Show comment
Hide comment
@pickView

pickView Jun 10, 2016

ss瘫痪了,报错:[2016-06-10 23:52:53] System.Net.Sockets.SocketException (0x80004005): 系统检测到在一个调用中尝试使用指针参数时的无效指针地址。
在 System.Net.Sockets.Socket.get_RemoteEndPoint()
在 Shadowsocks.Controller.TCPHandler.ConnectCallback(IAsyncResult ar)

pickView commented Jun 10, 2016

ss瘫痪了,报错:[2016-06-10 23:52:53] System.Net.Sockets.SocketException (0x80004005): 系统检测到在一个调用中尝试使用指针参数时的无效指针地址。
在 System.Net.Sockets.Socket.get_RemoteEndPoint()
在 Shadowsocks.Controller.TCPHandler.ConnectCallback(IAsyncResult ar)

@otherfish

This comment has been minimized.

Show comment
Hide comment
@otherfish

otherfish Jun 10, 2016

使用迅雷极速版,仍然会有这个问题禁用服务可破,但是每次重新运行迅雷要注意还是有可能上不了外网。

qq 20160611000615

otherfish commented Jun 10, 2016

使用迅雷极速版,仍然会有这个问题禁用服务可破,但是每次重新运行迅雷要注意还是有可能上不了外网。

qq 20160611000615

@wanglongbiao

This comment has been minimized.

Show comment
Hide comment
@wanglongbiao

wanglongbiao Jul 7, 2016

卸载迅雷极速版,问题解决。非常感谢。

wanglongbiao commented Jul 7, 2016

卸载迅雷极速版,问题解决。非常感谢。

@wikilike7

This comment has been minimized.

Show comment
Hide comment
@wikilike7

wikilike7 Jul 22, 2016

  1. 果然是将socket5改成HTTP就解决
  2. 有没有更好的下载工具介绍呢?

wikilike7 commented Jul 22, 2016

  1. 果然是将socket5改成HTTP就解决
  2. 有没有更好的下载工具介绍呢?
@jen-ping

This comment has been minimized.

Show comment
Hide comment
@jen-ping

jen-ping Oct 5, 2016

果然是将switchyomega的socket5改成HTTP就解决!!
经过重新安装chrome,依旧不行。才看到此方法!谢谢!!

jen-ping commented Oct 5, 2016

果然是将switchyomega的socket5改成HTTP就解决!!
经过重新安装chrome,依旧不行。才看到此方法!谢谢!!

@sherppard

This comment has been minimized.

Show comment
Hide comment
@sherppard

sherppard Mar 2, 2017

牛逼,解决了我的问题。

sherppard commented Mar 2, 2017

牛逼,解决了我的问题。

@Aisuko

This comment has been minimized.

Show comment
Hide comment
@Aisuko

Aisuko Mar 25, 2017

coursera始终不行,我觉得应该是速度问题,可以配置gae+shadowsocks用switchyomega代理,目前我是这么解决的。

Aisuko commented Mar 25, 2017

coursera始终不行,我觉得应该是速度问题,可以配置gae+shadowsocks用switchyomega代理,目前我是这么解决的。

@shenmijiabing

This comment has been minimized.

Show comment
Hide comment
@shenmijiabing

shenmijiabing Jan 2, 2018

linuxmint 出现这个问题了。没办法解决。选了socks5 还是一样。以前挺顺利的,这次不知道为什么会这样

shenmijiabing commented Jan 2, 2018

linuxmint 出现这个问题了。没办法解决。选了socks5 还是一样。以前挺顺利的,这次不知道为什么会这样

@luzong

This comment has been minimized.

Show comment
Hide comment
@luzong

luzong Jul 14, 2018

终于懂了,我的ssr问题一个多月了,一直超时后来能显示成功连接,别的电脑也能连接,怎么配置就是不行,系统重装都试了。原来迅雷搞得鬼。卸载迅雷本地配置1080搞定终于可以看YouTube了。感谢~~~

luzong commented Jul 14, 2018

终于懂了,我的ssr问题一个多月了,一直超时后来能显示成功连接,别的电脑也能连接,怎么配置就是不行,系统重装都试了。原来迅雷搞得鬼。卸载迅雷本地配置1080搞定终于可以看YouTube了。感谢~~~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment