TelegramMessenger/MTProxy

MTProxy is a proxy server that routes Telegram client connections through the MTProto protocol to Telegram's servers.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 9th, 2026
Created on May 29th, 2018
Open Issues & Pull Requests: 339 (+0)
GitHub issues: Enabled
Number of forks: 1,135
Total Stargazers: 6,917 (+0)
Total Subscribers: 266 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

MTProxy is a proxy server that routes Telegram client connections through the MTProto protocol to Telegram's servers.

The tool solves the problem of accessing Telegram in environments where direct connections are blocked or restricted. It works by accepting client connections on a local port, authenticating them with a shared secret, and forwarding their traffic to Telegram's infrastructure. The proxy handles the MTProto protocol directly, allowing clients to connect via a simple link that can be shared or registered with Telegram's official proxy bot.

Operators should know that MTProxy requires obtaining a secret from Telegram, fetching current Telegram configuration (which changes occasionally and should be refreshed daily), and generating a separate secret for users. The tool supports multiple secrets simultaneously, allowing different users or groups to connect through the same proxy instance. It includes a statistics endpoint accessible via loopback on a configurable port. For networks where packet inspection occurs, random padding can be enabled by prefixing the client secret with `dd`, which obscures traffic patterns. The proxy can scale across multiple worker processes on powerful servers. Systemd integration is documented, and an official Docker image exists though it is outdated.

The project maintains active engagement with its user base through documentation of setup procedures and operational modes. Development activity shows responsiveness to practical deployment concerns, evidenced by features addressing ISP-level packet detection and the inclusion of privilege-dropping mechanisms for security. The codebase remains focused on core proxy functionality without feature bloat, reflecting a pragmatic approach to maintaining a stable, production-grade tool.