Server App Blank Page via Traffic Manager + App Gateway – Suspected Asset Blocking or WebSocket Handling

Mohammad Khan 20 Reputation points
2025-05-06T11:50:41.9166667+00:00

We have configured a application (.NET 9) hosted on Linux App Service (Basic B2), fronted by an Azure Application Gateway (Standard V2). Traffic is routed via Azure Traffic Manager, and the Traffic Manager profile URL is added as a CNAME in our DNS hosting provider.

The application loads successfully via App Service default URL, but when accessed through the custom domain routing via Traffic Manager + App Gateway, we observe a blank white page after loading for sometime.

Observations

  • WebSocket handshake (wss://dev.mindzillion.com/_blazor?...) returns HTTP 101, confirming upgrade.
  • App loads perfectly when bypassing Traffic Manager and App Gateway.
  • When accessed via Traffic Manager + App Gateway path, browser dev tools show:
    • 403 Forbidden errors on api.raygun.io assets and telemetry calls.
      • 404 error for BlazorTable.min.js – critical for rendering.
        • No explicit JavaScript exceptions, but UI fails to load.
        • WebSocket was confirmed enabled via az webapp config show.
  • No caching or DNS issues confirmed — cache cleared, tested across networks/browsers.
Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
1,213 questions
{count} votes

Accepted answer
  1. Venkat V 2,545 Reputation points Microsoft External Staff Moderator
    2025-05-13T05:14:42.27+00:00

    Hi @Mohammad Khan

    I understand you’ve configured a WebSocket-based .NET 9 app hosted on a Linux App Service (Basic B2), with traffic routed through Azure Traffic Manager and Application Gateway.

    To validate this setup, I deployed a sample WebSocket app to App Service, fronted it with Application Gateway, and registered the App Gateway’s public IP as an endpoint in Traffic Manager.

    Gateway backend Settings
    User's image

    **Backend health
    **
    User's image

    Output:
    User's image

    • Traffic Manager Endpoint: [http://test-trafficmanager.trafficmanager.net/]

    Traffic Manager endpointUser's image

    Output:

    User's image

    The application works as expected when accessed via Traffic Manager, and the WebSocket connection remains functional.

    If it's not working on your end, please verify:

    • Whether the app is accessible directly from the Application Gateway’s public IP (without Traffic Manager).
    • That WebSockets are enabled in App Service.
    • That your App Gateway’s HTTP settings have WebSocket support enabled (this must be toggled on explicitly in Standard V2).
    • Check browser console and network tab for wss:// connection errors or CORS issues.

    Reference: WebSocket support in Azure Application Gateway

    I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn't helpful.

    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.