503 Errors or Blank Page from Azure Front Door

0
votes

I've read through the link below and extended the timeout, disable compression on the Origin/Azure Front Door and a Rules Set rule to remove accept-encoding from the request for byte range requests. However, I am still getting these random 503 errors or blank pages.

https://docs.microsoft.com/en-us/azure/frontdoor/front-door-troubleshoot-routing

In my web app, I've added the custom domain (app.contoso.com) with my own certificate.

enter image description here

And in my Front door, I've added my custom domain (app.contoso.com) with my own certificate and set up a backend pool and a routing rule.

enter image description here

enter image description here

And in the update backend, I've left the backend host header empty as I would like it to be able to redirect to the custom domain instead of showing the web app url.

enter image description here

And in my routing rule, I've set the following

enter image description here

I've followed the instruction closely provided from Azure but still getting random 503 Errors or Blank Page from Azure Front Door. And I can confirm that my Web app (contoso.azurewebsites.net) is working when I am getting a 503 errors or blank pages from the custom domain from front door. I've also ensure I used the same SSL certificate on the web app and front door custom domain.

In my DNS, I've mapped the following

app.contoso.com CNAME contoso.azurefd.net

Is there anything I missed out or does anybody have a solution to this?

Follow up

I've tried to enable and disable the certificate subject name validation and change the send/receive timeout from 30 to 240 or from 240 to 30 but still getting the same issues.

enter image description here

Update: It giving blank page or 503 error (see screenshot below)

I have FrontDoor setup in front of multiple backend Web App. I've noticed there's a number of random 503 errors each day. The requests themselves are valid, and retrying generally works, however, the initial request that fails is not hitting the backend Web App. The backend health at the times of the errors are also 100%, and it can't be a timeout because the error is immediate (timeout is also extended to 240 seconds). It seems like FrontDoor itself is having some kind of health issue, but there's no health issues mentioned.

enter image description here

1
azureazure-web-app-serviceazure-front-door
Could you please help us to know that have you configure this setting in azure front door as followed by Microsoft document [1]: i.stack.imgur.com/UFi0r.png – AjayKumarGhose-MT
@AjayKumarGhose-MT I've updated the post. See Follow up section. Initially, 30 doesnt work so I changed to 240 based on the Azure troubleshooting article (docs.microsoft.com/en-us/azure/frontdoor/…) – DANLEE

1 Answers

0
votes

I tried in my local environment and it works fine for me ,Followed by this MS DOC .

Here is my configuration :

enter image description here

Make sure that you have add your custom domain properly which destination as frontend host name.

enter image description here

In backend pool i have tried to set the interval to 5(small value) so the front door knows if backend is down and that it shouldn't routes traffic to that backend anymore

enter image description here

In routing rules, make sure that you have checked all your frontends/domains . enter image description here

enter image description here

After that you can run by hitting your frontdoor host . enter image description here

Please refer this Microsoft documentation : Add a custom domain to your Front Door for more information.