Instability on WSS Connections, only works when one client abandon connection

[Irahe]

hello, im implementing a simple secure websocket server and client. My server implementation is the same as provided in the example folders, and im using websocket.org to test this implementation (http://www.websocket.org/echo.html). I can connect using WSS. However, to do so, i need to request connection on thwo tabs, and close one of them. The other then, connects perfectly. If i dont close one of the tabs, all connections timeout. The server does not give me any exceptions on console not when it connects nor when it cant.
I dont have many experience with WSS. However, WS implementaton works out of the box with this same server.
For my experience, seems like a endless loop is created when i try to connect. And only breaks when i kill one of the tabs trying to connect.

For the record, im using version 1.3.3

Can you help me out pls?! =*

EDIT -

Hello again, im posting a sample project to illustrate my problem. With this project is my keystore.jks.
The password for the keystore is password and the password for the key is password, as shown on my source.

Please, help out.
d3_Servidor.zip

[marci4]

Hello @Irahe,

I just tested your problem with my wss which I use in production and the issue mentioned does not occur for me.

Going to look into your sample project.

Til then, could you please tell me which clients you use? (so which browser)

Greetings
marci4

[marci4]

Hello @Irahe,

I looked into your project and for me it works fine.

The problem may be your self signed certificate.

Did you go to https://localhost:8283 and told your browser to trust the certificate? (wss server has to run)

Greetings
marci4

[Irahe]

Hello @marci4 , thank you for your fast response!

Im using firefox 53.0 (32bits) for my tests. and i already have gone to https://localhost:8283 and accepted my certificate.
What i cant understand is that if the problem is with my certificate, why some times it can connect correctly?

The client im testig with is from websocket.org. it is on this link: http://www.websocket.org/echo.html.

Can you tell me step by step how i must configure my setup so it works for me too?

Thank you =*

[marci4]

Hello @Irahe,

this is interesting. This problem occurs for me as well in firefox, but not in chrome.
It is also limited to localhost, since I was able to connect to my production wss.

Just to clear some things up, your client is firefox.
The websocket.org website just provides an easy interface for the javascript implementation below.

Gonna test it against other implementations of websocket servers and gonna keep you updated.

Greetings
marci4

[Irahe]

Hello there, @marci4 ,

Thank you again for your immediate response! This is really getting interesting.
Im getting a Let's Encrypt certificate for my production domain, and so ill try to apply it to a test server on a subdomain there...
I hope it works...

I keep you posted!

Best wishes,
Irahe Kasprzykowski.

[marci4]

Ok here is my current status:

SSC = Self signed certificate
LE = Let's Encrypt

Test case echo.websocket.org SSC:

• Internet Explorer 11.1066 ERROR Security error
• Firefox 53.0 ERROR Sometimes doesn't work (like 75% are fine)
• Edge 38.14393 ERROR Security error
• Chrome 59.0.3071.29 PASS

Test case local file SSC:

• Internet Explorer 11.1066 PASS ALWAYS
• Firefox 53.0 ERROR Sometimes doesn't work (like 75% are fine)
• Edge 38.14393 PASS Cannot get the browser to trust the certificate
• Chrome 59.0.3071.29 PASS

Test case local file LE:

• Internet Explorer 11.1066 PASS (After not checking for revoke server)
• Firefox 53.0 ERROR Sometimes doesn't work (like 95% are fine)
• Edge 38.14393 PASS (After not checking for revoke server)
• Chrome 59.0.3071.29 PASS

Having TcpNoDelay set to false!

I also was able to connect to your server without problems.

Do you really need TCP_NODELAY set to true?

Greetings
marci4

[marci4]

Hello @Irahe,

as mentioned above, do you really need tcpNoDelay set?
It does cause additional stress for the cpu and network, and I think it could be the main reason for the problems.
It is the only difference between your and my server.

Greetings
marci4

[Irahe]

Hi, @marci4 ,

I have disabled TCPNoDelay on the chatserver at my domain.
However, my problems with Firefox and other naughty browsers other than chrome keep happening.
In Firefox, if i connect, disconnect and try to reconnect, it just does nothing for a while, then times out.

Why is Firefox so unrighteous? LOL...

Greetings,

Irahe Kasprzykowski