From 11a862f101355ce400c81e56f3b37d1d94523542 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20=C5=A0ediv=C3=BD?= Date: Sun, 19 May 2024 23:17:17 +0200 Subject: [PATCH] update docs. --- docs/getting-started/troubleshooting.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/getting-started/troubleshooting.md b/docs/getting-started/troubleshooting.md index 99265c324..cdf191c1d 100644 --- a/docs/getting-started/troubleshooting.md +++ b/docs/getting-started/troubleshooting.md @@ -4,15 +4,18 @@ Neko UI loads, but you don't see the screen, and it gives you `connection timeou ## Test your client -Some browser may block WebRTC access by default. You can check if it is enabled by going to `about:webrtc` or `chrome://webrtc-internals` in your browser. +Some browsers may block WebRTC access by default. You can check if it is enabled by going to `about:webrtc` or `chrome://webrtc-internals` in your browser. -Check if your extensions are not blocking WebRTC access. For example, Privacy Badger or Private Internet Access blocks WebRTC by default. +Check if your extensions are not blocking WebRTC access. Following extensions are known to block or does not work properly with WebRTC: +- Privacy Badger +- Private Internet Access +- PIA VPN (even if disabled) Test whether your client [supports](https://www.webrtc-experiment.com/DetectRTC/) and can [connect to WebRTC](https://www.webcasts.com/webrtc/). ## Networking -Most problems are networking related. +If you are absolutely sure, that your client is working correctly, then most likely your networking is not set up correctly. ### Check if your ports are correctly exposed using docker