@Syed (MS Admin) Thanks for posting your query on Microsoft Q&A.
You are seeing this error : 500.30 In-Process Startup Failure while hosting your website through IIS Manager on Azure Virtual Server - The worker process fails. The app doesn't start. This error occurs when the ASP.NET Core Module attempts to start the .NET Core CLR in-process, but it fails to start. The cause of a process startup failure can usually be determined from entries in the Application Event Log and the ASP.NET Core Module stdout log.
Common failure conditions:
- The app is misconfigured due to targeting a version of the ASP.NET Core shared framework that isn't present. Check which versions of the ASP.NET Core shared framework are installed on the target machine.
- Using Azure Key Vault, lack of permissions to the Key Vault. Check the access policies in the targeted Key Vault to ensure that the correct permissions are granted.
If you are using Azure App service, please refer to the suggestions provided here:
- Azure App Service & ASP.NET Core 3.1 500.30 - One odd cause
The problem in this case was, somehow, being caused by the customer's App Service having the .NET Core 3.1 runtime installed via Site Extension, instead of using the built-in runtime that comes with App Services. The issue resolved when the Site Extension was removed, and the App Service was stopped and re-started. - Troubleshoot on Azure App Service
Other potential causes and solutions:
- Troubleshoot on IIS
- How to Fix Error 500.30 – ASP.NET Core app failed to start
- Stackoverflow threads on the same issue - Post 1, Post 2, Post 3
Please try the suggestions provided above and let me know in the "comments" if you have any updates/questions/further details to share. Comment is the quickest way of notifying the experts.
If this helps, please 'Accept Answer' so that it can help others in the community facing the same issue.