Skip to content

Commit 4801084

Browse files
committed
docs
1 parent b372d14 commit 4801084

1 file changed

Lines changed: 10 additions & 2 deletions

File tree

docs/config/remote.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,13 +60,21 @@ There are three ways to connect the web frontend to your ECA session. Pick the o
6060
**Steps:**
6161

6262
1. Install Tailscale and enable [HTTPS certificates](https://tailscale.com/kb/1153/enabling-https)
63-
2. Start ECA — it will log the connection URL and auth token to stderr. The URL is a deep-link you can open directly:
63+
2. Expose the ECA port range via Tailscale serve so they are reachable over your tailnet:
64+
65+
```bash
66+
sudo tailscale serve --bg --tcp 7777 tcp://localhost:7777
67+
sudo tailscale serve --bg --tcp 7778 tcp://localhost:7778
68+
# ... repeat for as many ports as you need (7777–7787)
69+
```
70+
71+
3. Start ECA — it will log the connection URL and auth token to stderr. The URL is a deep-link you can open directly:
6472

6573
```
6674
https://web.eca.dev?host=my-machine.tail1234.ts.net:7777&pass=a3f8b2c1...&protocol=https
6775
```
6876

69-
3. Open `https://web.eca.dev` and paste the connection URL or manually enter host and password
77+
4. Open `https://web.eca.dev` and paste the connection URL or manually enter host and password
7078

7179
Because Tailscale provides valid HTTPS certificates for your machine, the browser connects without any mixed-content issues or permission prompts.
7280

0 commit comments

Comments
 (0)