Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
506 questions
Increase Application Gateway Load balancer gateway timeout
![](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(313.6, 40%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Debarth
0
Reputation points
Application gateway load balancer request timeout was set to 20s.
Increased in to 300s but still request gets timed out in 60s.
Any solution would be much appreciated.
Azure Load Balancer
{count} votes
-
SUNOJ KUMAR YELURU 15,256 Reputation points MVP Volunteer Moderator2024-10-04T07:43:49.5366667+00:00 Hello @Debarth
Azure Application Gateway timeouts occur when requests exceed the configured timeout period. This can be due to slow backend servers, network issues, or misconfigurations within the gateway itself. Troubleshooting involves checking gateway settings, backend health, and network connectivity.
Step 1: Understand Timeout Settings
Azure Application Gateway has a default timeout setting for requests, which is typically 60 seconds. If you've increased the timeout to 300 seconds but still experience timeouts, it’s essential to verify that the correct settings are applied.
Step 2: Check Application Gateway Configuration
- Access the Azure Portal: Log in to your Azure account and navigate to the Application Gateway resource.
- Review Timeout Settings: Look for the "Settings" section, then check the "HTTP settings". Ensure that the "Timeout" value is indeed set to 300 seconds.
Step 3: Verify Backend Health
- Check Backend Pool: Ensure that the backend servers are healthy and responsive. Navigate to the "Backend health" section of the Application Gateway.
- Investigate Backend Response Times: If the backend servers are slow to respond, they may still cause timeouts even if the Application Gateway timeout is set higher.
Step 4: Review Application Gateway Logs
- Enable Diagnostics Logs: If not already enabled, turn on diagnostics logs for the Application Gateway.
- Analyze Logs: Look for any errors or patterns in the logs that might indicate why requests are timing out.
Step 5: Test with Different Scenarios
- Test Different Endpoints: If possible, test requests to different endpoints or services behind the Application Gateway to see if the issue is consistent.
- Use Tools: Utilize tools like Postman or curl to simulate requests and measure response times.
Final Answer
If the timeout persists despite increasing the setting to 300 seconds, ensure that the backend servers are healthy and responsive. Check the Application Gateway logs for any errors and consider testing different endpoints to isolate the issue. If necessary, consult Azure support for further assistance.
Step 1: Understand Timeout Settings
Azure Application Gateway has a default timeout setting for requests, which is typically 60 seconds. If you've increased the timeout to 300 seconds but still experience timeouts, it’s essential to verify that the correct settings are applied.
Step 2: Check Application Gateway Configuration
- Access the Azure Portal: Log in to your Azure account and navigate to the Application Gateway resource.
- Review Timeout Settings: Look for the "Settings" section, then check the "HTTP settings". Ensure that the "Timeout" value is indeed set to 300 seconds.
Step 3: Verify Backend Health
- Check Backend Pool: Ensure that the backend servers are healthy and responsive. Navigate to the "Backend health" section of the Application Gateway.
- Investigate Backend Response Times: If the backend servers are slow to respond, they may still cause timeouts even if the Application Gateway timeout is set higher.
Step 4: Review Application Gateway Logs
- Enable Diagnostics Logs: If not already enabled, turn on diagnostics logs for the Application Gateway.
- Analyze Logs: Look for any errors or patterns in the logs that might indicate why requests are timing out.
Step 5: Test with Different Scenarios
- Test Different Endpoints: If possible, test requests to different endpoints or services behind the Application Gateway to see if the issue is consistent.
- Use Tools: Utilize tools like Postman or curl to simulate requests and measure response times.
Final Answer
If the timeout persists despite increasing the setting to 300 seconds, ensure that the backend servers are healthy and responsive. Check the Application Gateway logs for any errors and consider testing different endpoints to isolate the issue. If necessary, consult Azure support for further assistance.
If this answers your query, do click
Accept Answerand Up-Vote for the same. And, if you have any further query do let us know. -
SUNOJ KUMAR YELURU 15,256 Reputation points MVP Volunteer Moderator
2024-10-06T07:22:40.03+00:00 @Debarth To follow-up, Please let us know if you have further query on this and don’t forget to
Accept the answer -
KapilAnanth-MSFT 49,536 Reputation points Microsoft Employee Moderator2024-10-08T10:49:23.9433333+00:00 @Debarth ,
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I see Sunoj has added their insights.
I would suggest you check the Application Gateway Access Log.
- And use properties such as
- timeTaken
- serverResponseLatency
- clientResponseTime
- error_info
- To understand whether or not the application itself closed the connection rather than the App gateway
See : How to Enable logging through the Azure portal
Cheers,
Kapil
- And use properties such as
-
Bjørn Einar Bjartnes 0 Reputation points2024-11-27T10:03:38.3033333+00:00 I observe the same issues, it did ultimately update when I came back the next day. I have tried waiting at least 15-20 minutes after the updates should have been affected, so I am wondering if this might be some propagation time issue?
-
Bjørn Einar Bjartnes 0 Reputation points
2024-11-27T10:58:38.4+00:00 My bad, is was a Front Door Instance in front with another timeout of 30 seconds. Front Door took about 20 minutes to update, but App Gateway was more or less instantly. (Front Door has a global setting for timeout, so it was not discoverable at the same place as App Gateway).
Sign in to comment
Sign in to answer