How to fix HTTP Error 500.30 - ASP.NET Core app failed to start

Question

I'm new to Azure and unsure how to start troubleshooting my issue, I've found the portal support to be unhelpful. The support system asks numerous questions about the problem but ultimately provides no solutions or contact with a support representative, which is very frustrating.
My ASP.NET Core web app is failing to run on Azure, though it works fine on my PC. I downloaded a publishing profile and republished the app, but this didn't resolve the issue. I'm encountering a 500.30 error indicating the Core app failed to start.

Can anyone guide me on how to diagnose this?
Thank you!

Answer 1

Hi there Sooraj Krishnakumar

Thanks for postingon QandAplatform.

There may be a few reasons behind the error which you can only identify by debugging. You can try to debug this error using the steps below:

1. Navigate to the root directory of the application using CMD
2. Run the application using the command dotnet run (yourApplicationName).dll

If there are any errors, they should appear in the output.

Alternatively, you can check "Event Viewer" (search Event Viewer using Windows search) and navigate to

• Windows Logs
  • ApplicationThere may be a few reasons behind the error which you can only identify by debugging. You can try to debug this error using the steps below:
    1. Navigate to the root directory of the application using CMD
    2. Run the application using the command dotnet run (yourApplicationName).dll
    If there are any errors, they should appear in the output. Alternatively, you can check "Event Viewer" (search Event Viewer using Windows search) and navigate to
    • Windows Logs
      • Application

Have a look at the below link, a similar thread, hope it helps.

reference - https://stackoverflow.com/questions/67211060/http-error-500-30-asp-net-core-app-failed-to-start

If this helps kindly accept the answer thanks much.

Answer 2

@Sooraj Krishnakumar , Adding to Azar's suggestions. If you are fine, kindly share your webapp URL/ details.

• As outlined in the troubleshooting IIS doc 500.30 is more generic error and this might be caused due to multiple reasons.

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.

To isolate the issue:

• If you haven't done, kindly run the webapp down detector under diagnose and solve problems of your webapps to fetch more details about the issue.
• Also, review Application event logs - access application event logs.

Note: Please do not share any PII data on the public forum.

---

If the answer helped (pointed you in the right direction) > please click Accept Answer - it will benefit users in finding the right answer quickly.

Answer 3

Faced this issue and resolved by setting Enable 32 bit Applications property in IIS application pool to false. The deployed asp.net core application was configured to run as 64 bit.

Answer 4

the 500.30 error generally means your app throw an exception during startup. this is often a configuration or permission error.

try this doc:

https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-2.2