The Swiss Army knife to power JavaScript based client solutions ranging from Web apps/explorers over browser extensions to server-side clients like faucets/scrapers.
_app-XXXXXXX.js:1 Mixed Content: The page at '' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://websocket/'. This request has been blocked; this endpoint must be available over WSS.
This is very confusing since no wwebsocket connection is used here. "ws://websocket/" probably just means the RPC string was empty and "ws://" was prepended and "websocket/" was appended.
It should not be too much to ask the app developer to always include the protocol in the URLs.
In an app I am running into errors like this:
This is very confusing since no wwebsocket connection is used here. "ws://websocket/" probably just means the RPC string was empty and "ws://" was prepended and "websocket/" was appended.
It should not be too much to ask the app developer to always include the protocol in the URLs.