I have a .net framework application running on IIS version 10.0.17763.1 hosted on an Azure Virtual Machine and sometimes my users are getting ERR_HTTP2_PROTOCOL_ERROR
This site can’t be reachedThe webpage at https://..../page.aspx might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR
I have no idea how to debug and it's an intermittent issue
Below are two screenshots from the developer tools network tab
The only thing that is failing to load is the page.aspx, all the JS and CSS are loading properly.
Related
I have moved an existing ASP.NET Core Web application to a new server. On the old server we had Windows Server 2012 R2 and IIS 8.5 installed. The new server is running Windows Server 2019 and IIS 10.
We encountered a bad loading perfomance with slow network connection for the site when hosted on the new server. Browser development tools revealed that on the old server resources are loaded in parallel, resulting in images and videos already available while some other content is still loading.
On the new server, only one resource is loaded at a time and the other requests are in waiting mode.
Old server loading behaviour:
New server loading behaviour:
I checked all configuration values I'm aware of in IIS but could not find any difference. Neither in server settings nor page settings nor application pool settings. There are everywhere the same default values, we haven't changed anything other then the application pool identity.
The application itself has not changed. But it has been updated from .NET5 to .NET6. I don't expect that this makes any difference for content servering by IIS, though.
As always, any help or hint is appreciated!
Scenario:
IIS Version 10.0.14393.0 installed.
Net framework 4.6.1 installed.
Windows 10
We are having an issue when opening multiple tabs of the same website hosted in our server.
If we open 3+ tabs at the same time, the site wont load. The exact same package is installed on another server and working properly.
We have cross checked the application pool(4.0 integrated) with the working one, and the site configuration too and they are the same.
We even changed the connection string of the website to connect to the db of the site working and it also fails.
This happens when connecting from another machine, and also when opening the website on the server itself.
Any help?
I was running my asp.net application on localhost in the internal IIS for Visual Studio and for Testing purposes I was trying to host my website on my LAN at home. I obviously had to switch to use the custom IIS web server. I followed all the steps to do this i.e. I turned on IIS from the windows features in control panel and added my web application to IIS and configured VS settings to use that server and gave it a start URL.
However when I run my project I am getting an error message:
Unable to start debugging on the web server. The web server did not
respond in a timely manner. This may be because another debugger is
already attached to the web server.
What is the cause of this error and how can I solve it?
Thanks
One workaround is to make an empty page and you call the debugger from it as
System.Diagnostics.Debugger.Launch();
To solve it and make possible to start the debugger from the VS you must configure the start up page to see the local IIS on the properties of your project. Also I have notice that if you do not have default browser the IE it may also fail. So for me, to move on, call the debugger from the page.
I have the same problem and I solved it by reseting iis from cmd => "iisreset"
i have web site and it is hosted on shared server ORCSWEB. now when i testing one page locally then i found it is running fine but when i test the same page putting our live site url then i found it is not working. so i want to test that from live site but from my own VS2010 IDE and want to set break point. i just do not know is it possible or not but i can not install any remote debugger there due to lack of access.
i visit this url for gudance http://www.codeproject.com/Articles/38132/Remote-IIS-Debugging-Debug-your-ASP-NET-Applicatio
but i could not help me. thanks
I'm not an Orcsweb customer, but you cannot do Remote Debugging unless the VS Remote Debugger service is running on the target machine. If I were a shared webhost then I wouldn't provide this service to my customers because it's a massive security liability.
Out of curiosity, why can't you fix it based on any exception reports generated right now?
I created a Virtual Application in IIS 7 to host my app so I could test it on other machines on the local network, since the development web server will not respond to requests from machines other than the local machine. I had to allow IIS to login as me to get into My Documents, and enabled ASP.NET impersonation through the IIS. That worked fine, but...
Now the ASP.NET Development Webserver won't serve anything at all. I hit debug in VS2008, the dev webserver starts up seemingly fine, but then the IDE launches Chrome and the browser just sits there twiddling its thumbs. It never fails, but never loads. Nothing.
There are no errors from ASP.NET Development Webserver or Visual Studio or Chrome that I can find. I even looked in the Event Log. Nothing.
What did I just stupidly do?
I haven't got Chrome installed at the moment so i can't confirm for sure before i answer this, but IIRC i have seen this before and the VS debugger cannot correctly launch Chrome and serve it pages from Cassini (the VS development webserver).
The way i got round this previously is to just create a virtual directory in the local (dev machine) instance of IIS, and point it to the folder containing your web project. Then you can use Chrome to browse it just like a normal web site. You can then manually attach the VS debugger to the right worker process.
Alternatively, you could start up the debugger as you are now, and when Chrome sits there, you could manually enter the url for the page you want to start with (it will be http://localhost:<some port>/default.aspx or similar). VS won't be able to debug the script in the page, but it should still debug the compiled code just fine (like it does for Firefox).
Holy crap, I know what it was. When I changed the IIS settings to have ASP.NET impersonate me to get into the My Documents folder, it modified the web.config file. Now you're probably thinking, well duh, of course it did. I honestly thought that IIS 7 had some new way of dealing with impersonation other than the web.config setting. Turns out it's just built into the MMC snap-in to manage it now, but it does it in the same way.
Once I reverted back to the original version of the web.config file, ASP.NET Development Server happily worked exactly as intended again. I suppose ASP.NET Development Server craps out if there are impersonation settings in the web.config.