From 634a8ba0af8a825125eef6395e19fcc9c2cf3982 Mon Sep 17 00:00:00 2001 From: Ricki Moore Date: Thu, 31 Aug 2023 11:36:36 +0100 Subject: [PATCH] Update book/src/ui-faqs.md Co-authored-by: Age Manning --- book/src/ui-faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/ui-faqs.md b/book/src/ui-faqs.md index 1357c637eca..a5f793b76e1 100644 --- a/book/src/ui-faqs.md +++ b/book/src/ui-faqs.md @@ -14,7 +14,7 @@ The most effective approach to enable access for a local network computer to Lig Subsequently, by designating the host as `192.168.0.200`, you can seamlessly connect Siren to this specific beacon node and validator client pair from any computer situated within the same network. ## 5. How do I connect Siren to Lighthouse via a ssh tunnel? -If you would like to access Siren beyond the local computer, we recommend using an SSH tunnel. This requires a tunnel for 3 ports: `80` (assuming the port is unchanged as per the [installation guide](./ui-installation.md#docker-recommended), `5052` (for beacon node) and `5062` (for validator client). You can use the command below to perform SSH tunneling: +If you would like to access Siren beyond the local network (i.e across the internet), we recommend using an SSH tunnel. This requires a tunnel for 3 ports: `80` (assuming the port is unchanged as per the [installation guide](./ui-installation.md#docker-recommended), `5052` (for beacon node) and `5062` (for validator client). You can use the command below to perform SSH tunneling: ```bash