Useful or not, from you.
shadowsocks-windows SS with Cloak constantly stops working
  • Shadowsocks is an open source project for noneprofit. If you bought the service from a provider, please contact them. / 影梭(Shadowsocks)是一个开源非盈利项目,不提供任何托管服务。如果你是从服务提供商购买的服务,请联系他们
  • If you have questions rather than Shadowsocks Windows client, please go to / 如果你有非影梭Windows客户端相关的问题,请去 https://github.com/shadowsocks
  • Please read Wiki carefully, especially / 提问前请先阅读wiki https://github.com/shadowsocks/shadowsocks-windows/wiki/Troubleshooting.
  • Or search from Issue Board / 或在Issue Board中搜索 https://github.com/shadowsocks/shadowsocks-windows/issues?utf8=%E2%9C%93&q=is%3Aissue
  • Please answer the following questions before submission. Questions lack of details will be closed. / 请按照以下格式描述你的问题,描述不清的问题将会被关闭

Shadowsocks version / 影梭版本

Shaowsocks-libev server 3.3.0 with Cloak plugin Shadowsocks Windows client 4.1.6 with Cloak plugin

Environment(Operating system, .NET Framework, etc) / 使用环境(操作系统,.NET Framework等)

SS-Server OS : Ubuntu 18.04 LTS (GNU/Linux 4.15.0-20-generic x86_64) Local OS : Windows 7 Home

Steps you have tried / 操作步骤

Set up server and client following the offical guide.

What did you expect to see? / 期望的结果

It works without constant failure.

What did you see instead? / 实际结果

Proxy speed constantly goes down to an unbearable level or time out every few minutes.

Config and error log in detail (with all sensitive info masked) / 配置文件和日志文件(请隐去敏感信息)

[2019-07-02 20:54:32] Shadowsocks started (4.1.6)
[2019-07-02 20:55:34] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:35] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:35] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:35] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:35] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:35] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:36] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:39] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:41] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:41] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:43] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:43] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:51] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:51] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:51] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:51] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:57] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:58] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:58] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:58] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:58] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:58] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:59] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:55:59] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:02] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:02] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:03] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:03] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:03] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:04] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 20:56:04] System.ArgumentException: No server configured
   在 Shadowsocks.Controller.TCPHandler.CreateRemote()
   在 Shadowsocks.Controller.TCPHandler.StartConnect()
[2019-07-02 21:27:04] Shadowsocks started (4.1.6)
[2019-07-02 21:28:31] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49248 - PID: 4960
[2019-07-02 21:28:31] Shadowsocks started (4.1.6)
[2019-07-02 21:28:36] 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)
[2019-07-02 21:28:59] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49364 - PID: 1208
[2019-07-02 21:28:59] Shadowsocks started (4.1.6)
[2019-07-02 21:28:59] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49370 - PID: 2612
[2019-07-02 21:28:59] Shadowsocks started (4.1.6)
[2019-07-02 21:29:14] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-02 21:29:24] 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.GFWListUpdater.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
[2019-07-02 21:29:46] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49511 - PID: 5472
[2019-07-02 21:29:46] Shadowsocks started (4.1.6)
[2019-07-02 21:30:16] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49629 - PID: 4932
[2019-07-02 21:30:16] Shadowsocks started (4.1.6)
[2019-07-02 21:37:19] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50185 - PID: 5104
[2019-07-02 21:37:19] Shadowsocks started (4.1.6)
[2019-07-02 21:37:19] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50191 - PID: 4400
[2019-07-02 21:37:19] Shadowsocks started (4.1.6)
[2019-07-02 21:38:32] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50220 - PID: 3444
[2019-07-02 21:38:32] Shadowsocks started (4.1.6)
[2019-07-02 21:38:32] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50226 - PID: 3308
[2019-07-02 21:38:32] Shadowsocks started (4.1.6)
[2019-07-02 21:39:40] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50294 - PID: 6048
[2019-07-02 21:39:40] Shadowsocks started (4.1.6)
[2019-07-02 21:39:40] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50296 - PID: 4868
[2019-07-02 21:39:40] Shadowsocks started (4.1.6)
[2019-07-02 21:43:11] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50326 - PID: 5232
[2019-07-02 21:43:11] Shadowsocks started (4.1.6)
[2019-07-02 21:43:11] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50332 - PID: 5020
[2019-07-02 21:43:11] Shadowsocks started (4.1.6)
[2019-07-02 21:44:06] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50446 - PID: 5292
[2019-07-02 21:44:06] Shadowsocks started (4.1.6)
[2019-07-02 21:44:06] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50455 - PID: 4496
[2019-07-02 21:44:06] Shadowsocks started (4.1.6)
[2019-07-02 21:44:10] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50473 - PID: 224
[2019-07-02 21:44:10] Shadowsocks started (4.1.6)
[2019-07-02 21:44:11] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50475 - PID: 4864
[2019-07-02 21:44:11] Shadowsocks started (4.1.6)
[2019-07-02 21:44:12] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-02 21:46:58] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-02 21:48:11] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50694 - PID: 5588
[2019-07-02 21:48:11] Shadowsocks started (4.1.6)
[2019-07-02 21:48:11] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50701 - PID: 5424
[2019-07-02 21:48:11] Shadowsocks started (4.1.6)
[2019-07-02 21:52:32] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:50983 - PID: 4636
[2019-07-02 21:52:32] Shadowsocks started (4.1.6)
[2019-07-02 21:52:32] 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.GFWListUpdater.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
[2019-07-02 21:59:00] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-02 21:59:51] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:51378 - PID: 296
[2019-07-02 21:59:51] Shadowsocks started (4.1.6)
[2019-07-02 22:04:52] 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.GFWListUpdater.http_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e)
[2019-07-02 22:21:22] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52269 - PID: 2964
[2019-07-02 22:21:22] Shadowsocks started (4.1.6)
[2019-07-02 22:21:22] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52271 - PID: 3620
[2019-07-02 22:21:22] Shadowsocks started (4.1.6)
[2019-07-02 22:25:10] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-02 22:25:11] Detected: PAC file 'pac.txt' was created.
[2019-07-02 23:38:00] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-02 23:43:48] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54857 - PID: 6952
[2019-07-02 23:43:48] Shadowsocks started (4.1.6)
[2019-07-02 23:43:49] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54859 - PID: 5216
[2019-07-02 23:43:49] Shadowsocks started (4.1.6)
[2019-07-02 23:43:52] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54865 - PID: 3736
[2019-07-02 23:43:52] Shadowsocks started (4.1.6)
[2019-07-02 23:43:52] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54871 - PID: 5920
[2019-07-02 23:43:52] Shadowsocks started (4.1.6)
[2019-07-03 06:31:14] controller stopped
[2019-07-03 06:31:14] os suspend
[2019-07-03 06:37:05] os wake up
[2019-07-03 06:37:18] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:65298 - PID: 3328
[2019-07-03 06:37:18] Shadowsocks started (4.1.6)
[2019-07-03 06:37:19] controller started
[2019-07-03 06:57:57] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49198 - PID: 3080
[2019-07-03 06:57:57] Shadowsocks started (4.1.6)
[2019-07-03 11:54:55] Checking GFWList from https://raw.githubusercontent.com/gfwlist/gfwlist/master/gfwlist.txt
[2019-07-03 11:55:08] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52179 - PID: 5184
[2019-07-03 11:55:08] Shadowsocks started (4.1.6)
[2019-07-03 11:55:09] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52194 - PID: 4224
[2019-07-03 11:55:09] Shadowsocks started (4.1.6)
[2019-07-03 11:55:10] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 11:55:10] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 11:55:10] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 11:55:10] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 11:55:10] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 11:55:18] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52232 - PID: 2180
[2019-07-03 11:55:18] Shadowsocks started (4.1.6)
[2019-07-03 11:55:18] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:52234 - PID: 5884
[2019-07-03 11:55:18] Shadowsocks started (4.1.6)
[2019-07-03 12:32:13] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54632 - PID: 3876
[2019-07-03 12:32:14] Shadowsocks started (4.1.6)
[2019-07-03 12:32:15] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54653 - PID: 4804
[2019-07-03 12:32:15] Shadowsocks started (4.1.6)
[2019-07-03 12:32:17] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 12:32:21] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54673 - PID: 5176
[2019-07-03 12:32:21] Shadowsocks started (4.1.6)
[2019-07-03 12:32:21] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:54676 - PID: 5836
[2019-07-03 12:32:22] Shadowsocks started (4.1.6)
[2019-07-03 13:11:28] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:56499 - PID: 3200
[2019-07-03 13:11:28] Shadowsocks started (4.1.6)
[2019-07-03 13:11:28] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:56502 - PID: 3772
[2019-07-03 13:11:28] Shadowsocks started (4.1.6)
[2019-07-03 13:11:35] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:56520 - PID: 1052
[2019-07-03 13:11:35] Shadowsocks started (4.1.6)
[2019-07-03 13:11:35] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:56523 - PID: 6080
[2019-07-03 13:11:35] Shadowsocks started (4.1.6)
[2019-07-03 13:37:54] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:58734 - PID: 6016
[2019-07-03 13:37:54] Shadowsocks started (4.1.6)
[2019-07-03 13:37:54] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:58744 - PID: 5396
[2019-07-03 13:37:54] Shadowsocks started (4.1.6)
[2019-07-03 13:37:55] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 13:37:55] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝,无法连接。
   在 Shadowsocks.Util.Sockets.WrappedSocket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.PortForwarder.Handler.ConnectCallback(IAsyncResult ar)
[2019-07-03 13:38:02] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:58759 - PID: 4496
[2019-07-03 13:38:02] Shadowsocks started (4.1.6)
[2019-07-03 13:38:02] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:58761 - PID: 4688
[2019-07-03 13:38:02] Shadowsocks started (4.1.6)
[2019-07-03 14:10:49] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:60174 - PID: 4464
[2019-07-03 14:10:49] Shadowsocks started (4.1.6)
[2019-07-03 14:10:49] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:60188 - PID: 5304
[2019-07-03 14:10:49] Shadowsocks started (4.1.6)
[2019-07-03 14:10:54] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:60214 - PID: 3276
[2019-07-03 14:10:54] Shadowsocks started (4.1.6)
[2019-07-03 14:10:54] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:60217 - PID: 3988
[2019-07-03 14:10:54] Shadowsocks started (4.1.6)
[2019-07-03 14:36:27] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62010 - PID: 2804
[2019-07-03 14:36:27] Shadowsocks started (4.1.6)
[2019-07-03 14:36:27] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62014 - PID: 5204
[2019-07-03 14:36:27] Shadowsocks started (4.1.6)
[2019-07-03 14:36:36] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62030 - PID: 7976
[2019-07-03 14:36:36] Shadowsocks started (4.1.6)
[2019-07-03 14:36:36] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62041 - PID: 7328
[2019-07-03 14:36:36] Shadowsocks started (4.1.6)
[2019-07-03 14:37:56] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62108 - PID: 4296
[2019-07-03 14:37:56] Shadowsocks started (4.1.6)
[2019-07-03 14:37:57] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62110 - PID: 7480
[2019-07-03 14:37:57] Shadowsocks started (4.1.6)
[2019-07-03 14:38:01] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62126 - PID: 4840
[2019-07-03 14:38:01] Shadowsocks started (4.1.6)
[2019-07-03 14:38:01] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62132 - PID: 7536
[2019-07-03 14:38:01] Shadowsocks started (4.1.6)
[2019-07-03 14:38:36] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:62140 - PID: 6408
[2019-07-03 14:38:36] Shadowsocks started (4.1.6)
[2019-07-03 15:01:35] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:63367 - PID: 7000
[2019-07-03 15:01:35] Shadowsocks started (4.1.6)
[2019-07-03 15:01:35] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:63374 - PID: 4152
[2019-07-03 15:01:35] Shadowsocks started (4.1.6)
[2019-07-03 15:01:41] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:63387 - PID: 5812
[2019-07-03 15:01:41] Shadowsocks started (4.1.6)
[2019-07-03 15:01:41] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:63394 - PID: 6264
[2019-07-03 15:01:41] Shadowsocks started (4.1.6)
[2019-07-03 15:08:49] controller stopped
[2019-07-03 15:08:49] os suspend
[2019-07-03 15:10:27] os wake up
[2019-07-03 15:10:37] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:63668 - PID: 6912
[2019-07-03 15:10:37] Shadowsocks started (4.1.6)
[2019-07-03 15:10:37] controller started
[2019-07-03 18:45:39] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49237 - PID: 3404
[2019-07-03 18:45:39] Shadowsocks started (4.1.6)
[2019-07-03 20:54:51] Started SIP003 plugin for *.*.*.*:443 on 127.0.0.1:49188 - PID: 1076
[2019-07-03 20:54:51] Shadowsocks started (4.1.6)

Two workaround i found are : A. Switch proxy mode from Global to Pac if failure occurs when using Global mode. If it occurs using Pac mode, i have to switch to Global then to Pac then back to Global again (Sigh..). B. Restart Shadowsocks Windows client, but it doesn't work every time.

If i leave it be and do nothing about it, it sometimes goes back to normal in few minutes, sometime it just stay dead until i perform the CPR which are the workround above lol . Besides, i found out that when the SS proxy goes extremely slow or failed, so does the SSH connection to the remote server. The connectivity of my remote server is all good at the moment.

That's a useful answer
Without any help

The log from last looks fine, Please check your Cloak configure.

Ok, thx.