dir/telegram-web-proxy-stack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: verify proxy domain after deployment

Browse Source
This commit is contained in:
Maintainer
2026-10-14 18:15:57 +07:00
parent 7ebde9cff4
commit c19de56558
5 changed files with 29 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -1
View File
@@ -54,7 +54,8 @@ sudo ./quick-install.sh
The script asks only for the hostname. It resolves the public IPv4 from DNS,
installs Docker from Docker's official package repository, deploys the proxy and
Caddy, obtains the TLS certificate, and prints the Telegram connection values.
Caddy, obtains the TLS certificate, verifies a unique response from this exact
proxy instance, and prints the Telegram connection values.
Inbound TCP ports 80 and 443 must be allowed by the VPS provider. This is a
separate deployment mode and does not require Nginx Proxy Manager.