💬 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
🚀 New Release: v4.8.0
DC health probes (#47).
- Periodic TCP handshake probes to all 5 Telegram DCs, exposed as Prometheus histograms (
- Disabled by default. Enable with
- Probes run in master process only with non-blocking poll for sub-millisecond accuracy
- Text stats include per-DC latency, average, count, and failure fields
Release notes | GitHub
DC health probes (#47).
- Periodic TCP handshake probes to all 5 Telegram DCs, exposed as Prometheus histograms (
teleproxy_dc_latency_seconds), failure counters, and last-latency gauges- Disabled by default. Enable with
--dc-probe-interval 30 (CLI), dc_probe_interval = 30 (TOML), or DC_PROBE_INTERVAL=30 (Docker env)- Probes run in master process only with non-blocking poll for sub-millisecond accuracy
- Text stats include per-DC latency, average, count, and failure fields
Release notes | GitHub
💬 Comment on #11: failed: auth error
A build cleanup script briefly removed platform manifests from the registry. It's been fixed and a new image is published.
Your container runtime cached the old manifest index. Force a fresh pull:
``
If you're on a system like Portainer or Watchtower that auto-updates, restart the update cycle so it re-fetches the index.
View comment
A build cleanup script briefly removed platform manifests from the registry. It's been fixed and a new image is published.
Your container runtime cached the old manifest index. Force a fresh pull:
``
docker pull ghcr.io/teleproxy/teleproxy:latest
If you're on a system like Portainer or Watchtower that auto-updates, restart the update cycle so it re-fetches the index.
View comment
💬 Comment on #49: Manifest unknown error while pulling the image.
@ant-222 apologies for stealing your attention!
View comment
@ant-222 apologies for stealing your attention!
View comment
🚀 New Release: v4.9.0
PROXY protocol v1/v2 listener support.
-
- Auto-detects v1 (text) and v2 (binary) headers, extracts real client IP from load balancer
- IP ACLs re-checked against the real client IP after header parsing
- v2 LOCAL command accepted for health check probes
- New stats:
- Prometheus metrics:
Other changes:
- Fix auto-generated secret not written to TOML config
- TON wallet donation option
- Per-page SEO metadata, OpenGraph tags, JSON-LD structured data, robots.txt
- Complete Russian translation (100%), expanded Farsi and Vietnamese (38%)
- Merged duplicate issue notification workflows
Release notes | GitHub
PROXY protocol v1/v2 listener support.
-
--proxy-protocol CLI flag / proxy_protocol = true TOML config / PROXY_PROTOCOL=true Docker env- Auto-detects v1 (text) and v2 (binary) headers, extracts real client IP from load balancer
- IP ACLs re-checked against the real client IP after header parsing
- v2 LOCAL command accepted for health check probes
- New stats:
proxy_protocol_enabled, proxy_protocol_connections, proxy_protocol_errors- Prometheus metrics:
teleproxy_proxy_protocol_connections_total, teleproxy_proxy_protocol_errors_totalOther changes:
- Fix auto-generated secret not written to TOML config
- TON wallet donation option
- Per-page SEO metadata, OpenGraph tags, JSON-LD structured data, robots.txt
- Complete Russian translation (100%), expanded Farsi and Vietnamese (38%)
- Merged duplicate issue notification workflows
Release notes | GitHub
👍2