How to continue debugging internal server internal error after upgrading to ASP.NET 5 beta5

I had a site running asp.net 5 beta4, and decided to switch to beta5. The site works locally fine. I pushed the changes to the master, and he was taken from a bit bag and successfully deployed.

When I try to get to the site in blue, I get 500 internal server errors. I tried a few things, but it seems I can not trace the root cause of the failure. I am looking for suggestions as I click on the wall. From what I tried below, it seems that some kind of fundamental initialization is failing.

Here is what I tried:

  • Inclusion customerrors = "off". I added web.config to the wwwroot folder with system.web / customErrors mode = "Off". I checked that web.config is correctly populated in a deployed wwwroot and has the correct configuration containing dnxversion, etc.
  • Custom error page setup, adding runtimeinfo. I have the following set in my Startup.cs: app.UseErrorHandler("/Home/Error");. I also set an error page to display an exception. It doesn't seem to get it.
  • Attached to a remote process for debugging . The visual studio eventually freezes, so nothing came of it.
  • App understanding included . This logs events when I debug locally, but does not extract anything from the azure instance.
  • . 500.0 .

Imgur Imgur

, ​​ 5.

Update: ASPNET_ENV , azure. ASPNET_ENV - . startup.cs, , . .

+4
1

, DNX451, dnxcore50, , Azure - beta4 beta5. , .

Azure "SCM_DNX_VERSION" 1.0.0-beta5. , kudu beta5 https://github.com/projectkudu/kudu/commit/55175a017779bf493ff8e6ce87b96dd1451f7d7b, , Kudu .

( "K" ) :

- ASP.NET vNext 2 Azure Kudu

, -, SCM_DNX_VERSION.

+1

All Articles