:( Application Error

[ttbush]

:( Application Error If you are the application administrator, you can access the diagnostic resources.

I recently tried deploying a project on Azure App Service through a one-click deployment from GitHub. However, I'm encountering an error during the startup of the service:

2023-08-07T05:17:04.709273528Z 2023-08-07T05:17:04.712456057Z / \ __ ___ ___ 2023-08-07T05:17:04.712468257Z / /\ \_ / | _ _/ \ 2023-08-07T05:17:04.712473857Z / | \/ /| | /| | \/\ / 2023-08-07T05:17:04.712477957Z __| /__ __/ |_| \ > 2023-08-07T05:17:04.712482057Z \/ \/ \/ 2023-08-07T05:17:04.712486157Z A P P S E R V I C E O N L I N U X 2023-08-07T05:17:04.712490257Z 2023-08-07T05:17:04.712494357Z Documentation: http://aka.ms/webapp-linux 2023-08-07T05:17:04.712498557Z NodeJS quickstart: https://aka.ms/node-qs 2023-08-07T05:17:04.712502257Z NodeJS Version : v18.16.0 2023-08-07T05:17:04.712505957Z Note: Any data outside '/home' is not persisted 2023-08-07T05:17:04.712509757Z 2023-08-07T05:17:04.913114427Z Starting OpenBSD Secure Shell server: sshd. 2023-08-07T05:17:04.947974835Z Starting periodic command scheduler: cron. 2023-08-07T05:17:04.954004788Z Cound not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml' 2023-08-07T05:17:04.954215690Z Could not find operation ID in manifest. Generating an operation id... 2023-08-07T05:17:04.954432492Z Build Operation ID: a3c3cf80-71c0-4bc2-ae4e-c0e57fa9d32c 2023-08-07T05:17:05.107466342Z Environment Variables for Application Insight's IPA Codeless Configuration exists.. 2023-08-07T05:17:05.158724795Z Writing output script to '/opt/startup/startup.sh' 2023-08-07T05:17:05.241667726Z Running #!/bin/sh 2023-08-07T05:17:05.241858328Z 2023-08-07T05:17:05.241872128Z # Enter the source directory to make sure the script runs where the user expects 2023-08-07T05:17:05.241878628Z cd "/home/site/wwwroot" 2023-08-07T05:17:05.241883828Z 2023-08-07T05:17:05.241888728Z export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH 2023-08-07T05:17:05.241893528Z if [ -z "$PORT" ]; then 2023-08-07T05:17:05.241898428Z export PORT=8080 2023-08-07T05:17:05.241904129Z fi 2023-08-07T05:17:05.241908229Z 2023-08-07T05:17:05.251246511Z PATH="$PATH:/home/site/wwwroot" node server.js 2023-08-07T05:17:05.343407024Z node:internal/modules/cjs/loader:1078 2023-08-07T05:17:05.343467825Z throw err; 2023-08-07T05:17:05.343477025Z ^ 2023-08-07T05:17:05.343482325Z 2023-08-07T05:17:05.343487225Z Error: Cannot find module '/home/site/wwwroot/server.js' 2023-08-07T05:17:05.343491725Z at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15) 2023-08-07T05:17:05.343496025Z at Module._load (node:internal/modules/cjs/loader:920:27) 2023-08-07T05:17:05.343500125Z at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2023-08-07T05:17:05.343517225Z at node:internal/main/run_main_module:23:47 { 2023-08-07T05:17:05.343532125Z code: 'MODULE_NOT_FOUND', 2023-08-07T05:17:05.343536625Z requireStack: [] 2023-08-07T05:17:05.343540925Z } 2023-08-07T05:17:05.343621026Z 2023-08-07T05:17:05.343633926Z Node.js v18.16.0 2023-08-07T05:17:04.326Z INFO - 18-lts_20230502.1.tuxprod Pulling from appsvc/node 2023-08-07T05:17:04.328Z INFO - Digest: sha256:b1dc34abcaac6f00dd945840a5bc6367123b63b56465a5ec20c316eca98e569e 2023-08-07T05:17:04.329Z INFO - Status: Image is up to date for mcr.microsoft.com/appsvc/node:18-lts_20230502.1.tuxprod 2023-08-07T05:17:04.332Z INFO - Pull Image successful, Time taken: 0 Minutes and 0 Seconds 2023-08-07T05:17:04.342Z INFO - Starting container for site 2023-08-07T05:17:04.343Z INFO - docker run -d --expose=8080 --name mmgchatgpt-app-ekefg2g2a57xe_0_5c14d46b -e WEBSITE_SITE_NAME=mmgchatgpt-app-ekefg2g2a57xe -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=mmgchatgpt-app-ekefg2g2a57xe.azurewebsites.net -e WEBSITE_INSTANCE_ID=0f8bc5d9c5b2341c0b55ca041f95daa510fb3166fa4f873a130341dda37c34af -e HTTP_LOGGING_ENABLED=1 -e WEBSITE_USE_DIAGNOSTIC_SERVER=True appsvc/node:18-lts_20230502.1.tuxprod node server.js 2023-08-07T05:17:04.821Z INFO - Initiating warmup request to container mmgchatgpt-app-ekefg2g2a57xe_0_5c14d46b for site mmgchatgpt-app-ekefg2g2a57xe 2023-08-07T05:17:05.840Z ERROR - Container mmgchatgpt-app-ekefg2g2a57xe_0_5c14d46b for site mmgchatgpt-app-ekefg2g2a57xe has exited, failing site start 2023-08-07T05:17:05.847Z ERROR - Container mmgchatgpt-app-ekefg2g2a57xe_0_5c14d46b didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. 2023-08-07T05:17:05.850Z INFO - Stopping site mmgchatgpt-app-ekefg2g2a57xe because it failed during startup.

[shohei1029]

+1 I faced the same error.

[murdockcrc]

+1, facing this same issue after using the "Deploy to Azure" button.

[KoheiYamamoto]

+1 faced same here; it says having a problm at startup.

[aawaheed]

"Deploy to Azure" button only creates the infrastructure. The next step is to fork and deploy your app using GitHub Actions as mentioned by @oliverlabs in https://github.com/microsoft/azurechatgpt/issues/49#issuecomment-1665831443

[shohei1029]

Thank you for sharing that. I've created a PR to solve the confusion. https://github.com/microsoft/azurechatgpt/pull/71

[murdockcrc]

@shohei1029 , gotcha, that makes sense. Thx for clarifying and adjusting the README.

[thivy]

Thank you all for helping fix this issue.

We will update the documentation to avoid the confusion between Provisioning Azure resources vs Build and Deploy to Azure.

[shohei1029]

@thivy Thanks a lot! As a temporary remedy, could you please approve the PR here? https://github.com/microsoft/azurechatgpt/pull/71