In this case you should contact your ISP representative. Make sure that the Host can establish outbound connections on these ports or allow the ports in the local and perimeter firewall if necessary.Įven if outbound connections on TCP ports 5655 and 443 are allowed on the Host machine and in the perimeter firewall, such connections may still be blocked on the ISP level. When used with our public service the ports used are TCP 5655 and 443. The Internet-ID connection requires some outbound ports to be open. Solution 3: Make sure outbound connection is allowed Please, contact your system administrator. If you receive "Request timed out" as a response, the ID server cannot be reached from the Host location.If the ping command and DNS resolution are successful, the result will be shown in the CMD window:.Type cmd and click OK (or press Enter).If you use our public Internet-ID service make sure that the primary server at id. can be accessed from the Host PC and the IP address of the server can be resolved successfully. Solution 2: Check connectivity with our public server Wait 10-20 seconds until the Host restarts and connects back to the intermediate server. Right click on the Host icon in the tray area and select Restart Host.Type ipconfig /flushdns and click OK (or press Enter) to clear the DNS cache:.This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. With privoxy with exactly the same forward rule of QQ PC clients, it works pretty well.As quoted from Windows Sockets Error Codes: The server will do 302 redirect to and should connect to the actual video file. Just wait for update : I send all traffic of QQ PC client to node server (mitm_proxy on), it just repeatedly loading like this In theory, It should work with node server with mitm_proxy even you forward all traffic. I still can't figure out how to further limit the url it needed to access. Please make sure that you have read and understood the HTTP proxy servers topic before using this am not good at providing support of all PC clients because of my progamming and networking skill is not good(T^T). You can enable this protocol at Profile->Advanced->HTTP Proxy Servers. Reedng proxy replay on a c o m e d c n reouest faled w theror 10054 (376. Unfortunately, such proxies can only be used for HTTP connections. If a n y p o r t r e t u r n s an IC M P e r r o r, t h e n its clo s e d. HTTP - the most common type of proxy servers. You can also check the proxy with the Proxy Checker tool. If an HTTP proxy works properly in the browser but fails in Proxifier, it most likely means that SSL support is unavailable. Many HTTP proxy servers do not support SSL tunneling therefore, they cannot be used as HTTPS. HTTP proxy with SSL tunnel support is also known as: Technical documentation can be found at: HTTPS - HTTP proxy with SSL support for arbitrary ports. Proxy type HTTP can only tunnel HTTP connection When you need to proxy ssl connection, proxy type should be HTTPS Per the help file in proxifier 3.21, Working with proxifier -> Proxy Server Settings Please make sure that client uses HTTP protocol. YoukuDesktop.exe - :443 HTTP connection error : Client sent incorrect HTTP request. YoukuDesktop.exe - :443 open through proxy XXXX HTTP Worker 7120 exited with error code: is interesting that when I set the mode as http TypeError: Cannot call method 'on' of undefinedĪt nnect_req_handler (C:\Users.\AppData\Roaming\npm\node_modules\ub.uku.js\server\server.js:333:23)Īt (events.js:106:17)Īt (http.js:1986:14) Caught uncaughtException: TypeError: Cannot call method 'on' of undefined YoukuMediaCenter.exe - :443 error : Could not connect through proxy ub.uku.js.cmd - Reading proxy replay on a connection request failed with error 10054ġ2 Sep 14:06:48 - Worker 7120 is now connected to 127.0.0.1:8888 I thought you may be interested to see that. With server type set to HTTPS, I saw following repeated error messages from both proxifier and ub.uku.js proxy server windows while Youku client is running. However, Youku client works either with the type set to HTTPS or to HTTP. Ub.uku.js.cmd -local_only I set the proxy server type to HTTPS but it failed to pass checking so I changed it to HTTP type it passed. Will continue trying more to be sure but so far so good. With a proxifier rule set to force Youku PC client to use proxy server that I run on the same PC with the following command, I can now play at least one video clip which wasn't possible.
0 Comments
Leave a Reply. |