HTTP2_Protocol_Error when debugging ASP.NET MVC Core from Visual Studio

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

https://asp.net

MIT License

35.15k stars 9.92k forks source link

HTTP2_Protocol_Error when debugging ASP.NET MVC Core from Visual Studio #42303

Open joelcochran opened 2 years ago

joelcochran commented 2 years ago

Starting Friday, trying to launch an ASP.NET Core MVC app from Visual Studio results in an HTTP2_Protocol_Error.

I have tried this in two different apps. One targets .NET Core 3.1 and the other .NET 5. I tried changing the .NET 5 to .NET 6, but received the same error. I have tried it in VS2019 (V16.11.16) and VS2022 (V17.2.4). I had a Windows update sometime last week (Wed/Thu). I have rebooted multiple times.

I started a brand new MVC project in VS2022, and accepted the self-signed certificate configuration. The new project starts correctly.

javiercn commented 2 years ago

@joelcochran thanks for contacting us.

Are you using IIS? To get a better and faster response, could you file this issue through the report a problem dialog in Visual Studio?

/cc @DamianEdwards @BillHiebert FYI, in case this is related to the HTTPS changes going on.

Tratcher commented 2 years ago

@joelcochran thanks for contacting us.

Are you using IIS? To get a better and faster response, could you file this issue through the report a problem dialog in Visual Studio?

I referred them here for initial debugging as this is likely to affect many of our customers.

/cc @DamianEdwards @BillHiebert FYI, in case this is related to the HTTPS changes going on.

It's not.

Tratcher commented 2 years ago

@joelcochran Some things that would be helpful:

The Windows version shown by WinVer.exe (E.g. 22621.160), Start -> Search -> winver.
Recent updates listed in your windows update history.
The version of C:\Program Files\IIS Express\iisexpress.exe (e.g. 10.0.25095.1000)
Capturing a decrypted wireshark trace and sharing the last HTTP/2 message to and from the server. What does the client think the server did wrong (or is it the server that thinks the client is wrong?). https://wiki.wireshark.org/TLS#using-the-pre-master-secret

You should be able to work around this for now by using Kestrel. https://dotnettutorials.net/lesson/kestrel-web-server-asp-net-core/

joelcochran commented 2 years ago

WinVer: 21H1 (OS Build 19043.1766) Recent update: KB5014699 (2202-06 Cumulative Update for 21H1) IIS Express version: 10.0.25095.1000

joelcochran commented 2 years ago

Confirmed that it works in Kestrel (thanks, I had never used that before). I will try to capture the Wireshark information.

Tratcher commented 2 years ago

ghost commented 2 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.