enable WebSocket profile.

[mdtariqul]

We want to enable WebSocket profile. I set is "websocket" in the virtual server

To enable it, HTTP profile needs to be enabled. I set it "http" in the same virtual server

We have SSL communication through F5 LTM from the internet, if I enable HTTP profile -- the connection is not established with the server. 

Anything I need to configure? 

Thanks in advance. 

[PSFletchTheTek]

Hi,

So websockets is part of the html payload.

So you need to be able to see that payload for the profile to take affect.
Have you got the client ssl and server ssl configuations on?

Before you enabled the websockets profile, was this a working setup?

[mdtariqul]

We did not off-load ssl in our LTM (Local Traffic Manager, i4800; BIG-IP 16.1.0 Build 0.0.19 Final). We only create sessions for 443 https virtual servers, ssl is maintained by internal servers. So, this was a working setup.

Now the application vendor needs the WebSocket session.  I just enable it in the virtual server as follows, and then the total communication stops. 

to do this, we need to enable http profile

it seems I am not on the right track. 

[boneyard · Accepted solution]

if you do not offload (or bridge - decrypt / re encrypt) SSL on the BIG-IP you can't do other profiles as the BIG-IP can only the encrypted traffic, which it can't read / understand.

[mdtariqul]

Finally, we are going for off-loading. 

Thank you all for the support. 

[LiefZimmerman]

@mdtariqul - If your post was solved it would be helpful to the community if you selected Accept As Solution on the relevant reply (or replies). This helps future readers find answers more quickly and confirms the efforts of those who helped.

Thanks for being part of our community.
Lief

[Poseidon1974]

Its works ? 

[ZANOOB]

Hi ,

I am as well doing the same , want to enable webscoket.

I do have http profile and ssl bridgin in place . but some how i get an error when enabling webscoket .

01070734:3: Configuration error: Profile(s) found on /Common/example.com that are not allowed: Only (TCP Profile, UDP Profile, QUIC Profile, ClientSSL Profile, ServerSSL Profile, HTTP Profile, HTTP2 Profile, HTTP3 Profile, HTTP Compression Profile, Application Visibility and Reporting Profile, DNS Profile, DOH Proxy Profile, profile statistics, Protection Profile, Bot Defense Profile, Bot Defense ASM Profile, Web Security Profile, HTTP Router Profile, Web Accelerator Profile, Request Logging Profile, TDR Profile)

[ZANOOB]

Hi ,

I was able to reolve it after disabling http/2 profile from the virtual server.

[Poseidon1974]

Hi ,

Solved after adding certificat on VS