Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
625 questions
"startup probe failed: connection refused" on Azure Container App with Azure Files volume
![](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(160, 83%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDC%3C/text%3E%3C/svg%3E)
Daniel Cuellar
0
Reputation points
I have an Azure Container App that is a Web API in .NET 6 and has a volume associated with Azure Files to the /app/wwwroot folder and for a few weeks now when trying to start a new review it throws the error "startup probe failed: connection refused" and that configuration had been working for a year, the source code is functional, the Docker image compiles well and uploads to the Container Registry, the volume configuration has not changed, it works fine locally, it only fails when starting the review in Azure, why is it failing now?
Azure Container Apps
{count} votes
-
![](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(57.599999999999994, 5%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Praveen Kumar Gudipudi 170 Reputation points Microsoft External Staff2025-04-21T21:20:07.4366667+00:00 Hello Daniel Cuellar,
Could you please check the private message and provide the required details for troubleshooting the issue further.
-
Daniel Cuellar 0 Reputation points
2025-04-21T22:25:31.9666667+00:00 Hi, response sent
-
Praveen Kumar Gudipudi 170 Reputation points Microsoft External Staff
2025-04-23T18:08:54.4166667+00:00 Hello Daniel Cuellar,
Could you please provide logs from log analytic workspace to identify root cause.
-
Daniel Cuellar 0 Reputation points
2025-04-23T22:47:18.11+00:00 Hi @Praveen Kumar Gudipudi , in a private message, I'm sharing an exported file of the logs from the ContainerAppSystemLogs_CL table during a patch startup test with the associated Azure Files volume. Change the file extension from .csv to .txt so you can upload the file.
-
Praveen Kumar Gudipudi 170 Reputation points Microsoft External Staff
2025-04-24T21:59:35.7133333+00:00 Hello Daniel Cuellar,
I can see ReplicaUnhealthy status in logs. Common Causes and Solutions:
I understand that you are having Startup probe failed error for your container app.
https://learn.microsoft.com/en-gb/answers/questions/2118109/startup-probe-failed
please check above document and if this issue still persistent please let us know.
-
Daniel Cuellar 0 Reputation points
2025-04-25T19:46:32.3233333+00:00 Hi, I set the maximum possible values for the startup probe, and the revision doesn't work. I'm sharing the configuration and logs in the private messages.
-
Praveen Kumar Gudipudi 170 Reputation points Microsoft External Staff
2025-04-28T19:15:08.75+00:00 Hello Daniel Cuellar,
Ensure your startup probe is defined correctly in your configuration file (YAML or equivalent). Here is an example:
Please check the below document: https://learn.microsoft.com/en-us/azure/container-apps/health-probes?tabs=arm-template
startupProbe: httpGet: path: /health port: <your-port-number> initialDelaySeconds: 30 periodSeconds: 10 failureThreshold: 3 -
Daniel Cuellar 0 Reputation points
2025-04-29T13:50:33.89+00:00 Hi, we configure the application from the Portal, not from the console, to use templates.
The "startup probe" configuration sent is correct: the application is configured with HTTP, port 80, the route is a valid endpoint that responds with 200, and the other values are allowed.
We understand that Azure internally sets default configurations, but as mentioned above, the application has been running with that default internal configuration for a year.
Keep in mind that the error occurs when setting the "Azure Files volume" because without it, the application launches without problems.
On the service's GitHub, we found bugs related to this error where the Azure Files volume issue is present:
- https://github.com/microsoft/azure-container-apps/issues/1425
- https://github.com/microsoft/azure-container-apps/issues/1423
I would appreciate it if you could validate whether it is a bug in Azure or what alternatives we can implement.
-
Daniel Cuellar 0 Reputation points
2025-05-02T12:59:02.7166667+00:00 Hi @Praveen Kumar Gudipudi, any news?
Sign in to comment
Sign in to answer