ProxySG & Advanced Secure Gateway

Expand all | Collapse all

Web WhatsApp QR code not display when traffic via ProxySG

  • 1.  Web WhatsApp QR code not display when traffic via ProxySG

    Posted 15 days ago
    Hi Team,

    In chrome browser when we access web WhatsApp via ProxySG, unable to load the QR code and keep loading.

    Kindly advice what could be causing this issue.

    Thanks,
    Raju


  • 2.  RE: Web WhatsApp QR code not display when traffic via ProxySG

    Broadcom Employee
    Posted 15 days ago
    Hi Raju,

    I am not aware of any known compatibility issues between WhatsApp and ProxySG. As such, I would start basic troubleshooting, as you would any other URL that isn't loading.

    The first thing I would check is the behavior in other browsers. If the other browsers work just fine, I would look more closely at Chrome.

    If all the browsers have issues, I would use the network section of the Developer Tools in the browser to check what components of the webpage are failing, and then look for those same components in policy traces and packet captures to see if the ProxySG is blocking those components, or if something is failing.

    Another option is to troubleshoot using the following CPL, which allows you to take a test user, and troubleshoot the connection with different options (such as ssl decrytion) disabled, to try and hone down any possible conflict that way.

    https://knowledge.broadcom.com/external/article/167379/cpl-script-to-troubleshoot-proxysg-or-as.html

    Hope that helps!


  • 3.  RE: Web WhatsApp QR code not display when traffic via ProxySG

    Posted 15 days ago
    Hi Jacob,

    Thanks for sharing feedback.
    User facing issue in all browsers and reviewed the policy trace but couldnt get much information.
    Even created rule and alowed the user IP as any any but still facing the same issue.

    Let me try the magic scripts which you have recommended.

    Thanks,
    Raju


  • 4.  RE: Web WhatsApp QR code not display when traffic via ProxySG

    Posted 12 days ago
    I remember we had this case some years ago. Internally we don´t allow whatsapp, but the solution is/was  to disable the ssl interception.
    you just need to check which url need the interception disable.

    Regards

    Fermin

    ------------------------------
    Sytems Engineer
    GW
    ------------------------------