Azure CDN for Edgio returns 504 Gateway Timeout on URL request

Samuel Peter Jenks 20 Reputation points
2024-05-07T08:12:59.6966667+00:00

I am attempting to point my Azure CDN for Edgio towards an Azure Container App's custom domain with HTTPS traffic. I have bought a custom certificate which has been uploaded to a Key Vault which both the container app and cdn have permission to use for custom domains. The certificate allows wildcard domains which allows me to assign a different CNAME record to each cloud resource.

Ingress traffic has been configured on the Container App to allow HTTP on port 80 and HTTPS on port 443. Likewise for the CDN. Performing a GET request via HTTP to the CDNs custom domain succeeds with a 200 OK status. Performing a GET request via HTTPS fails with 504 Gateway timeout. This is failing not just for the CDN's custom domain, but also the auto generated URL.

Switching to Azure Front Door resolved the issue, but it is too expensive for me.

I am struggling to find a solution to this problem. How can I maintain the same architecture while fixing this problem?

Azure Content Delivery Network
Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
324 questions
0 comments
Accepted answer
  1. KapilAnanth-MSFT 39,211 Reputation points Microsoft Employee
    2024-05-07T11:13:53.55+00:00

    @Samuel Peter Jenks ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you are experiencing 504 Gateway timeout with Azure Edgio CDN, where as AFD works perfectly with Azure Container App (which uses a custom domain).

    • Is there any requirement that you would like to use Azure Edgio CDN and not Azure CDN Microsoft?
    • You may also consider Core Reports and Custom Reports , to troubleshoot why the Edgio CDN gives a 504.
    • 504 generally means that the Gatway (CDN) did not receive a timely response from the Origin which results in a time out, and it is possible that the backend itself is not responding to the HTTPS request from the CDN.

    Cheers,

    Kapil

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest