Container App does'nt run when Deploying using V=16.0.0

[Sreekanth11reddy]

Iam trying to deploy the solution for the first time in my Free Trial and always see the Container App never run and it throws couple of errors. Should i use latest version to make the solution run in Azure?

[Clémence Lesné (clemlesne)]

Hello, Indeed it’s important to use the latest version. Once you’ll tried with it, if you have more errors, feel free to share them in the issue :) Regards, Clémence LESNÉ (she/her) On Mon, Mar 10, 2025 at 12:05, Sreekanth11reddy ***@***.***> wrote: Iam trying to deploy the solution for the first time in my Free Trial and always see the Container App never run and it throws couple of errors. Should i use latest version to make the solution run in Azure? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Sreekanth11reddy]

Thanks a lot for your quick response. Ive tried installing latest release and cant access my container app and is getting below error: {"error":{"message":"Not Found","details":[]}}

[Clémence Lesné (clemlesne)]

Can you detail every steps you followed? Plus, detail the command you can to get that result. Regards, Clémence LESNÉ (she/her) On Mon, Mar 10, 2025 at 18:08, Sreekanth11reddy ***@***.***> wrote: Thanks a lot for your quick response. Ive tried installing latest release and cant access my container app and is getting below error: {"error":{"message":"Not Found","details":[]}} — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[Sreekanth11reddy]

I'm setting up the environment using GitHub Codespaces and following these steps:

1. Copy "config-remote-example.yaml" to the root folder and rename it to "config.yaml". Since I'm using an Azure Free Trial, I can't create a phone number, so I'm leaving the phone number field in "config.yaml" as-is or using a dummy value.
2. Running the command "make deploy name=our-rg-name image_version=17.2.1"
   After executing this, I see the following logs:
   🚀 Call Center AI is running on https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io
   make[1]: Entering directory '/workspaces/call-center-ai'
   make[2]: Entering directory '/workspaces/call-center-ai'
   📦 Copying public resources...
   az storage blob upload-batch
   --account-name ourrgname
   --auth-mode login
   --destination '$web'
   --no-progress
   --output none
   --overwrite
   --source public
   make[2]: Leaving directory '/workspaces/call-center-ai'
   make[2]: Entering directory '/workspaces/call-center-ai'
   ⚙️ Registering Twilio webhook...
   twilio phone-numbers:update null
   --sms-url https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io/twilio/sms
   » There is no active profile set.
   » To activate the profile, run:

twilio profiles:use
make[2]: *** [Makefile:185: twilio-register] Error 1
make[2]: Leaving directory '/workspaces/call-center-ai'
make[1]: *** [Makefile:158: deploy-post] Error 2
make[1]: Leaving directory '/workspaces/call-center-ai'
make: *** [Makefile:135: deploy] Error 2

The container app setup completes without errors, but when I try to open "https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io" in a browser, I encounter the following issue:

Since I don't have a phone number for testing, I'm unsure how to validate my deployment. One approach I considered was simply opening the container app in a browser to see if it's functioning correctly.

Thanks a lot for your support.

[Clémence Lesné (clemlesne)]

The API response seems correct. Try adding a “/report” path? Regarding to the application usability, it must work with a phone number. This is the purpose of the app! Regards, Clémence LESNÉ (she/her) On Tue, Mar 11, 2025 at 05:54, Sreekanth11reddy ***@***.***&gt; wrote: I'm setting up the environment using GitHub Codespaces and following these steps: Copy "config-remote-example.yaml" to the root folder and rename it to "config.yaml". Since I'm using an Azure Free Trial, I can't create a phone number, so I'm leaving the phone number field in "config.yaml" as-is or using a dummy value. Running the command "make deploy name=our-rg-name image_version=17.2.1" After executing this, I see the following logs: 🚀 Call Center AI is running on https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io make[1]: Entering directory '/workspaces/call-center-ai' make[2]: Entering directory '/workspaces/call-center-ai' 📦 Copying public resources... az storage blob upload-batch --account-name ourrgname --auth-mode login --destination '$web' --no-progress --output none --overwrite --source public make[2]: Leaving directory '/workspaces/call-center-ai' make[2]: Entering directory '/workspaces/call-center-ai' ⚙️ Registering Twilio webhook... twilio phone-numbers:update null --sms-url https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io/twilio/sms » There is no active profile set. » To activate the profile, run: twilio profiles:use make[2]: *** [Makefile:185: twilio-register] Error 1 make[2]: Leaving directory '/workspaces/call-center-ai' make[1]: *** [Makefile:158: deploy-post] Error 2 make[1]: Leaving directory '/workspaces/call-center-ai' make: *** [Makefile:135: deploy] Error 2 The container app setup completes without errors, but when I try to open "https://call-center-ai.gentlemushroom-f9039ac4.swedencentral.azurecontainerapps.io" in a browser, I encounter the following issue: image.png (view on web) Since I don't have a phone number for testing, I'm unsure how to validate my deployment. One approach I considered was simply opening the container app in a browser to see if it's functioning correctly. Thanks a lot for your support. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***&gt; </blockquote>