Public URL blocks on chart load, but 3 VPN/Private URLs work perfectly on the same pod.

[user1500177]

Hello Superset Community,I am running a single Apache Superset pod in a Kubernetes cluster.The exact same codebase and pod work flawlessly across 3 separate private/VPN links. Users can view, load, and interact with everything over the VPN.However, when using the Public URL, everything works fine until the charts try to load. The moment chart data is requested, the upstream firewall (Azure Front Door WAF) blocks the request completely.

the error i am getting :

<style type='text/css'> body { font-family: Arial; margin-left: 40px; }

    img {
        border: 0 none;
    }

    #content {
        margin-left: auto;
        margin-right: auto
    }

    #message h1 {
        font-size: 24px;
        font-weight: normal;
        color: #000000;
        margin: 34px 0px 0px 0px
    }

    #message h2 {
        font-size: 20px;
        font-weight: normal;
        color: #000000;
        margin: 34px 0px 0px 0px
    }

    #message p {
        font-size: 16px;
        color: #000000;
        margin: 8px 0px 0px 0px
    }

    #message hr {
        margin: 15px 0px
    }

    #errorref {
        font-size: 11px;
        color: #737373;
        margin-top: 41px
    }
</style>
<title>Service unavailable</title>

The request is blocked.

20260609T050402Z-17ffbf94dd9sbhhbhC1CH1nqrg0000000cp000000000wdau

where as it worth mentioning that same issues doesnt occur with the other urls , the issue is with only the publically accceble one , what could be the causes ?