Webapp returns 500 error but runs locally

Akeem Afuwape 0 Reputation points
2024-03-14T06:07:14.83+00:00

My WebAPP deploys fine and the stream shows all is well. But the page keeps returning Internal Error.

I have moved from Botframework to Quart and the problem still remains. Worked through by line and I don't see what I am doing wrong especially since it runs fine locally.

I did SSH into the app and at least the startup command works fine there too. I am 48 hrs into this and would appreciate any insights.

docker run -d --expose=8000 --name project-jarvis-rag_0_8aab0da4 -e WEBSITE_USE_DIAGNOSTIC_SERVER=false -e WEBSITE_SITE_NAME=project-jarvis-rag -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=project-jarvis-rag.azurewebsites.net -e WEBSITE_INSTANCE_ID= XXXXX appsvc/python:3.10_20240207.3.tuxprod gunicorn --bind 0.0.0.0:8000 app:app
2024-03-14T05:59:37.080Z INFO  - Initiating warmup request to container project-jarvis-rag_0_8aab0da4 for site project-jarvis-rag
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,830 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 18,021 Reputation points Microsoft Employee
    2024-03-14T06:50:57.2+00:00

    @Akeem Afuwape Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

    Based on the shared information, I have looked the backend logs of your app service (prot-rag) We can see couple of 500 errors and also your site is unable to start and it is getting timed out.

    • Could you please add this application setting WEBSITES_CONTAINER_START_TIME_LIMIT of value 1800 to avoid the time out.
    • Also regarding 500 error this is common error which can occurs due to many reasons. I would suggest you to enable the application logs and review them to understand more about it.

    Alternatively, you can run the WebApp Down detector in Availability and Performance under Diagnose and Solve Problems Blade of your webapp to know more about the issue/ for initial troubleshooting.

    Hope this helps and let me know if you have any further questions on this.