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

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

Thanks for your Answer. The Application is responding in a SSH Session with a HTTP 200 OK (curl 127.0.0.1:8080). But from external the App isn't responding. Can you give me any advice on other Plattforms i don't find any answer thats seems to work. The node.js Application is binded on 0.0.0.0

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.

We have the same issue. The container suddenly fails to restart after being online for a while and then never starts.

Have tried to set the WEBSITES_PORT (and/or) PORT to 8080 and we are exposing 8080 in our Dockerfile.

The image works perfectly locally.

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