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

Noa 71 Reputation points
2020-11-19T17:39:01.323+00:00

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

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,427 questions
{count} votes

20 answers

Sort by: Most helpful
  1. Solecki, Grzegorz 0 Reputation points
    2023-03-29T20:23:59.6133333+00:00

    I do have the same issue with standard Spring Boot Application.

    Any solutions?

    0 comments No comments

  2. Nick Mertzanis 0 Reputation points
    2023-03-31T12:23:32.3666667+00:00

    For me what ended up working was simply restarting the web application. Not re-deploying but restarting

    Also make sure DEBUG=TRUE for some reason in your settings file

    0 comments No comments

  3. Noah Tucker 0 Reputation points
    2023-04-09T16:51:00.5+00:00

    I am having the same issue trying to deploy a Python Flask app that is using port 5000.


  4. Yaroslav Yakushev 0 Reputation points
    2023-05-23T21:26:14.6566667+00:00

    I had the same problem with the Keystone 6 (node.js) application. I've tried to deploy it using the Azure web app as code and as a docker container but with the same result: container X didn't respond to HTTP pings. Changing configuration settings PORT and WEBSITES_PORT, as well as EXPOSE in a Dockerfile gave nothing.

    Finally, I solved the problem by deploying the application as a container using the pm2 as a server wrapper instead of starting the application with npm as recommended by Microsoft https://learn.microsoft.com/en-us/azure/app-service/configure-language-nodejs?pivots=platform-linux#configure-nodejs-server

    pm2-runtime --delay 30 'npm start'
    

    Hope that it helps.

    0 comments No comments

  5. Pasalapudi, Rajasekhar 0 Reputation points
    2024-07-09T09:36:58.1333333+00:00

    Use the App settings as PORT 3000 instead of WEBSITES_PORT.

    0 comments No comments