When browse ASP.NET core web API from IIS this error happens

Question

1.00/5 (1 vote)

See more:

HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.

What I have tried:

I installed dotnet-hosting-7.0.0-win
Tried Publishing using different options like Folder and IIS

In IIS Option I use Web Deploy.

Currently using VS 2022 17.4 version with .net 7.0

I also added the following on Program.cs

</div>builder.Services.Configure<IISServerOptions>(options =>
{
    options.AutomaticAuthentication = false;
});

builder.Services.AddAuthentication(IISServerDefaults.AuthenticationScheme);

And this on csproj inside <propertygroup>

<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>

Posted 19-Nov-22 0:30am

Laiju k

Updated 19-Nov-22 4:28am

v3

Add a Solution

Comments

Laiju k 22-Nov-22 0:14am

This happens when I publish my site to IIS.I just need a proper way for hosting ASP . Net Core Web API on IIS

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2022-11-19T04:28:00

Solution 1

This is the error you get on the client-side, not the server-side.

500 errors mean you server-side code stopped for some internal error. Basically, your server-side code probably crashed because of an exception that was thrown.

Run your server under the debugger and try the operation in the browser again. The debugger will stop the code on the line that throws the error.

Given what you posted in your question, there is nothing there that could possibly tell anyone what the problem is.

Posted 19-Nov-22 4:28am

Dave Kreskowiak

Comments

Laiju k 22-Nov-22 0:04am

Sorry for the delay. I had some family issues last few days. Thanks for the solution I will check out what you have said. If there is any progress I shall get back to you.

Laiju k 22-Nov-22 0:11am

And also this is an release error not runtime one

Dave Kreskowiak 22-Nov-22 7:37am

You just told me you don't know what you're talking about. This is an error that occurs AT RUNTIME! You cannot get any error like this outside of the server code attempting to start or during its execution.

Laiju k 22-Nov-22 23:57pm

Yea My fault. I just meant its an error after publish to IIS and browse

Laiju k 23-Nov-22 0:02am

Can you also tell what more information that I can provide, So I can have a better solution

Dave Kreskowiak 23-Nov-22 14:21pm

Did you actually read the error page? There are suggested step on how to troubleshoot this.