Shadowsocks-windows: 加了obfs也不通

Created on 16 Feb 2019 · 22Comments · Source: shadowsocks/shadowsocks-windows

[2019-02-16 18:54:31] connect to api.github.com:443
[2019-02-16 18:54:31] Socket connected to ss server: 45.32.81.124:12998
[2019-02-16 18:54:34] connect to apis.google.com:443
[2019-02-16 18:54:34] connect to www.gstatic.com:443
[2019-02-16 18:54:34] Socket connected to ss server: 45.32.81.124:12998
[2019-02-16 18:54:34] Socket connected to ss server: 45.32.81.124:12998
[2019-02-16 18:54:34] connect to www.google.com:443
[2019-02-16 18:54:34] Socket connected to ss server: 45.32.81.124:12998
[2019-02-16 18:55:09] connect to api.github.com:443
[2019-02-16 18:55:09] Socket connected to ss server: 45.32.81.124:12998
[2019-02-16 18:55:49] 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()
在 Shadowsocks.Controller.UpdateChecker.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)

Source

litianyuhehe

Most helpful comment

请不要留私人联系方式，因为无法保证联系你的人就是你所期望的那个人。

一般是写入 shadowsocks-libev 的配置文件 config.json 中的一行参数，给你参考：

{
    "server":"0.0.0.0",
    "server_port":443,
    "local_port":10800,
    "password":"pBpAXnvH2JhT",
    "timeout":20,
    "method":"aes-256-gcm",
    "plugin":"obfs-server",
    "plugin_opts":"obfs=tls;failover=104.193.88.77:443"
}

客户端的话，在插件程序中指定插件的路径后，在插件选项中指定参数：

obfs=tls;obfs-host=www.baidu.com

chenshaoju on 17 Feb 2019

👀5 👍3

All 22 comments

C:\Users\Administrator>tcping -t 45.32.81.124 12998

* Pinging continuously. Press control-c to stop *

Probing 45.32.81.124:12998/tcp - Port is open - time=246.079ms
Probing 45.32.81.124:12998/tcp - Port is open - time=246.777ms
Probing 45.32.81.124:12998/tcp - Port is open - time=231.456ms
Probing 45.32.81.124:12998/tcp - Port is open - time=232.785ms
Probing 45.32.81.124:12998/tcp - Port is open - time=225.498ms
Probing 45.32.81.124:12998/tcp - Port is open - time=209.684ms
Probing 45.32.81.124:12998/tcp - Port is open - time=228.593ms
Probing 45.32.81.124:12998/tcp - Port is open - time=207.660ms
Probing 45.32.81.124:12998/tcp - Port is open - time=248.650ms
Probing 45.32.81.124:12998/tcp - Port is open - time=226.471ms
Probing 45.32.81.124:12998/tcp - Port is open - time=213.558ms
Probing 45.32.81.124:12998/tcp - Port is open - time=207.557ms
Control-C

Ping statistics for 45.32.81.124:12998
12 probes sent.
12 successful, 0 failed. (0.00% fail)
Approximate trip times in milli-seconds:
Minimum = 207.557ms, Maximum = 248.650ms, Average = 227.064ms
tcp协议也是通的