Share via

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,524 questions

20 answers

Sort by: Newest
Most helpful Newest Oldest
  1. 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
  2. Kevin Rizzo 5 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!

    1 person found this answer helpful.
    0 comments
  3. Sriharsha Ramachandra 5 Reputation points
    2023-06-19T19:29:07.77+00:00

    Any known solution for this problem?

    Tried below things

    1. Restarted -- multiple times
    2. Set below mentioned Env variables as well

    App Details
    Node js Application

    Docker is exposing 8080 port
    App running on 8080 port

    gave PORT as env variable which is set to 8080 - used in App to run the server

    set WEBSITES_PORT to 8080

    gave high number for WEBSITES_CONTAINER_START_TIME_LIMIT

    Stopped and started the container multiple times

    1 person found this answer helpful.
    0 comments
  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
  5. 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.