Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Blazor wasm debugging SSL problem

See original GitHub issue

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

Issue Analytics

State:
Created 9 months ago
Reactions:1
Comments:13 (8 by maintainers)

Top GitHub Comments

2reactions

thaystgcommented, Dec 19, 2022

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

Thanks.

1reaction

seriouzcommented, Dec 19, 2022

Thanks this works! I don’t know in my “not demo project” the inspectUri attribute was declared as an error because it was not known. In this demo project it works flawlessly. I think i have to inspect why this prop does not work on my original project. I’ll reopen this issue, when i find a traceable problem. Thanks!

Top Results From Across the Web

Cannot debug Blazor wasm

I'm using chromium on linux (ubuntu 20). When I try debug, I get this error in a popup: Unable to launch browser: "Failed...

Troubleshooting .NET Blazor WASM Debugging

It's common to see messages saying: “Blazor Wasm Debugging: lockfile exists, connecting to already running browser”. The message means you have ...

Debug ASP.NET Core Blazor WebAssembly

This article describes how to debug Blazor WebAssembly with browser developer tools and an integrated development environment (IDE).

Blazor WASM debugging takes forever to load initial page ...

I have the new initial loading animation in place, actual loading of the app takes only minimal amount of time. After it is...

Blazor WASM Debugging Still Does Not Work : RIDER-78498

I've been down many rabbitholes with regards to the SSL certificate, disabling SSL. Different chrome user profiles, etc. It simply does not work ......