🚀 New Release: v4.5.0
QR codes for connection links.
-
- Docker
- Vendored nayuki/QR-Code-generator (MIT) for zero-dependency QR rendering on any platform
- E2E tests decode the rendered QR output with pyzbar and verify it matches the expected URL
- Documentation: new "Connection Links" page (en + ru)
Release notes | GitHub
QR codes for connection links.
-
teleproxy link subcommand prints a proxy URL and renders a scannable QR code in the terminal using UTF-8 half-block characters- Docker
start.sh and install.sh now display QR codes automatically at startup — point a phone camera at the screen to connect- Vendored nayuki/QR-Code-generator (MIT) for zero-dependency QR rendering on any platform
- E2E tests decode the rendered QR output with pyzbar and verify it matches the expected URL
- Documentation: new "Connection Links" page (en + ru)
Release notes | GitHub
💬 Comment on #37: QR-CODE (Mikrotik)
Fixed in e9292d4 — open
View comment
Fixed in e9292d4 — open
http://<your-server>:8888/link in a browser to get scannable QR codes.View comment
👍1
💬 Comment on #38: Healthcheck always unhealthy with custom ports
Fixed in v4.6.0. The Dockerfile and docker-compose.yml healthchecks now use
View comment
Fixed in v4.6.0. The Dockerfile and docker-compose.yml healthchecks now use
${STATS_PORT:-8888} instead of a hardcoded port, exactly as @FFourtyTwo suggested. Also added a CI test that starts the container with a non-default STATS_PORT to prevent regression.View comment
💬 Comment on #37: QR-CODE (Mikrotik)
Available since e9292d4 — the
View comment
Available since e9292d4 — the
/link endpoint serves HTML with QR codes, works from any browser including Mikrotik's webfig.View comment
💬 Comment on #25: QR codes for connection links
Shipped across two releases:
- v4.5.0:
- v4.6.0:
View comment
Shipped across two releases:
- v4.5.0:
teleproxy link subcommand + terminal QR codes at startup- v4.6.0:
/link HTTP endpoint serves HTML pages with scannable QR codesView comment
💬 Comment on #39: Russian DPI (TSPU) blocking fake-TLS connections (April 2026)
v4.6.0 is out with the server-side mitigations described above:
- ServerHello encrypted size variation widened to ±32 bytes
- ServerHello/CCS split into separate TCP segments
- New DPI Resistance docs page
These reduce fingerprinting surface but won't fix detection on their own — the core issue is the client's TLS fingerprint. Track tdesktop#30513 for the client-side fix.
View comment
v4.6.0 is out with the server-side mitigations described above:
- ServerHello encrypted size variation widened to ±32 bytes
- ServerHello/CCS split into separate TCP segments
- New DPI Resistance docs page
These reduce fingerprinting surface but won't fix detection on their own — the core issue is the client's TLS fingerprint. Track tdesktop#30513 for the client-side fix.
View comment
👍3
💬 Comment on #37: QR-CODE (Mikrotik)
Fixed in 21b22d9 — the
View comment
Fixed in 21b22d9 — the
/link page now detects Docker-internal and loopback IPs and substitutes the external IP from --nat-info.View comment
💬 Comment on #22: SOCKS5 upstream proxy support
Implemented in aae0470, documented in 354af2c.
View comment
Implemented in aae0470, documented in 354af2c.
View comment
👍1
💬 Comment on #49: Manifest unknown error while pulling the image.
Fixed in 8465e7e. A cleanup step in the build workflow was incorrectly deleting untagged platform manifests that the multi-arch index references.
View comment
Fixed in 8465e7e. A cleanup step in the build workflow was incorrectly deleting untagged platform manifests that the multi-arch index references.
docker pull ghcr.io/teleproxy/teleproxy:latest works again.View comment