Blazor wasm debugging SSL problem

[seriouz]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am running a Blazor WASM app as hosted app through a WebApi project.
Everything is smooth but the debugging experience of the Blazor app.

When i am running Chrome with chrome --remote-debugging-port=9222 --ignore-certificate-errors --ignore-ssl-errors --enable-logging --disable-extensions --user-data-dir="C:\Users\serio\AppData\Local\Temp\blazor-chrome-debug" https://localhost:7081/

I get this output (the Blazor app runs but no debugging / breakpoint will be hit):

DevTools listening on ws://127.0.0.1:9222/devtools/browser/8decada6-eb5e-43fe-ac0f-9552a2f614d3
[22776:10556:1216/151153.567:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -101
[22776:10556:1216/151153.573:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -101
[22776:10556:1216/151203.797:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -101
[22776:10556:1216/151214.159:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -101
[16232:20740:1216/151346.074:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is

I've added the app.UseWebAssemblyDebugging(); on the WebApi host and added the package Microsoft.AspNetCore.Components.WebAssembly.DevServer in both projects.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

7.0.1

Anything else?

No response

[TanayParikh]

@thaystg is this a scenario we support?

[thaystg]

I think I need more information to understand it.
@seriouz can you provide us a simple project that reproduces this issue?

[seriouz]

@thaystg Sure here you go. Run the HostApi project:
WebApiHostsBlazorWasm.zip

@TanayParikh I think i saw somewhere that a hosted Blazor wasm app was debuggable but i don't find the source right now.

[TanayParikh]

Just to clarify, we definitely support debugging hosted Blazor WASM apps, however that's usually through VS/VSCode debugging extensions. I wasn't sure if the Chrome CLI command was supported.

More info: https://learn.microsoft.com/aspnet/core/blazor/debug

Also, could you please provide the repro as a publicly hosted github project?

[seriouz]

@TanayParikh Sure, i pushed the folder as a repo: https://github.com/seriouz/WebApiHostsBlazorWasm

[seriouz]

Note: I tried to set the breakpoints in VS 2022 and in Rider 2022.3 both did not hit nor load the breakpoints.

[thaystg]

@seriouz in which source are you trying to add the breakpoint that is not working?

[seriouz]

@thaystg This line: https://github.com/seriouz/WebApiHostsBlazorWasm/blob/main/src/DebugTest.BlazorWasm/Pages/Counter.razor#L16

[thaystg]

I'm sorry, I think I don't understand, you have two projects, DebugTest.HostApi, this should be the one to be started from VS right?
Then I see this page:

Where should I click to run the Counter.razor code?

[thaystg]

Oh , okay, I can change the URL to go to the blazor app:

Thanks.

[thaystg]

In your launchSettings.json in the DebugTest.HostApi you need to add the inspectUri key:
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",