From 303b273c77b7e6c6660d81c76049f525a2efc109 Mon Sep 17 00:00:00 2001 From: Alexander <32452033+avbor@users.noreply.github.com> Date: Fri, 10 Apr 2026 11:52:58 +0300 Subject: [PATCH] Update VPS_DOUBLE_HOP.en.md --- docs/Setup_examples/VPS_DOUBLE_HOP.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Setup_examples/VPS_DOUBLE_HOP.en.md b/docs/Setup_examples/VPS_DOUBLE_HOP.en.md index df960e8..093239b 100644 --- a/docs/Setup_examples/VPS_DOUBLE_HOP.en.md +++ b/docs/Setup_examples/VPS_DOUBLE_HOP.en.md @@ -163,7 +163,7 @@ PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data. --- ## Step 2. Installing telemt on Server B (conditionally Netherlands) -Installation and configuration are described [here](https://github.com/avbor/telemt/blob/main/docs/Quick_start/QUICK_START_GUIDE.en.md) or [here](https://gitlab.com/An0nX/telemt-docker#-quick-start-docker-compose).\ +Installation and configuration are described [here](https://github.com/telemt/telemt/blob/main/docs/Quick_start/QUICK_START_GUIDE.en.md) or [here](https://gitlab.com/An0nX/telemt-docker#-quick-start-docker-compose).\ It is assumed that telemt expects connections on port `443\tcp`. In the telemt config, you must enable the `Proxy` protocol and restrict connections to it only through the tunnel.