i have a situation here. I would to publish one of my \'test\' .net core application (.net core 3.1) to see how Azure platfrom works and there is a problem after publishing web
From your description, I think this 500
error should be a deployment failure error.
At the end of the answer, there is a suggested solution to try, it is recommended to try.
In order to quickly locate and solve the problem, I recommend using git for continuous deployment. More error logs can be viewed in Action like pic.
If the above method does not help you locate the specific cause of the failure, then I suggest you use Diagnose and solve problems
to troubleshoot the problem. Search the search box for Collect .NET Profiler Trace
,
Then you can click Collect Profile Trace
, and wait system generate a report. Click the link, you will open a new page and see more details about the webapp.
Suggest a trial plan (specific problems need specific solutions)
web.config
file.<customErrors defaultRedirect="YourErrorPage.aspx" mode="Off">
<error statusCode="500" redirect="InternalErrorPage.aspx"/>
You also can create log in your code, then you can see more details.
resource group
or choose another region
to try to redeploy. If this error still occurs, it is recommended to raise a support ticket
in the portal.Sum up:
First of all, it is recommended to use git for continuous deployment to troubleshoot the operating environment or problems that occur in the release operation.
Use tools to troubleshoot the root cause, if it is really impossible, you can raise a ticket for support.