Forum Discussion
NimbostratusHow to set up web socket comms on LTM V11.5
Hello,
I am looking to use our LTM v11.5 to balance traffic for our mobile device web services which utilise the "Node.js" web socket services, but I just can't seem to get it to work correctly.
The initial call in works but the web socket communication doesn't get established and faults.
I have read that we needed to update our firmware to 11.5 for support of web sockets and then that we should use a http profile, no other guidance can I find!
Could someone please provide me with a step-by-step process of how to allow web socket communication to occur please?
We are making the communication using port 443/SSL.
Many thanks for any help provided.
4 Replies
That should be all that is required. If your connections are failing for some reason, you need to define "fail" in a bit more detail.
Also, this document may be helpful/relevant: BigIP support for the websocket protocol
AndyC_128552Hello,
Thanks you very much for your response. I think I need to explicitly define what is meant by a "HTTP" profile as I am no expert on configuring the LTM but do know my way around it. I have set up a virtual server with: Type - Standard Service Port - 443 /HTTPS Protocol - TCP HTTP Profile - None Source Address Translation - Auto-Map The rest is as per default, there is no persistence or Connect-one profile in place and I only have one of the servers enabled in the 2 server pool to allow me to diagnose this without having to follow server connections. The problem is like the web service hears the request but it can't set-up the web socket correctly (internal service fault). The service works fine if run locally on the server, not including the LTM in the call.Thanks
This may be useful: Websocket with HTTPS
- Also, internal service fault on the webserver? You'll get better information in the server's logs.
