MTProxy appears to be completely ineffective / blocked in real-world usage (2025)

[GabrielKidd]

What I’ve tried

Fresh clone and rebuild of MTProxy from the official repository

Multiple secrets tested:

Classic secret

dd-prefixed secret

Fake-TLS style secret

Different listening ports:

443

8443

Random high ports

Verified the following:

MTProxy process is running normally

Listening ports are reachable from clients

TCP connections and initial handshakes complete successfully

Observed behavior

Telegram clients are able to reach the MTProxy server

However, the MTProxy server fails to complete a handshake with Telegram’s official servers

From logs and behavior, the failure occurs between the proxy and Telegram upstream, not between client and proxy

As a result:

Client connections stall indefinitely or time out

In some cases, a short-lived connection is established and then dropped

This behavior is consistent across:

Multiple VPS providers

Different geographic regions

Different ISPs and client networks

Conclusion

Although client → proxy connectivity works at the TCP level, proxy → Telegram server communication fails, making MTProxy unusable in practice.

This suggests that MTProxy traffic is either:

Blocked upstream,

Rejected by Telegram servers,

Or no longer compatible with the current Telegram backend infrastructure.