Azure App Service - Request Diagnostics reveals HTTPS on port 80 - azure-web-app-service

I created an Azure App Service. Deployed it via a develops pipeline.
Basically, this service is broken, and im trying to troubleshoot it.
During my investigation using the Request Diagnostics blade/tool, i learned that the request url is using HTTPS with port 80.
Does this mean i tried making an invalid request?

Here is some ways for troubleshooting web app breken:
You could find out the error logs in kudu: yourwebapp.scm.azurewebsites.net/DebugConsole --> LogFiles --> eventlog.xml, which file only be created when your web app broken.
A useful tool you mentioned in your question also helps. The steps for diagnostics is: Click Availability and Performance--> click Web App Down.
Here is a solution about troubleshooting .net-core web application broken using Diagnostic tools. As you can see, JAVA and PHP also supported. see the created Profiler Trace in kudu: yourwebapp.scm.azurewebsites.net/DebugConsole--> data--> DaaS--> logs--> yourwebapp.

Related

Why I am not receiving proper logging of the failed request hosted on App Service?

I have web app and web api hosted on Azure App Service. It is a big application that works fine on IIS when hosted locally. When we hosted it on app service it works fine but only few things stopped working. I can't debug a code in App service because whole team is working on it, but when I host Web api in my personal azure account and used postman to debug it then also it works fine. When I check Application insight logging to figure out the issue, I can only see a log made by Web Api, this is the log:
How should I debug the issue in such a case?
When we hosted it on app service it works fine but only few things stopped working.
Make sure you are logging properly all your services in your Web App and Web API. You can check the details information of error in Application insights or in a KUDU console from there you can see the log files from where it has problem.
Using kudu:
https://<YourWebApp Service>.scm.azurewebsites.net/DebugConsole -> Log Files (Check the application logs)
How should I debug the issue in such a case?
The only solution is you can remote debug your application deployed in your App Service. For that you need to enable the remote debugging in your app service.
I can't debug a code in App service because whole team is working on it
If it is in a production environment, you can create a separate slot by MS-DOC and add your Web app and try to debug.

Connecting to an Azure App Service via IIS Manager (inetmgr)

Is it possible to remote-connect to an Azure App Service running on Windows with my IIS Manager?
This seems to have been possible according to this blog post by clicking in IIS Manager File -> Connect to a site.
I refer to the steps mentioned in the link shared by you and in the last step I got an error below.
I did some research on it and it looks like managing the App Service from IIS is not supported anymore. I have not got any official link but the below links might give you some information on it.
Microsoft.Web.Configuration.AppHostFileProvider not found after configured Remote IIS Administration for Microsoft Azure Web App
Can no longer manage any Web Apps with IIS Remote Manager - Could not load file or assembly - AppHostFileProvider
I'm not sure for what purpose why you want to. My thoughts is you shouldn't be doing that as it defeat the purpose of PaaS services. Cannot access the iis layer in app service however you can still configure in web.config of your web app.

Azure Web app service becomes unavailable for a few hours

My azure web app service suddenly becomes unavailable for a few hours.
The app hosts .net core 3.1 web API.
All the requests are pending for a few minutes and then fail. Restarting the app doesn't help. Stopping and starting again too.
Applications insights don't show those failed requests.
Please help, the app serves a lot of users and requests!
I have run Availability and Performance diagnostics at the time of the crash:
Everything looks just fine except the failed requests.
As suggested earlier , you can debug why the web app went unavailable by running the availability & performance under Diagnose and solve problems in the portal.
You can also refer this Azure documentation to troubleshoot Troubleshoot HTTP errors of "502 bad gateway" and "503 service unavailable" in Azure App Service
if you are still not able to find any insights , why the webapp went unavailable you can open a discussion over Microsoft Q&A or please create a technical support ticker by following the link where technical support team would help you in troubleshooting the issue from platform end.

React application deployed on azure is not using Http2 even though Http2.0 is enabled for app service on azure

I have deployed my react application on Azure App Service with .NET Stack (.NET Core 3.1,2.1). I have enabled Http2.0 from Azure App Service > Configuration > General Settings and also from azure resource explorer. At both places it shows Http2.0 but browser still uses Http1.1. TLS Settings are Https only and TLS version 1.2
There is no problem with this function.
I reproduced your problem. You only need to open a new privacy mode window and refresh it a few times to see the new settings take effect.
This problem may be caused by browser cache, etc.
Test Result.
In front of the APP service WAF was enabled. And WAF was not supporting Http2.0

Connection was reset / file upload in asp.net azure with ssl only

I am trying to upload a file to blob in asp.net azure. I am getting success if the page is without ssl. but if i upload with https page then i am getting connection was reset error.
And also I mentioned the maxrequestlength in web.config.
This is not Azure specific error instead it is an ASP.NET specific problem. I did some test if I could hit the problem but no luck..
I am getting sure that the problem is introduced by adding maxrequestlength and potentially having request filtering. You must setup the timeout setting with length and support script runtime in webserver specific settings.
You also have one option to RDP to your instance and enable IIS debugging to understand what could be the problem:
http://www.microsoft.com/en-us/download/details.aspx?id=26798
After running Debug Diagnostic Tool v1.2, please share your log, and i will look for root cause.
To RDP Access to Windows Azure Application, visit my blog here

Resources