-
Notifications
You must be signed in to change notification settings - Fork 5k
Blazor client side web debugging fails to function when run within IIS #101554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Tagging subscribers to this area: @thaystg |
Is this happening yet? |
Please reopen the issue if this is sill happening. |
Sorry, I didn't respond to the first notice. Yes this issue is still happening. |
We apologize for the delayed response! @xantari would it be possible to provide a repro for this issue? This is likely a https://github.com/microsoft/vscode-js-debug problem and so we should try to transfer this bug to that repo. |
Hi @xantari I just saw that there is a repro here, can you please close the issue here and reopen it on the repo that Tom suggested please? |
Copied it over there. Closing this one. |
Is there an existing issue for this?
Describe the bug
When attempting to debug a local IIS hosted web application running blazor you get an error when attempting to debug the blazor razor component.
Kestrel debugging works fine. However it is broken in IIS mode when running under an SSL certificate:
Unable to launch browser: "Could not open wss://localdev.arrt.org:443/_framework/debug/ws-proxy?browser=ws%3A%2F%2F127.0.0.1%3A34840%2Fdevtools%2Fbrowser%2Fd2b99056-84ce-433a-819b-d7df11de4a00\
Currently the only work around is to remove the following from the launchSettings.json, but then blazor components using WebAssemblyPrerendered are no longer able to be debugged.
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
Here is the log indicating it is unable to open a websocket connection.
visualstudio-js-debugger.txt
NOTE: IIS does have Websocket Protocol enabled in windows, so that is not the issue. Other websocket activities work fine, just not the debugging using inspectUri parameter.
This may be related to this issue: #96239
However the fix indicated in that issue does not work for me. This is the fix recommended (updated example to LocalDevelopment):
<DebuggerSupport Condition="'$(Configuration)' == 'LocalDevelopment'">true</DebuggerSupport>
Expected Behavior
Client side debugging should work without issue. The "inspectUri": "{wsProtocol}://{url.hostname}:443/_framework/debug/ws-proxy?browser={browserInspectUri}" line should also work without issue when running within IIS under an SSL certificate.
Steps To Reproduce
Exceptions (if any)
.NET Version
.NET 8.0.3
Anything else?
Visual Studio 2022. 17.9.6
Sample Project
BlazorApp1.zip
The text was updated successfully, but these errors were encountered: