[Bug] MyApp.Server (csproj) fails to make a ws connection when it launches.

[psimoes123]

Current behavior

When you create a new Uno platform app in visual studio and selects the Server option under 7. Features. Uno will create three csproj UnoApp, UnoApp.Contracts, UnoApp.Server. if you see the UnoApp to WebAssembly and the set the UnoApp.Server as a default startup project. A web browser will pop up and show the uno logo, but they application will get stuck there.

Upon opening the developers tool from the browser, I saw the following error in the console application.

From my understanding it seems that it tries to create a ws (web socket) over the https connection which only accepts wss (web socket secure). So it immediately terminate the connection, which then causes the application to not load.

Expected behavior

I assume that the WebAssembly from the UnoApp proj should be able to create a https connection (wss) so that it matches with the Servers expectation.

Affected platforms

WebAssembly, Server

Template Host

Visual Studio

Host OS

Windows

Template Options

Default Recommended preset + Server option (7-Features)

Template Version

Uno Platform Extension 6.1.20.20

Anything else we need to know?

No response

[DevTKSS]

You need to allow unsecure contents for localhost even if you set wasm startup project with additional https uri infront of the single one, but yes I would absolutely agree that all of this should not be required at all. I just stopped using the server project of uno and will instead create a non "uno wasm bootstrapper server" project for minimal api backend 😐
Maybe its related to that app.UseHttpsRedirection(); and no hsts or UseStaticAssets() like Blazor does, but missing knowledge to that. Whats that web socket security you mentioning? Do you know how that should be solved?

Hoping that at some day it will work fine

[DevTKSS]

@psimoes123 I dont know much/any about the web things, but this Mixed Contents I do also always have plus this strange Unsafe Contents behaviour, which I have no clue how I should fix this beside allowing them which is not what we want for production hopefully...

• [Wasm] Changing Unsave Contents from Block to allow shows js script and a before "safe" side is afterwards marked as unsafe while its https uno#21143

@Jen-Uno could the team check if they are somehow related? I am everytime getting that Messagebox if doing as Jerome told in the latest server docs, that is telling me that it can not reach the debug uri which we normally see (docs do tell) as white page with the blazor advises. but as soon as I close that Messagebox the Wasm debug session exits. leaving it just opened, lets me run the app future (if allowing those...) the user above has that same Mixed contents warning 🤔 and Jermome mentioned he seen it before