":( Application Error If you are the application administrator, you can access the diagnostic resources." Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

Jigar Parekh 6

I'm trying to deploy a react-app to Azure webapp service using Github Actions. Although the workflow is built successfully, yet I'm getting an error ":( Application Error If you are the application administrator, you can access the diagnostic resources" when I open the url. And the Log stream show the error "Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.". The container is probably expecting some other port, but I don't know how to change the port of the container.

Ryan Hill 27,111 Reputation points Microsoft Employee

2020-08-17T15:56:57.363+00:00

Check your log stream (in kudu -> http://<yourapp>.scm.azurewebsites.net/api/LogStream) @Jigar Parekh for errors. On Linux, the host will bind the image container to port 8080. You should see a line in the log stream like:

2020-08-17T15:36:00.898Z INFO - docker run -d -p 9388:8080 --name

If there are any error messages before or after that line, the post them here. If your app is listening on a particular port e.g. server.listen(3000) then you can use WEBSITES_PORT application setting to that port to instruct the app service what port to bind to.
Aditya Reddy 1 Reputation point

2020-08-17T16:05:38.53+00:00

Hello ,

I'm seeing similar issue but the actual error in logs was . Your help is much appreciated .

/home/LogFiles/2020_08_15_RD00155D64EA13_default_docker.log (https://issuetrackingsystem-ui.scm.azurewebsites.net/api/vfs/LogFiles/2020_08_15_RD00155D64EA13_default_docker.log)

2020-08-15T23:59:40.970333228Z npm ERR! issuetrackingsystem-ui@0.1.0 start: react-scripts start
2020-08-15T23:59:40.970756547Z npm ERR! spawn ENOENT
2020-08-15T23:59:40.971284070Z npm ERR!
2020-08-15T23:59:40.971725489Z npm ERR! Failed at the issuetrackingsystem-ui@0.1.0 start script.
2020-08-15T23:59:40.972168108Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-08-15T23:59:40.979426223Z npm timing npm Completed in 276ms
2020-08-15T23:59:40.979932145Z
2020-08-15T23:59:40.980455168Z npm ERR! A complete log of this run can be found in:
2020-08-15T23:59:40.980866285Z npm ERR! /root/.npm/_logs/2020-08-15T23_59_40_973Z-debug.log
Robert Heynen 1 Reputation point

2020-09-16T16:35:27.92+00:00

I am trying to deploy through Visual code and am getting the same error/issue. I did not want containers on this but somehow it is expecting containers...is this a default setting for Azure Web Apps/ Node.js/ Linux?

I also see your npm build run comment...how do I deploy that to Azure?

The app works on my local host and has been deployed successfully in the past so I am unsure what may have changed.
Robert Heynen 1 Reputation point

2020-09-16T16:39:39.477+00:00

/home/LogFiles/2020_09_16_RD501AC525BB80_docker.log (https://slicereservationservice.scm.azurewebsites.net/api/vfs/LogFiles/2020_09_16_RD501AC525BB80_docker.log)
2020-09-16T15:45:47.127Z INFO - Stopping site slicereservationservice because it failed during startup.
2020-09-16T16:33:23.896Z INFO - Starting container for site
2020-09-16T16:33:23.900Z INFO - docker run -d -p 9607:8080 --name slicereservationservice_0_e6a8d54e -e WEBSITE_SITE_NAME=slicereservationservice -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=slicereservationservice.azurewebsites.net -e WEBSITE_INSTANCE_ID=74a00607285d883b7d8bba56c6442a95e1c75f2e7e55bc860a2aed31d56ba255 -e HTTP_LOGGING_ENABLED=1 appsvc/node:12.9_20200522.6
Robert Heynen 1 Reputation point

2020-09-16T16:39:54.647+00:00

2020-09-16T16:33:24.705Z INFO - Initiating warmup request to container slicereservationservice_0_e6a8d54e for site slicereservationservice
2020-09-16T16:33:39.847Z INFO - Waiting for response to warmup request for container slicereservationservice_0_e6a8d54e. Elapsed time = 15.1418625 sec
2020-09-16T16:33:57.244Z INFO - Waiting for response to warmup request for container slicereservationservice_0_e6a8d54e. Elapsed time = 32.5389237 sec
2020-09-16T16:34:07.341Z ERROR - Container slicereservationservice_0_e6a8d54e for site slicereservationservice has exited, failing site start
2020-09-16T16:34:07.350Z ERROR - Container slicereservationservice_0_e6a8d54e didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.
2020-09-16T16:34:07.360Z INFO - Stopping site slicereservationservice because it failed during startup.
Ishro App 0 Reputation points

2023-05-15T09:52:37.1766667+00:00

I have React app, Working fine in localhost:3000 and google cloud app engine! https://ola.afkkarr.com/

When trying to deploy Azure "App service" using VS code.

Deployed Successful. But the site not working!

Error:

:( Application Error

If you are the application administrator, you can access the diagnostic resources.

https://vendor-portal-frontend-web.scm.azurewebsites.net/api/logs/docker
Ryan Hill 27,111 Reputation points Microsoft Employee

2023-05-17T03:40:07.7833333+00:00

@Ishro App , when you get an application error message like the one above, it means there was an issue with application startup. In order to determine the cause, you have to access the logs.

Normally, the platform will bind to a port forward the HTTP requests. If this fails due to an application startup failure, you'll receive a message like this. So, check the logs for any startup failures.

2 answers

Ryan Hill 27,111 Reputation points Microsoft Employee

2020-08-18T17:54:20.693+00:00

@Aditya Reddy The react scripts from your package.json are not on the app service host. To get around this, deploy the build folder that gets created/updated when you run npm run build. If you're using CI/CD, make sure you copy the contents of /build to an artifacts directory that will be used later for publishing.

This may resolve your issue as well @JigarParkeh-6598. If not, please include any log information from your app service.
Please sign in to rate this answer.
Prasanna Tuladhar 0 Reputation points

2024-02-28T21:00:08.52+00:00

I am using CI/CD and i have the issues mentioned above. How do I copy the contents of /build to an artifacts directory?
Sign in to comment
Utku Elhan 1 Reputation point

2021-09-03T11:56:52.92+00:00

I having a similar problem but the actual error in logs was like followings. Thank you in advance.

2021-09-03T11:21:57.847Z ERROR - Container fy22internwebapp_0_d753b068 for site fy22internwebapp has exited, failing site start
2021-09-03T11:21:57.852Z ERROR - Container fy22internwebapp_0_d753b068 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.
2021-09-03T11:21:57.855Z INFO - Stopping site fy22internwebapp because it failed during startup.
2021-09-03T11:24:14.662Z INFO - Starting container for site
2021-09-03T11:24:14.663Z INFO - docker run -d -p 9109:8000 --name fy22internwebapp_0_5ecdf76f -e WEBSITE_SITE_NAME=fy22internwebapp -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=fy22internwebapp.azurewebsites.net -e WEBSITE_INSTANCE_ID=7571d6c587badd556f121600341391499495b95be08b041b7155690115b6bddc -e HTTP_LOGGING_ENABLED=1 appsvc/python:3.7_20210709.2

2021-09-03T11:24:18.289Z INFO - Initiating warmup request to container fy22internwebapp_0_5ecdf76f for site fy22internwebapp
2021-09-03T11:24:25.121Z ERROR - Container fy22internwebapp_0_5ecdf76f for site fy22internwebapp has exited, failing site start
2021-09-03T11:24:25.128Z ERROR - Container fy22internwebapp_0_5ecdf76f didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.
2021-09-03T11:24:25.132Z INFO - Stopping site fy22internwebapp because it failed during startup.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

":( Application Error If you are the application administrator, you can access the diagnostic resources." Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

2 answers