How to resolve .NET core azure appservice 500 error

Question

3.00/5 (1 vote)

See more:

I have published a basic .net core app in Azure Appservice. I followed many articles and did it successfully. I even attached remote debugger for the published app in visual studio. But the debugger is not hitting the startup class also, App just simply returns 500 error and says currently unable to handle requests.

Application is working fine locally and I have also hosted it in IIS, In Intranet it's working fine!

Please advise what could be the fault in this case.

What I have tried:

I enabled debugging mode in azure app service and attached debugger in visual studio for the published app. But, not even startup class is hitting when URL is triggered.

Posted 21-Nov-18 21:40pm

Sai_95

Updated 22-Nov-18 2:53am

v2

Add a Solution

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)

Afzaal Ahmad Zeeshan · Answer 1 · 2018-11-22T02:53:00

Solution 1

That process needs to be debugged, you can use the Production Testing to do that, or you can even try to connect the Visual Studio to the live environment and do a live testing of the application. That way you will understand what is being missed on the environment; perhaps a missing configuration setting, or unaccessible resource.

Testing in Production with Microsoft Azure[^]
Troubleshoot a web app in Azure App Service using Visual Studio | Microsoft Docs[^]

Posted 22-Nov-18 2:53am

Afzaal Ahmad Zeeshan

Comments

Sai_95 23-Nov-18 4:31am

Thanks, @Afzaal I tried attaching the remote debugger and followed all the steps, but it didn't help.
Finally, I created a deployment slot for the same app and published the app on it. Now with the deployment slot URL, the application is working fine.

I anticipate that the original publish file doesn't pick my latest changes. I'm not sure what's wrong with it and I'm still trying to accomplish it.

Will the reset publish profile works? But I need to get credentials from my manager, which is not possible at this time.

Afzaal Ahmad Zeeshan 23-Nov-18 6:26am

Might be, because deployment slots are the same settings and configuration environments nonetheless. So something might have been missed during deployment.

Reset publish profile does not help with this case. Try redeploying automatically, if you have access. Publish profile is just a connection between your machine and Azure's pod for your app.