I have deployed an application in azure web app service. But while accessing the url i am getting application error .

Question

I have deployed a containerized application in azure web app service. The deployment was successful .But while accessing the url, the webpage is displaying application error . The error says :

The resource was not found, it may have been deleted. If this was launched from a pinned tile on the dashboard, it should be removed. Resource ID: /subscriptions/83130aba-cb89-4f7e-b969-23e91bb6029f/resourceGroups/myresourcegroup/providers/Microsoft.Web/sites/botperf/slots/h4fcbnbmcpfsbrht Status Code: 404 Status Message: The Resource 'Microsoft.Web/sites/botperf/slots/h4fcbnbmcpfsbrht' under resource group 'myresourcegroup' was not found.

Every resources are present in my resource group" Myresourcegroup" . Nothing is deleted or renamed. I have a container registry, blob storage container and this azure app service web app under this resource group.

Answer 1

Hello Aswathi Anil,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are having error with Status Code: 404 Status Message: The Resource 'Microsoft.Web/sites/botperf/slots/h4fcbnbmcpfsbrht' under resource group 'myresourcegroup' was not found while accessing the url of your web app, despite the fact you have other resources like Azure Blob et al in the Resources Group.

The 404 error with the resource not found message usually occurs due to the following:

1. Misconfigured deployment slot or routing.
2. Missing or incorrect resource references in the configuration.
3. DNS or mapping issues for the custom domain or default Azure URL.

The below are the steps to resolve the issue: 1

1. First, confirm that the deployment slot h4fcbnbmcpfsbrht exists and is active as a Resource exists by Go to the Azure Portal and navigate to > Resource Group > App Service > Deployment Slots.
2. Secondly, under Deployment Slots, check that traffic is routed correctly to the slot (h4fcbnbmcpfsbrht) if you're accessing the slot URL directly and verify whether the slot is configured to swap traffic with the production slot.
3. Also, validate the Web App Configuration by Go to the Configuration section of your Azure Web App Service and check, make sure correct container registry URL and credentials are configured and correct paths for the app.
4. Also, inspect Logs such as Log Stream from the Azure portal to view real-time application logs, then enable Application Logging and Container Logging to check if the container failed to start.
5. Fifth, if accessing via a custom domain, ensure the domain is correctly mapped to the App Service. Use Diagnose and Solve Problems > DNS Validation. For the default Azure URL, confirm no issues with the FQDN (e.g., botperf.azurewebsites.net).
6. Finally, if configurations and logs show no issues, redeploy the container using az webapp create or directly from the container registry. After making the changes, access the slot URL and validate whether the 404 error persists.

This is an alternative step to take if the issue persists:

• Manually Recreate the Slot by delete and recreate the deployment slot if misconfiguration is suspected, reconfigure traffic routing and redeploy the container, enable App Service Diagnostic Tools, use the Diagnose and Solve Problems feature to identify deployment slot-specific issues.
• Then, contact Azure Support via your Portal.

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Answer 2

Hello Aswathi Anil,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
The error you're encountering indicates that Azure is unable to locate the specified resource (Microsoft.Web/sites/botperf/slots/h4fcbnbmcpfsbrht).

Confirm that the slot (h4fcbnbmcpfsbrht) exists in your Azure Web App.

Navigate to App Service > Deployment slots and ensure the slot is correctly listed.

Ensure the URL points to the correct deployment slot.

If accessing a non-default slot, use the format: https://<app-name>-<slot-name>.azurewebsites.net.

Check the diagnostics logs for any errors or misconfigurations.

Go to App Service > Monitoring > Log stream or enable Application Insights for detailed insights.

Review App Service diagnostics for slot/container configuration issues.

Ensure the container is correctly deployed and running.

Go to App Service > Container settings and verify the container image.

Check Container logs under App Service > Logs for any runtime issues.

Verify that there are no permission issues preventing resource access.

Ensure proper Azure Active Directory (AAD) or RBAC permissions are set for the resource group.

A restart may help resolve any transient issues.

Restart the App Service from the Azure portal.

If the answer is helpful, please click ACCEPT ANSWER and kindly upvote it.