Azure Front Door - Our services aren't available right now

Question

Hello,

I'm trying to deploy Azure Front Door + WFA for the web site that is hosted on IIS on the VM in Azure. All services located in one subscription.

I set up the Azure Front Door but it's not working. I only see next error message when I open front door URL:

I tried to connect a custom domain to the Front Door but this has not affected it and the error message still persists. There are some similar topics with the same issue but I don't use CDN or something. My current IT topology is much simpler: one VM with Windows 2019 with IIS (only HTTPS) and I want to improve security enabling FD + WFA.

Thank you!

Answer 1

Typically this error occurs when there is an issue with the routing rule, causing incoming traffic to not appropriately be sent to your backend pool.

Make sure that you have a routing rule that works for HTTPS, as well as making sure you have a separate routing rule if you have a custom domain on your front door.

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!

Answer 2

Ok, it seems I understood the problem but still can't find out how to manage it. There are multiple websites on the IIS server and I cannot understand how to route the incoming traffic to the proper web site in IIS.

For example, next web sites hosted in the IIS: site1.contoso.com, site2.contoso.com and site3.contoso.com. All sites are in public access. I want to enable AFD for the web Site #1. I registered a custom domain site1fd.contoso.com. But how to set up AFD to route traffic site1fd.contoso.com -> site1.contoso.com? Currently I set the public IP of the IIS server in the backend pool and it's definitely not working. It started working if I set site1.contoso.com in the backend pool but it doesn't make sense because site1.contoso.com will be still in public access. 

Also, I've tried next settings but still no luck

Thank you!

Answer 3

Can you check what certificate you are presenting from the backend? It's possible the subject name presented by origin certificate isn't matching the backend host header name.

Answer 4

Hello!

I have the same problem on my computer. When I try to reach "www.dev.azure.com" I get the same message in the browser, namely: "Our services aren't available right now We're working to restore all services as soon as possible. Please check back soon.". When I try to ping "13.107.42.20" in my Powershell, I get the message "Timed Out". I would appreciate any help about this issue.

Thank you,
Dota