Today, the use of the acquisition end of the connection server, the discovery of either the previous platform, or the newly deployed platform, when registering information, always fail to register the success of the platform as a problem, but the first platform can be logged in, and the use of Interface Connection tool verification is also can be connected, so the problem of the server interface is excluded.
Then carefully debug your own program, found that the error is: "Because the target computer actively refused to connect." 127.0.0.1:56013 ", the first reaction port is occupied, use Netstat-ano view found no problem, and then online to find this post: http://blog.csdn.net/u010784236/article/details/ 51820284?_t=t, then looked at his default browser, found that no use of agents, and then continue to look for problems, but check to find that the agent caused the problem, and then think of the previous chrome use anomalies, and then looked at the Chrome proxy server settings, Sure enough, the 127.0.0.1:56013 is used, the proxy server is canceled, the problem is resolved.
In fact, the cause of the final cause is caused by the use of blue light FQ. Ha ha
To request a web interface to prompt for resolution of a problem that cannot connect to a remote server