Being served over HTTP causes issues on HTTPS sites
See original GitHub issueWhen attempting to use PeerJS from a site that is served over HTTP, this error appears in the console:
Blocked loading mixed active content “http://0.peerjs.com:9000/lwjd5qra8257b9/id?ts=15151778159410.6040248252280473”
Because the site for peerJS is served over HTTP, it is considered dangerous for the script to be loaded from there.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Quickly Fix Mixed Content Warnings (HTTPS/SSL)
Mixed content warnings are common after an HTTPS migration or adding a new service. Check out how to quickly fix these on your...
Read more >How to Find and Fix Mixed Content Warnings on HTTPS Sites
If mixed content loads over a secure connection, you may be asking ... Blocking all of it will lead to ruin and cause...
Read more >Mixed content - Web security - MDN Web Docs - Mozilla
Mixed passive/display content is content served over HTTP that is included in an HTTPS webpage, but that cannot alter other portions of the ......
Read more >Fixing the mixed content problem with Automatic HTTPS ...
Here's the problem: if an https:// website includes any content from a site (even its own) served over http:// the green padlock can't...
Read more >Is there any reason not to serve https content on a page ...
If the content served over HTTPS within the HTTP page isn't particularly sensitive and could equally be served over HTTP, there is no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

use a custom peerjs-server for this and host it to your vps
Update your peerjs version and it will work. (Even with key option, although it’s useless)