Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
828 questions
Azure FrontDoor timeout / closing connection
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 72%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Stefano Azzalini
6
Reputation points
We are facing availability issues with Azure Frontdoor (classic).
The first picture shows availability on the public frontdoor endpoint, the second one is the relative backend (appgw public ip)
The reported error is Unable to read data from the transport connection: The connection was closed.. (the test timeouts out after 120s)
It is worth mentioning that headers are always successfully sent to the client, but not the body.
The availability tests runs from the same regions.
Azure Front Door
{count} votes
-
KapilAnanth-MSFT 49,421 Reputation points Microsoft Employee Moderator2022-12-29T15:34:21.053+00:00 Hi @Stefano Azzalini ,
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are facing timeouts with Azure FrontDoor.To figure out if the timeout is coming from Azure Front Door or the backend,
- Please check the diagnostic logs of the AFD
- From your monitoring tool, get the client IP and Port.
- Use this to filter the logs and see what the HTTP error code and "ErrorInfo" are from AFD perspective
Refer:
AFD TimeOuts- May I know what is the TCP idle-timeout value configured in the Public IP of the App Gateway?
- Is the test being performed in the region of App Gateway?
- If so, can you perform the same test from a different region than where App Gateway is deployed
-
Udaiappa Ramachandran 726 Reputation points MVP2023-01-02T17:19:22.167+00:00 If you use a premium front door increase the origin response timeout from overview to 240 seconds (max)
If you use a classic front door increase the value from FD Designer-->Settings-->Send/Receive Timeout (in seconds) to 240 (max)
-
Stefano Azzalini 6 Reputation points
2023-01-05T09:25:55.997+00:00 @KapilAnanth-MSFT
We have tests from multiple regions and we have consistent failures from a bunch of them.
I do not really want to increase the timeout since 120s is already too high imo.
I also monitored the app with an 3rd party tool and the result are the same:
frontdoor timeout while the backend has 100% uptime -
KapilAnanth-MSFT 49,421 Reputation points Microsoft Employee Moderator
2023-01-05T12:51:52.643+00:00 Hi @Stefano Azzalini ,
I understand your concern here.
It is highly possible that the timeout is coming from the backend to AFD and not from AFD to the end clients.
Please note that it is not my suggestion to increase the timeout value.
Only if we could check the AFD logs, we can understand what caused the timeout for a specific request.
- Please check the diagnostic logs of the AFD
- From your monitoring tool, get the client IP and Port.
- Use this to filter the logs and see what the HTTP error code and "ErrorInfo" are from AFD perspective
Thanks,
Kapil
Sign in to comment
Sign in to answer