tproxy-relay
Self-hosted WEB-proxy relay for Telegram MTProto traffic, masking it as ordinary HTTPS behind nginx with Docker Compose.
Ficha actualizada 23 sept 2026, 17:11 · upstream 23 sept 2026, 16:34 · release v1.2.0
Qué es tproxy-relay
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
tproxy-relay is a self-hosted web proxy relay that masks Telegram MTProto traffic as ordinary HTTPS. It uses C#/.NET 10 and Docker Compose to create a transparent layer between the client browser and the official MTProxy backend. The setup requires only nginx, Let's Encrypt certificates, and two containerized services: one acting as the public-facing web proxy (exposing port 8080) and another running the official MTProxy server on port 2398 inside a Docker network. This approach allows Telegram Desktop to connect normally while the actual relay logic remains hidden from external users.
- Telegram Desktop users who want to use MTProto without exposing their real IP or domain to censorship filters
- Organizations requiring encrypted communication channels that appear as standard HTTPS connections
- Developers needing a clean, containerized solution for routing Telegram traffic through an internal relay service
- Users with restricted internet access where direct MTProxy access is blocked but web proxying is permitted
- MTProto traffic is completely masked as ordinary HTTPS, making it indistinguishable from normal website traffic to any external observer
- The official MTProxy server runs in a separate Docker container inside the relay's docker network, keeping it isolated and hidden from outside users
- Supports multiple transport layers including long-polling https, websocket, and dedicated lanes for streaming data with flow control
- Each client receives its own unique secret and process ID, ensuring complete isolation between different Telegram clients
- Built-in budget management, rate limiting, per-IP limits, and automatic 503 responses with Retry-After headers when resources are exhausted
- Requires a public IP address for the MTProxy container to receive incoming connections from Telegram Desktop
- The official MTProxy server must be installed on the same machine or accessible via Docker network; no remote relay option is supported
- Telegram Desktop 7.2+ is required as the client application, with earlier versions not fully supported
- Only HTTP/HTTPS and WebSocket transports are supported; other protocols like API calls require manual configuration
- The base path feature requires a custom setup script to generate unique credentials for each base path variant
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Install nginx as systemd service on the host, configure Let's Encrypt certificates via webroot method, and deploy both containers using docker compose. The public-facing container listens on port 8080 while the MTProxy container runs internally on port 2398 within a Docker network. Always verify the health endpoint at /readyz before connecting clients. For production use, consider setting up SSL termination at the nginx level or configuring your own certificate authority for full control over certificates.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.