hint to ad-/scriptblockers

Florian Knodt 2018-12-06 01:53:08 +01:00
parent 486f63811c
commit beda56114c
1 changed files with 1 additions and 0 deletions

@ -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: If it still doesn't work, here are some things you can try:
- navigate to `https://<host>:<port>/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. - navigate to `https://<host>:<port>/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. - 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 <host>:<port>` (substituting host and port as above) - let our bot diagnose your TLS setup, query `lorelai` on freenode and type `>tls <host>:<port>` (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`. 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`.