Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
863 questions
Need help on Health Probes for Azure Front door and Azure Container Apps
![](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(307.2, 1%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Salini, Krovi
0
Reputation points
Hi Team,
I have created health probes in azure container apps and what are the services deployed in container apps their traffic will going through Azure front door but here my issue is in my front door every service is receiving 404 error and also not receiving expected health check status can anyone help me this issue. For health probes checking in container apps we have provided path but in front door I didn't see my service probe URL in properly.
Thanks,
Salini
Azure Front Door
Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
708 questions
{count} votes
-
GitaraniSharma-MSFT 50,106 Reputation points Microsoft Employee Moderator2023-11-24T10:14:33.5033333+00:00 Hello @Salini, Krovi ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand that you need help configuring the health probes for Azure Front Door and Azure Container Apps.
You can find the configuration recommendation for Container apps in the below doc:
And it says:
- Secure inbound connectivity: When publishing internet-facing services, use Azure Application Gateway (WAF_v2 SKU) or Azure Front Door (with Web Application Firewall) to secure inbound connectivity.
- Internal traffic management: Use an internal network configuration for services like Azure Application Gateway or Azure Front Door, ensuring traffic from the load-balancer to the Azure Container Apps Environment uses an internal connection.
And as mentioned in the below Microsoft blog:
Azure Container Apps ingress can be exposed on either a Public or Private IP address. One option is to put Azure Front Door in front of an ACA public endpoint, but currently there is no way (other than in application code) to restrict access to the ACA public IP address from a single Azure Front Door instance. Azure App Service Access restrictions supports this scenario, but unfortunately, there is currently no equivalent access restriction for Azure Container Apps.
To work around this limitation, Azure Private Link Service can be provisioned in front of an internal ACA load balancer. A Private endpoint (NIC with private IP in a virtual network) is connected to the Private Link Service and an Azure Front Door Premium SKU instance can then be used to connect to the private endpoint (known as a Private Origin in AFD). This configuration removes the need to inspect the value of the "X-Azure-FDID" header sent from AFD since only a single AFD instance is connected to the private endpoint, guaranteeing traffic to the ACA environment occurs only from that specific AFD instance.
Could you please confirm if your setup is as recommended above?
For Health probe configuration, please refer the below docs:
https://learn.microsoft.com/en-us/azure/container-apps/health-probes?tabs=arm-template
NOTE: In Azure Front Door, the health probe configuration is added in the Origin group settings.
Regards,
Gita
-
Salini, Krovi 0 Reputation points
2023-11-24T11:45:32.66+00:00 Thank you for your response, actually I have created health probes in container apps with some path and after that I added same path in front door but after that I receiving error for health probes in front door why I don't know front door not able to reaching my service receiving 404 error
-
GitaraniSharma-MSFT 50,106 Reputation points Microsoft Employee Moderator
2023-11-24T12:50:25.31+00:00 Hello @Salini, Krovi , I would need more details about your setup and configuration to find the cause of the issue.
- What is your Front Door configuration?
- What have you added in the origin?
- Do you have a valid route added in the Front Door?
- Are you using custom domain?
Without more information, I could only point out some possibilities.
404 - is a "Page not found" error which could be coming from the origin and simply being forwarded by the Front Door, or it could be from the Front Door due to a configuration issue.
One of the Front Door configuration issues that could cause a 404 is discussed in the below thread:
https://learn.microsoft.com/en-us/answers/questions/1194782/front-door-404-error
However, please provide more details for further discussion.
Regards,
Gita
-
GitaraniSharma-MSFT 50,106 Reputation points Microsoft Employee Moderator
2023-11-27T10:07:19.4433333+00:00 @Salini, Krovi , could you please provide an update on this issue?
-
GitaraniSharma-MSFT 50,106 Reputation points Microsoft Employee Moderator
2023-11-29T10:37:57.7866667+00:00 @Salini, Krovi , Could you please provide an update on this post?
-
GitaraniSharma-MSFT 50,106 Reputation points Microsoft Employee Moderator
2023-12-01T14:13:14.6866667+00:00 @Salini, Krovi , do you have any new updates on this issue?
Sign in to comment
Sign in to answer