From 713f74ff6a3cf677a2850b7831fd6a97e45d95a9 Mon Sep 17 00:00:00 2001
From: Adrien Lacombe <6303520+adrienlacombe@users.noreply.github.com>
Date: Fri, 27 Sep 2024 09:24:29 +0200
Subject: [PATCH] add details for beacon node on same machine

---
 docs/start/quickstart_group.mdx | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/docs/start/quickstart_group.mdx b/docs/start/quickstart_group.mdx
index 5e585b2fa..88a9202ec 100644
--- a/docs/start/quickstart_group.mdx
+++ b/docs/start/quickstart_group.mdx
@@ -579,7 +579,7 @@ services:
 ...
 ```
 
-3. Then, uncomment and set the `CHARON_BEACON_NODE_ENDPOINTS` variable in the `.env` file to your beacon node's URL
+3. Then, uncomment and set the `CHARON_BEACON_NODE_ENDPOINTS` variable in the `.env` file to your beacon node's URL. If your beacon node is running on the same machine, the URL is the LAN one, usually starting by `192.168.`.
 
 ```shell
 ...
@@ -588,6 +588,19 @@ CHARON_BEACON_NODE_ENDPOINTS=<YOUR_REMOTE_BEACON_NODE_URL>
 ...
 ```
 
+If you have `ufw` enabled, you might have to allow connections from the charon container to your beacon node.
+First get your charon container ip address by running
+
+```shell
+docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' charon-distributed-validator-node-charon-1
+```
+
+then using the IP (x.x.x.x) you just got
+
+```shell
+sudo ufw allow from x.x.x.x/16 to any port 5052 comment 'Allow Charon access to beacon'
+```
+
 4. Restart your docker compose
 
 ```shell