Forum Discussion

wogo1905_288591's avatar
wogo1905_288591
Icon for Nimbostratus rankNimbostratus
Aug 29, 2017

APM + LTM: Web socket issue

Dear Colleagues, I have been asked to configure load balancing on F5 between two web servers and provide secure access to it. I configured virtual server on F5 LTM and I configured access policy which allow user to login to application with using webtop. After implementation I get below error which affect.

 

Virtual server: WebSocket connection to ‘wss://URL’ failed: Error during WebSocket handshake: Unexpected response code: 504

 

Webtop + Virtual server: WebSocket connection to ‘wss://URL’ failed: Error during WebSocket handshake: Unexpected response code: 302

 

I use BIG IP in version 12.1.2 Should I configure come Web Socket profile on virtual servers, please could you advise?

 

7 Replies

  • Hello Wogo,

     

    On your VS did you selected the default "Websocket" profile and tried with that one ?

     

  • When I try to connect with VS without APM I get below error WebSocket connection to ‘wss://URL’ failed: Error during WebSocket handshake: Unexpected response code: 504

     

    When I try to connect with VS through APM I get below errors: Webtop + Virtual server: WebSocket connection to ‘wss://URL’ failed: Error during WebSocket handshake: Unexpected response code: 302 Uncaught ReferenceError: F5_Inflateindex is not defined.

     

    On VS I applied profiles: TCP, WebSocket, HTTP, SSL (Client and Server), wancompresion, oneconnect

     

    • Jad_Tabbara__J1's avatar
      Jad_Tabbara__J1
      Icon for Cirrostratus rankCirrostratus

      1) First of all, without F5 when passing directly, does it work ?

       

      2) Then pass the VS_1 to "Performance Layer 4" without any profile except TCP ? Once you validate this, we can go further

       

    • wogo1905_288591's avatar
      wogo1905_288591
      Icon for Nimbostratus rankNimbostratus

      1) First of all, without F5 when passing directly, does it work ?

       

      Yes, when I connect to servers directly application works fine.

       

      2) Then pass the VS_1 to "Performance Layer 4" without any profile except TCP ? Once you validate this, we can go further

       

      When I changed VS to Performance Layer 4 VS went down. It uses SSL profiles and they missed.

       

    • Jad_Tabbara__J1's avatar
      Jad_Tabbara__J1
      Icon for Cirrostratus rankCirrostratus

      VS went down (red) ? how is it possible since you didn't make any change to your pool...

      On which port you VS is listenning ? and on which port your backend are listenning.

      Based on you this

      On VS I applied profiles: TCP, WebSocket, HTTP, SSL (Client and Server), wancompresion, oneconnect

      I guess that both VS & backend listen on 443, can you confirm ?