What I have:
VS2015U2
ASP.NET 5 MVC 6 website
Deployed to Azure Web App
The site works locally
When I deploy to Azure I get internal server error (500)
I'm unable to Attach a debugger since they messed up something with the latest versions (tried manually too https://azure.microsoft.com/en-us/blog/introduction-to-remote-debugging-on-azure-web-sites/)
I have app.UseDeveloperExceptionPage(); but I guess the site is failing during configuration so it doesn't display any other information.
So how to resolve this? I need to see the .net exception but I have no idea how to do that.
Try adding Application Insights to the app. You should see errors on startup of your application.
I would also take a look at your startup code to see if you are writing to disk anywhere during configuration or app.start. This might be the case if you are using AAD in any capacity.
You can also hit up the KUDU console by targetting https://sitename.scm.azurewebsites.net . You will be able to navigate in the debugging console to see the RAW logs from IIS. That might shed some light into the situation. See KUDU for more info.
I solved this problem like show below.HTTP 500 error interested about that is not allowed to access the server.Go to azure portal address and choose your database.Press"Set server firewall " and Allow Azure services and resources to access this server choose "Yes" save that page and refresh your service.Than you can see your data
Use the KUDU console at https://sitename.scm.azurewebsites.net
Go to web.config file and check if the process path is correct.
I used the Azure Log Stream to help figure out what was going on. As Karishma Tiwari - MSFT said, the issue ended up being my web.config file (which was built for .NET 3.5 and not 4.7)
Here's the tutorial to set up Log Streaming: https://blogs.msdn.microsoft.com/azureossds/2016/09/28/how-to-identifyreview-errors-on-php-applications-in-azure-web-apps-using-log-stream-service/
My particular app's solution was to update my Azure App Service to use .NET 3.5, in its Application Settings, like so:
For me it worked after I turned "Allow Azure services and resources to access this server
" to Yes
I got this error even though I had enabled Application Logging (Filesystem), Detailed error messages and Failed request tracing in App Service logs
This page isn’t working
mysite.azurewebsites.net is currently unable
to handle this request.
HTTP ERROR 500
However by navigating to Log stream and selecting Application Logs I could see a detailed error message:
I know this question has already been answered but here is a recent view of the Azure Portal where I found a solution to this problem
Related
I have a web app, ironradio.org, that I've deployed on Azure from VSCode. I've made some updates to the site and am now trying to deploy the newest version. Now when I try to deploy using this button:
I get the error 403 - This web app is stopped in the output window:
I've already deployed several versions of the site using the same method and it's never failed before. Also, the app is definitely not stopped because I can still browse to the site and it shows up.
My best guess as to what's going on is that I associated the App Service with a new resource group since the last deployment, so maybe VSCode isn't recognizing that? Does anyone have any idea what's going on here?
I tried the link given in the error message, but it wasn't much help.
Microsoft foreseen this type of error and how it can affected its customers greatly and this is why the deployment slot is for you.
Firstly, you have to delete the app and reupload again except you set up continuous deployment which work mostly with GitHub and other version control platforms.
Apart from this, I will suggest you check out the deployment slot docs. It’s very simple and easy to use
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots
I am trying to deploy a Blazor Server app using .NET5 to an Azure App Service via Azure DevOps.
The Blazor app runs and works correctly locally. The Azure DevOps pipeline appears to also be building and deploying correctly. If I use the console in the Azure portal I can see that the files I would expect are in the wwwroot folder (which I guess is correct?). In Configuration > General Settings I can see that the App Service is correctly configured for .NET 5. On the network side there are currently no access restrictions. I've also turned off all auth in the app for now just to make sure that wasn't having an impact.
When I try to access the site at https://my-app.azurewebsites.net (not the real url, just an example in case it's relevant) I get a white page with the following text: "You do not have permission to view this directory or page.". When I look in the Diagnostics dump from the Kudu page I can see more detail error pages which say 403.14 - Forbidden and the message "The Web server is configured to not list the contents of this directory.". If I look in App Insights for the times when I try to access it I can see requests with 403 response too (for some reason with url: http://localhost/). Unfortunately this error seems to cover a multitude of errors and so while I've found various sources with similar problems, none of the solutions I've found so far have had any positive impact.
EDIT: So I did some more digging and I think some files might be missing. I tried creating a new Blazor Server app and publishing it manually via Visual Studio. This worked and the only difference I've found from my app is that I have no web.config, hostingstart.html, or static css/js etc (from wwwroot). None of these files are in the output directory when I build for either my app or the test app I created so it looks like they must be getting added separately by something in the VS manual publish process and Azure DevOps publish step isn't doing it. Still not sure what the correct way to fix this is (or even entirely sure if any or all of this stuff is relevant).
Has anyone out there got any idea what I might be missing?
So after working out what was going on here I was going to delete this but I figured possibly someone else will make the same mistake I did and this might help. Basically I'd copied another deployment pipeline for an Azure function app as the basis for the deployment pipeline for this and in that I just did a dotnet build and that's enough. However it seems for this kind of app to get wholesome output you need to run dotnet publish.
I am a total newcomer to the Azure cloud. I have this .net-core 2.0 app which runs locally on my development PC (Ubuntu Linux 17.10).
I have followed this guide:
https://learn.microsoft.com/en-us/azure/app-service/containers/quickstart-dotnetcore
... and I have deployed my app to the App Service container.
However, when I go to the app in my browser I get:
"503 Service Temporarily Unavailable"
Now, there are probably thousand things which can go wrong. However, I can't seem to find any debug logs/console logs to look into - so I am kinda looking with my eyes closed (It's not easy to debug that way).
It should be noted that I am on a free trial which have given me a $200 credit to use in the next 30 days.
How do one debug when a service is failing (yes, I've already tried the various suggestions on the portal but with no luck)?
How do one debug when a service is failing?
You could check deployment log on Azure Portal.
Click first commit, you will see the log.
Also, you could access Kudu console to check the log. You could access http://<webapp name>.scm.azurewebsites.net
Migrating OP's self-answer from the question:
I solved this by adding this to the PropertyGroup in my *.csproj file:
<PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
(as per: https://github.com/aspnet/IISIntegration/issues/476)
Now my app works and gives the expected output.
I have an solution that consists of a web gui front end and a web api backend. Both use Azure AD for auth with the former passing a token to the latter.
This all works fine on both a localhost and an OnPrem server, but when I push the release to Azure, I get a 500 Internal Server error when the GUI attempts to utilise the API.
At the moment, I am unable to obtain any further error detail.
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Any assistance or pointers that people can give would be greatly appreciated.
Cheers
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Per my understanding, you could follow the steps below to troubleshoot this issue:
For .NET web application, you could add customErrors flag in the Web.config file and set the value to On or RemoteOnly to see the detailed error message. Also, you could enable diagnostics logging for web apps to retrieve more details about the error message. Or you could just leverage Remote debugging web apps for a simple way to locate the specific issue. For more details, you could follow this official tutorial about troubleshooting azure web apps.
For .NET Core web application, you could refer to this similar issue. Additionally, for php, you could refer to nfo About PHP Fatal Error and Error Log on Azure Website and Change the built-in PHP configurations to troubleshoot this issue.
I have a asp.net web api application deployed as an azure web app. One of the endpoints occasionally throws an exception. Normally this isn't an issue for us. We have an ExceptionLogger attached to the api services. This has been in place for sometime and normally works fine.
Currently we see that a 500 response comes back from the server, but nothing is logged. I have tried setting GlobalConfiguration.Configuration.IncludeErrorDetailPolicy to IncludeErrorDetailPolicy.Always, but the response always comes back with no body content.
What else can I do to track the source of the problem?
If you have a consistent repro, then you can use remote debugging to attach to your web app and debug it (https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/).
Failing that, you can enable better diagnostic logs using the web app settings. Information on how to do so is here:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure/ under the section "Enabling diagnostic logs".
In your case you should have application logging enabled, and perhaps failed request tracing would be useful (FREB).
For even more tools you can use the Support Site Extension (http://azure.microsoft.com/blog/2014/12/01/new-updates-to-support-site-extension-for-azure-websites/) which would allow you to look at live event logs and HTTP traffic. For a deeper dive into debugging in Azure App Service see: https://channel9.msdn.com/Events/Ignite/2015/BRK4704.