Container ... initialized successfully and is ready to serve requests. But when access web app show nginx page

Question

Dear All, I'm try to run my container for my laravel app in Azure wep app , and i already received below message : Pull Image successful, Time taken: 0 Seconds 2024-02-01T08:01:42.648Z INFO - Starting container for site 2024-02-01T08:01:42.649Z INFO - docker run -d --expose=80 --name supplylocalapp_1_165c19a4 -e WEBSITE_USE_DIAGNOSTIC_SERVER=false -e WEBSITES_ENABLE_APP_SERVICE_STORAGE=false -e WEBSITE_SITE_NAME=supplylocalapp -e WEBSITE_AUTH_ENABLED=False -e PORT=80 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=supplylocalapp.azurewebsites.net -e WEBSITE_INSTANCE_ID=ad51c3df8464631de8638f6da9738f5e365f2fd683aec2a7dea46284aa8922f7 -e HTTP_LOGGING_ENABLED=1 .../supply:latest 2024-02-01T08:01:43.492Z INFO - Initiating warmup request to container supplylocalapp_1_165c19a4 for site supplylocalapp 2024-02-01T08:01:43.494Z INFO - Container supplylocalapp_1_165c19a4 for site supplylocalapp initialized successfully and is ready to serve requests.

However when i try to access web app , it show only nginx page but on my local machine it working as normal. Please kindly help!! Thanks

Answer 1

@Rathanak Bun (DHL KH) Thank you for the additional information. To access the logs for your container in Azure Web App, you can use the Azure portal or the Azure CLI. To access the logs using the Azure portal, you can follow these steps: Go to the Azure portal and select your web app. Navigate to the "Logs" tab. Select "Container logs" from the dropdown menu. You should now see the logs for your container. You can use the search bar to filter the logs by keyword or time range.

To access the logs using the Azure CLI, you can use the following command:

az webapp log container show --name <your-web-app-name> --resource-

This command will show the logs for your container in the Azure CLI. If you are still having trouble accessing your Laravel app, you can try running the container locally on your machine using the same Dockerfile and startup command. This can help you identify any issues with your Dockerfile or startup command. You can also try checking the logs for your container to see if there are any error messages that might indicate the cause of the issue.