Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

Noa 76

I have deployed an App Service via Github Workers with node.js now i have the problem, that the node.js Application is running, but the Ports is not exposing. Can everyone give me an advice or is it possible to deactivate HTTP pings? Logs: 2020-11-19T16:19:27.439Z INFO - Initiating warmup request to container X for site X 2020-11-19T16:19:43.733Z INFO - Waiting for response to warmup request for container X. Elapsed time = 16.2938836 sec 2020-11-19T16:23:27.969Z ERROR - Container Xf for site X did not start within expected time limit. Elapsed time = 240.5298169 sec 2020-11-19T16:23:27.970Z ERROR - Container X didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. 2020-11-19T16:23:27.980Z INFO - Stopping site X because it failed during startup. Kind regards, Noah

Anonymous

2023-03-31T12:13:52.47+00:00

For me what ended up working was simply restarting the web application after setting DEBUG to TRUE
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
J. Victor Ferreira 15 Reputation points

2024-06-10T17:31:38.0333333+00:00

After so much effort, I found someone who suggested a fix that actually worked.

You container has to have a default response of 404. This means if someone tries to get to a page or resource that doesn't exist in your service, make it respond with a 404.

Apparently, Azure pings your container by trying to access a random resource and expects your service to respond with 404. If that doesn't help, the container is deemed as unusable.

Hope it helps other people to not have to go through the wild goose chase so many people in this thread had to go through.

Microsoft. Come on! That could have been documented or clearer from the error message.

20 answers

neas 121 Reputation points

2022-04-22T18:48:36.287+00:00

I can confirm that this is really a nightmare. I have followed the tutorial here: https://learn.microsoft.com/en-us/azure/developer/javascript/tutorial/tutorial-vscode-docker-node/tutorial-vscode-docker-node-04 with my custom node js app without success. Also the WEBSITES_PORT setting is not helping at all. Why do I have to waste more than a whole day for deploying an app in Azure?? And it's still not working!
Was this answer helpful?

10+ people found this answer helpful.
Rahul Shokeen 0 Reputation points

2023-12-20T08:13:18.4333333+00:00

Check your docker file and comment out,

# ENV PORT # ENV HOSTNAME # EXPOSE

This will allow the web app to dynamically map the port

Niral Patel 5 Reputation points

2024-01-27T21:47:49.57+00:00

This is incredibly frustrating. Also experiencing the same issue on such a simple deployment.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
marc 101 Reputation points

2021-12-17T10:01:52.527+00:00

I have switched to Aws instead, all the port configuration is as simple as doing network inbound rules, instead of playing around with these unexplained WESITE_PORT
Was this answer helpful?

10 people found this answer helpful.
Vibhor Agarwal 10 Reputation points

2024-10-04T10:29:36.1966667+00:00

MS documentation and console is awful!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Wahbi, Hicham 31 Reputation points

2021-12-19T13:02:56.097+00:00

deploying a node app to app service is really a nightmare. I have the same symptoms above and have been trying to resolve for the last couple of weeks with no success.
Was this answer helpful?

6 people found this answer helpful.
Anonymous

2023-03-31T12:14:02.99+00:00

For me what ended up working was simply restarting the web application
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Kevin Rizzo 15 Reputation points

2023-12-14T14:42:04.28+00:00

I saw this problem as well, and the issue turned out to be me building images locally on my Mac M1. In App Service, containers are likely using the x64 architecture instead of ARM. I fixed the issue by forcing docker to build for linux-amd64 (--platform linux-amd64) when pushing to my remote registry. After that, I was able to start up fine.

That being said, the UX could be better here. It's fairly trivial to get the architecture of an image in a registry. App Service could alert you that it was built using the incorrect architecture for a better debugging experience.

Hope this helps others!
Was this answer helpful?

3 people found this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Kapilan Koch 0 Reputation points

2025-06-19T15:44:37.73+00:00

This is a really good hint! Thanks @Kevin Rizzo
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
SnehaAgrawal-MSFT 22,721 Reputation points Moderator

2020-11-20T08:12:39.197+00:00
Thanks for asking question! You may want to know that If your container takes a long time to start you can increase the start time limit. The default time is 230 seconds for starting the container. To configure that, add an app setting called WEBSITES_CONTAINER_START_TIME_LIMIT and set it to the number of seconds you would like for us to wait for your container to start (up to a maximum of 1800) as shown in the image below:

Also please ensure that your container must respond to an HTTP ping and In order for us to consider a container to be successfully started, the container must start and it must respond to an HTTP ping. If the container starts but does not respond to a ping, we will eventually log an event in the Docker log saying that it didn't start.

To resolve this.
1. Use the EXPOSE instruction in your Dockerfile to expose port 3000.
2. Use the WEBSITES_PORT app setting with a value of "3000" to expose that port.
Reference: https://techcommunity.microsoft.com/t5/apps-on-azure/things-you-should-know-web-apps-and-linux/ba-p/392472
Was this answer helpful?

3 people found this answer helpful.
Darshani Jayasekara 1 Reputation point

2021-08-18T14:36:17.063+00:00

Hey, Thanks a lot, WEBSITES_PORT saved me. After struggling a lot finally found your answer. thanks again

Nicolai Linde 6 Reputation points

2023-03-23T13:20:58.6833333+00:00

What if I don't want to run a website, just signalr?

Venkateswarlu Swarna 0 Reputation points

2023-03-30T10:16:21.5033333+00:00

Thanks to you!... This is very Helpful for me, finally it's working

Satya 20 Reputation points

2023-05-31T00:39:16.93+00:00

I am deploying code.. so i cant really set the Expose variable in docker container. And WEBSITES_PORT does not solve the problem. Any other ideas?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

20 answers

Your answer