[Question]: How can i connect to browser running on a Moon cluster over secure websocket connection

Your question

I am trying to connect to browser running on a Moon cluster over secure websocket connection as documented and i am getting the following exception "PlaywrightException: WebSocket error: unable to verify the first certificate" full trace:

Unhandled exception. Microsoft.Playwright.PlaywrightException: WebSocket error: unable to verify the first certificate
=========================== logs ===========================
<ws connecting> wss://moon.perci.dev.local/playwright/chromium/playwright-1.22.0
<ws error> [object Object]
<ws connect error> wss://moon.perci.dev.local/playwright/chromium/playwright-1.22.0 unable to verify the first certificate
<ws disconnected> wss://moon.perci.dev.local/playwright/chromium/playwright-1.22.0 code=1006 reason=
============================================================
   at Microsoft.Playwright.Transport.Connection.InnerSendMessageToServerAsync[T](String guid, String method, Object args) in /_/src/Playwright/Transport/Connection.cs:line 164
   at Microsoft.Playwright.Transport.Connection.WrapApiCallAsync[T](Func`1 action, Boolean isInternal)
   at Microsoft.Playwright.Core.BrowserType.ConnectAsync(String wsEndpoint, BrowserTypeConnectOptions options) in /_/src/Playwright/Core/BrowserType.cs:line 150
   at TestMoon.TestMoon.Main() in C:\Users\69935\code\TestMoon\TestMoon\Program.cs:line 10
   at TestMoon.TestMoon.<Main>()

Process finished with exit code -532,462,766.

It is failing here : await using var browser = await playwright.Chromium.ConnectAsync("wss://moon.test.local/playwright/chromium/playwright-1.22.0");

The sertificates as stored in Local and User Certificate manager.

any suggestions?

[rwoll]

That error should be resolved by setting NODE_EXTRA_CA_CERTS to point to your cert.

Let me know if that works for you. In my repro, I was hitting the same error as you above, and setting NODE_EXTRA_CA_CERTS to point at my cert.pem resolved it.

I consider this suggestion a workaround since it leaks Node.js implementation details up to .NET (and in an ideal world we’d automatically pick it up from your OSes trust store assuming it’s been added).

[dimsamaras]

@rwoll Thanks again! It works!