From df610e26306155358e00c067c69aa32c7e54d51b Mon Sep 17 00:00:00 2001 From: Denny Date: Thu, 23 Feb 2023 12:17:39 +0100 Subject: [PATCH] Add section clarifying ws usage to README --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 1b5a259..2e27725 100644 --- a/README.md +++ b/README.md @@ -39,6 +39,22 @@ Congrats, you can now share the presented link to the world. For more information head over to [docs](https://loophole.cloud/docs/). +## Having issues with WebSocket? +Because Loophole will always start connections to clients with HTTPS, it is not possible to establish plain + **ws://** connections, only **wss://** (WebSocket Secure) will work. In fact, establishing a **ws://** + connection from HTTPS would even be considered a security issue, which means that e.g. browsers block this + by default. This is not something we at Loophole can change. + +If you use **wss://** and have checked that it works locally but are still experiencing issues, try the following: +### Desktop version: +- Make sure the box named "The server is already using HTTPS." is ticked. +### CLI version: +- Make sure you use the --https flag. + +If your problem still persists, feel free to open a new +[Issue](https://github.com/loophole/cli/issues/new?assignees=&labels=bug&template=bug_report.md&title=) and tell us +about it! + ## Development