Can not send a message on my computer!

Jan 10, 2014 at 7:13 PM
Now I can not send a message and does not even use the examples page on my computer!
On although the connection was still open but I can not send one notice!
please help me!
Jan 11, 2014 at 1:51 AM
On your computer means the server runs on your local? Or just access a remote server from your local?
Jan 11, 2014 at 7:06 AM
Previously I have installed SupperSocket on IIS local. Then I uploaded to the sever to be remoted
with other local sever can acess my online server running very good
but my local server cann’t access socket on a remote sever!

I'm looking forward to your reply :)
Jan 11, 2014 at 12:29 PM
Could you verify the connectivity by telnet at first?

Sent from Windows Mail

Marked as answer by Kiennv on 1/11/2014 at 11:50 PM
Jan 11, 2014 at 5:01 PM
I have checked connection by telnet and it is still running
I forgot to provide one important information : when the page is loading( my local is wrong with) , the host and other clients still receive information from my local : "# System: Kiennv connected" and "# System: Kiennv disconnected"
It mean that it is still connected but after the page have loaded I cannot sent any notification!

Function ws.send([text]); wasn’t run or prevented.
Jan 12, 2014 at 1:57 AM
Did you check your browser's console log?
Marked as answer by Kiennv on 1/11/2014 at 11:49 PM
Jan 12, 2014 at 6:49 AM
OMG! it's true that my problem! :))
 * IE version - [11.0.9600.16476]   __OK__
 * Chrome ver - [31.0.1650.63 m] (current version)   __Bad__
 * Chrome ver - [31.0.1700.72 m]  __OK__
Thank you very much!
Apr 18, 2014 at 6:16 AM
I don't understand why sample projects don't work on Chrome Version 35.0.1916.27 beta-m but it's working fine on Firefox 28.0?

In Firefox able to send and receive chat messages and other sample projects work fine but not on Chrome!
I used to run sample projects on Chrome previously!
Apr 18, 2014 at 6:55 AM
Did you check the log of server side?
Apr 18, 2014 at 9:26 AM
Yes I checked logs and it's empty.
Client get disconnected as soon as it's attempt to connect. (Reason-Client Closing).
I can connect and successfully send data 55000 bytes per attempt in firefox but not in latest Chrome- Version 35.0.1916.47 beta-m!
Apr 19, 2014 at 11:58 AM
If the closing reason is ClientClosing, the connection should be closed from the client side.
So probably it is not a problem of SuperSocket/SuperWebSocket.
Apr 21, 2014 at 4:34 AM
Edited Apr 21, 2014 at 4:48 AM
Yes connection is closing from client side, more specifically on Chrome but not on Firefox! Why?
On Firefox it's working fine.
Apr 21, 2014 at 3:22 PM
I also don't have any idea. Could you try another version of Chrome?