Mixed Content: The page at '<URL>' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint

[hunterInt]

• Version:
  0.50.2

• Platform:
  Linux ubuntu 5.4.0-52-generic daemon #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Severity:

Medium - A non-essential functionality does not work, performance issues, etc.

Description:

My console is filled with these errors (already 400+ in just under a minute of page load):

Is there a way to either prevent my HTTPS page from attempting to load non-ssl connections or suppress these errors?

Steps to reproduce the error:

await IPFS.create();

for await (const chunk of ipfsNode.cat(CID)) {
	chunks.push(chunk);
}

[jacobheun]

The underlying issue is that libp2p needs to be more restrictive of its websocket dials, especially in browsers. This is being tracked at libp2p/js-libp2p#796.

[achingbrain]

This should be fixed by libp2p/js-libp2p-websockets#116 in the near future.

[SgtPooki]

js-IPFS is being deprecated, the replacement is Helia. It's a modern, lightweight, and composable take on what IPFS can be in JS and is where the team's energy will be focussed moving forwards.

To help you upgrade your app to use Helia please see the following resources:

• Migration guide
• FAQ
• Hello Helia talk
• The State of IPFS in JS

This issue was fixed in libp2p by libp2p/js-libp2p-websockets#116, and the latest libp2p is included in helia