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!
Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.
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
20 answers
Sort by: Most helpful
-
-
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
-
Wahbi, Hicham 26 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.
-
SnehaAgrawal-MSFT 21,006 Reputation points
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.
- Use the EXPOSE instruction in your Dockerfile to expose port 3000.
- Use the WEBSITES_PORT app setting with a value of "3000" to expose that port.
-
marc 101 Reputation points
2021-08-14T23:23:11.327+00:00 I am facing the same problem, saying my node js port 3000 can not be ping so the container exit even I have done following
Use the EXPOSE instruction in your Dockerfile to expose port 3000.
Use the WEBSITES_PORT app setting with a value of "3000" to expose that port.have seen many other posts out there suggesting same solution, but setting WEBSITES_PORT does not work. My image works perfectly locally..
2021-08-14T23:01:18.250Z INFO - Logging is not enabled for this container.
Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here.
2021-08-14T23:01:20.821Z INFO - Initiating warmup request to container xxxx for site xxxx
2021-08-14T23:01:20.832Z INFO - Container xxxxx for site xxxx initialized successfully and is ready to serve requests.
2021-08-14T23:01:20.832Z INFO - Initiating warmup request to container xxx for site xxx
2021-08-14T23:01:21.875Z ERROR - Container xxx for site xxx has exited, failing site start
2021-08-14T23:01:21.877Z ERROR - Container xxx didn't respond to HTTP pings on port: 3000, failing site start. See container logs for debugging.
2021-08-14T23:01:21.889Z INFO - Stopping site xxx because it failed during startup.