Connect over wss when loaded over https
See original GitHub issueWhen loading majestic over an https
connection, the client attempts to connect over ws
not wss
.
It seems the apollo http link will require https
too.
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (15 by maintainers)
Top Results From Across the Web
Mixed Content error when accessing WebSocket server ...
When the page is accessed through HTTP, you can use WS or WSS (WebSocket secure: WS over TLS) . However, when your page...
Read more >Problem with websockets over https - Questions - Defold Forum
Hi! We have a problem connecting our game to the server via HTML5 when we use websockets. Here are the extensions we use:...
Read more >Wss connection problem while trying to connect by https #114
I have a problem, Help me Mixed Content: The page at 'https://expzero.com/todolist/' was loaded over HTTPS, but attempted to connect to the ...
Read more >Allowing insecure WebSocket connections | Damir's Corner
SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS. Chrome also ...
Read more >Set up Secure WebSocket for Remote Connections
Let's see how we can set up WSS on a remote Substrate node. Note: this should only be done for sync nodes used...
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
@NickBolles I’m not against it but didn’t get the time or motivation to work on it yet. Reopening the issue. Feel free to send a PR if you are interested.
@Raathigesh: Thank you very much for your work on Majestic, it’s an awesome tool! 😃
I am currently working to get it to run on a server. It’s password protected but technically public-facing. This makes it a lot easier for our distributed team to run the same tests that lay centrally on the server. That way not everyone has to deep-dive into the inner workings of Majestic and Jest testing but can simply “click a button to check if everythings works” (= green).
Right now I have majestic running behind an nginx server with active HTTPS but the missing wss:// is the last remaining hurdle. So at least for me there’s absolutely usecase for it and I’d love to see it implemented