[blocked] The page at https:// was not allowed to run insecure content from ws://127.0.0.1:12345/.

I don't understand why it can work from the link you mentioned. If I enable the webSocketSecure, I also need to provide a certificate.

-useWebSocket, servers will start as websocket server if this is true
-webSocketSecure, if servers start as websocket server, it will start in secure mode if this is true
-webSocketCertPath, path to certification file which its extension is .pfx, it is required if webSocketSecure is true
-webSocketCertPassword, password for the certification file (.pfx).

Our product including website and app will be released to customers, is that 'private' certificate issued to a 127.0.0.1 address can be released?

added more information:

from the doc, it looks like that safari doesn't support mixed content.

https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

No, not http or https resources directly. My code will create a websocket, e.g.

const url = `ws://${this.host}:${this.port}`;

this.webSocket = new WebSocket(url);

after installing our app on local macOS, it will install an agent as well. so, in the browser, clicking the button will try to connect to the agent and awake it, then the agent will launch our app.

I don't know how zoom.us or Microsoft teams approach that. We just used this webSocket solution. Both Chrome and Edge can work, but Safari failed.

The address is 127.0.0.1 a local address, it cannot be issued a valid certificate. So, we use the ws (http) instead of wss

and as I know, a certificate can't be issued to a localhost or 127.0.0.1 address.