From beda56114ce32a0b1ac560531e0d30f7d8b9d4c7 Mon Sep 17 00:00:00 2001 From: Florian Knodt Date: Thu, 6 Dec 2018 01:53:08 +0100 Subject: [PATCH] hint to ad-/scriptblockers --- Troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Troubleshooting.md b/Troubleshooting.md index e38337e..8a34360 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -9,6 +9,7 @@ If you're using chrome there are several ports which are [blocked](https://src.c If it still doesn't work, here are some things you can try: - navigate to `https://:/weechat` (e.g. `https://foo.bar:9002/weechat`) in your browser. Do you get a certificate warning/error? If so, your certificate isn't set up properly. Correct behaviour would be a blank page. - did you run `/relay sslcertkey` after setting your certificate? Try re-running it. +- are you using an ad- or scriptblocker? If so check if websocket/xhr-connections to your server are allowed - let our bot diagnose your TLS setup, query `lorelai` on freenode and type `>tls :` (substituting host and port as above) If you can connect fine with your desktop/laptop, but are having trouble on your phone, you're most likely missing one or more intermediate CAs in your `relay.pem`. You can diagnose this with `lorelai` as above. Include *all* relevant intermediates and re-run `/relay sslcertkey`.