AZure Application Gateway 504, Backends Healthy

mikefinch87@gmail.com 60 Reputation points
2024-02-02T16:31:58.7633333+00:00

I have an application Gateway fronting two function apps, each with a separate host name. One I can access, the other generates a 504 Timeout every time.
I have increased the backend settings timeout to 240 to match an Azure Function in the portal. User's image

I am not running a load test, just manually from postman. The function Logs show no invocations. Where can I look for more information as to what is happening. I have reviewed the following questions:
https://learn.microsoft.com/en-us/answers/questions/1166337/how-to-troubleshoot-504-502-4xx-errors-in-app-gate https://learn.microsoft.com/en-us/answers/questions/1371233/getting-gateway-timeout-in-azure-application-gatew

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,301 questions
Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
962 questions
0 comments No comments
{count} votes

Accepted answer
  1. MayankBargali-MSFT 68,656 Reputation points
    2024-02-07T05:56:34.7633333+00:00

    @mikefinch87@gmail.com I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer.

    Issue:

    You have an application Gateway fronting two function apps, each with a separate host name. One you can access but the other generates a 504 Timeout every time.

    Solution:

    You found the root Cause of the issue that you were hitting an http endpoint with only an https listener.

    I will pass your feedback internally to the team.

    Thank you again for your time and patience throughout this issue.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. mikefinch87@gmail.com 60 Reputation points
    2024-02-04T17:20:31.1466667+00:00

    Root Cause was hitting an http endpoint with only an https listener.
    Seems like there should be a better error code.

    0 comments No comments