Getting error "Our services aren't available right now" While configure Azure front door on top of Application gate way

Question

My Application is deployed on useast2 and central us on the aks cluster. They are using the service as a load balancer. On top of the load balancer, we are using an application gateway where all routing rules are configured.On top of that we are using a traffic manager to accept traffic from globaly.

Now we are planning to replace traffic manger with Azure front door standard. I have configured AFD already and origin is set to application gateway. But I am getting Our services aren't available right now.

Can anyone help me to fix this issue?

Answer 1

Hello @Chinmaya Chhotaray ,

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

I understand that you configured Azure Front Door in front of your Application gateway but you are getting the following error "Our services aren't available right now".

May I know how long has it been since you configured the Azure Front Door?

Azure Front Door Standard/Premium Endpoint takes 10 to 90 minutes to take effect.

So, it is recommended for customers to check back after 30 minutes to 2 hours to see if the issue has auto mitigated.

If the error is still presented after 3 hours, then we need to verify if the endpoint and origin mapping is correct.

Please check the HTTP status code that you are receiving when accessing the Front Door.

• HTTP 400 responses from Front Door with "Our services aren't available right now" error could appear before the AFD profile is fully provisioned or for domains/hostnames/protocols that are not registered in Front Door.
• The 400 error can happen if you have not configured a routing rule for the frontend host. A routing rule needs to be explicitly added for the custom domain. Refer: https://learn.microsoft.com/en-us/azure/frontdoor/troubleshoot-issues#requests-sent-to-the-custom-domain-return-a-400-status-code
• If your environment is HTTPS only and you do not have a HTTP to HTTPS redirect, make sure that you are using HTTPS when you connect to the front door. Refer: https://learn.microsoft.com/en-us/azure/frontdoor/troubleshoot-issues#azure-front-door-doesnt-redirect-http-to-https
• If you are using own SSL certificate, make sure that the certificate has a complete certificate chain with leaf and intermediate certificates, and root CA must be part of the Microsoft Trusted CA list. Refer: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https#option-2-use-your-own-certificate
• 503 responses: If your AFD origin is configured as an IP address, then either disable "EnforceCertificateNameCheck" (not recommended) or change the origin from an IP address to an FQDN to which a valid certificate is issued that matches the origin certificate. Refer: https://learn.microsoft.com/en-us/azure/frontdoor/troubleshoot-issues#my-origin-is-configured-as-an-ip-address

Kindly let us know if the above helps or you need further assistance on this issue.

---

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.