Azure App Service Container Didn't Respond to HTTP Pings / Fails to Start
Quick answer
Custom containers fail when the warmup request times out, the port is wrong or host disk is full. Set WEBSITES_PORT and raise WEBSITES_CONTAINER_START_TIME_LIMIT.
Most likely fix: Fix the port
How to fix it
Try these in order — the most common fix is first.
1. Fix the port
- Set the WEBSITES_PORT app setting to the port your container listens on
- Built-in images: read the PORT environment variable
Did this fix it?2. Give it more startup time
- Add WEBSITES_CONTAINER_START_TIME_LIMIT with a value between 240 and 1800 seconds
Did this fix it?3. Fix the warmup request
- Make the app answer /robots933456.txt with any status code, or set WEBSITE_WARMUP_PATH and WEBSITE_WARMUP_STATUSES
Did this fix it?4. No space left on device
- Keep images small and write data under /home or a mounted Azure Storage path
- Split the App Service plan if host disk is shared by many containers
Did this fix it?
Symptoms
App Service on Linux keeps restarting your container, shows an application error, or reports 'no space left on device'.
Why it happens
- Container listens on a port other than 80 or 8080 without WEBSITES_PORT
- App does not answer the warmup request, so the container restarts forever
- Slow startup exceeds the default 230 to 240 second limit
- 15 GB host disk limit per instance exceeded
- SQLite or file locks on the network-mounted /home
This guide also covers
- azure app service application error
- azure web app container didn't respond to http pings
- azure app service container failed to start
- websites_port azure
Still not working?
If Azure keeps failing, you're not alone. See every Azure problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Azure errors
- Azure Subscription Disabled: Spending Limit Reached
- Azure Free Account Ended: Credit Expired, Subscription Disabled
- Azure Error: Operation results in exceeding quota limits of Core
- Azure App Service HTTP 503 Service Unavailable / 502 Bad Gateway
- Azure Error: The client does not have authorization to perform action (AuthorizationFailed)
- Azure Unexpected Charges: How to Find What Is Costing You Money
- How to Cancel and Delete an Azure Subscription
- Azure Subscription Disabled: Payment Wasn't Received