Hi Sujith Mohan,
In addition to Alex Burlachenko response,
- Go to Azure Portal > App Service > Restart to clear any temporary glitches. If the error persists, navigate to App Service > Diagnose and solve problems and clear the server-side cache.
- In Azure Portal > Configuration, ensure all environment variables are correctly set, including connection strings, keys, and any settings related to Managed Identity or User Delegation SAS for Azure Storage access. Misconfigured settings are a common cause after deployment.
- Verify the startup command under Configuration > General settings. Ensure it's pointing to the correct entry point (e.g., dotnet <YourApp>.dll for .NET Core apps). Incorrect startup commands often lead to application errors.
- Since Kudu is inaccessible, use Azure Portal > App Service > SSH to access the container. Check logs under /home/LogFiles for detailed error messages. This helps identify startup or dependency issues. (refer below link)
- If no configuration issues are found, redeploy the application to ensure the deployment artifacts aren't corrupted. After redeployment, restart the App Service.
If you have any further assistant, do let me know.
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.