From 1c228a7daa57a8d4260de5a3b88773cf6fefe8f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20=C5=A0ediv=C3=BD?= Date: Wed, 4 Jan 2023 23:16:17 +0100 Subject: [PATCH] update troubleshooting docs. --- docs/getting-started/troubleshooting.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/getting-started/troubleshooting.md b/docs/getting-started/troubleshooting.md index 967347d6..1f6381a0 100644 --- a/docs/getting-started/troubleshooting.md +++ b/docs/getting-started/troubleshooting.md @@ -4,6 +4,10 @@ Neko UI loads but you don't see the screen and it gives you `connection timeout` ## 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. + +Check if your extensions are not blocking WebRTC access. For example, Privacy Badger or Private Internet Access blocks WebRTC by default. + Test whether your client [supports](https://www.webrtc-experiment.com/DetectRTC/) and can [connect to WebRTC](https://www.webcasts.com/webrtc/). ## Networking @@ -113,6 +117,25 @@ services: If you want to use n.eko only locally, you must put here your local IP address, otherwise public address will be used. +### Neko works externally, but not locally + +You are probabbly missing NAT Loopback (NAT Hairpinning) setting on your router. + +Example for pfsense with truecharts docker container: +- First, port forward the relevant ports 8080 and 52000-52100/udp for the container. +- Then turn on `Pure NAT` pfsense (under system > advanced > firewall and nat). + - Make sure to check the two boxes so it works. +- Make sure `NEKO_NAT1TO1` is blank and `NEKO_IPFETCH` address is working correclty (if unset default value is chosen). +- Test externally to confirm it works. +- Internally you have to access it using `:port` + + +### Neko works locally, but not externally + +Make sure, that you are exposing your ports correctly. + +If you put local ip as `NEKO_NAT1TO1`, external clients try to connect to that ip. But it is unreachable for them, because it is your local IP. You must use your public IP address with port forwarding. + ## Debug mode To see verbose information from n.eko server, you can enable debug mode using `NEKO_DEBUG`.