Skip to content

Commit

Permalink
Update book/src/ui-faqs.md
Browse files Browse the repository at this point in the history
Co-authored-by: Age Manning <[email protected]>
  • Loading branch information
rickimoore and AgeManning authored Aug 31, 2023
1 parent 1e3c27b commit 634a8ba
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion book/src/ui-faqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 634a8ba

Please sign in to comment.