MtProxies working in Telegram X and not working in Telegram App
MtProto Proxies with custom domain names in the IP field are not working in blocked networks in Brazil if you are using the default Telegram app.
Although, using Telegram X you can access all proxies, with domain names or with direct IP address. (Using Telegram App you can only access MtProxies using direct IP)
There is no DNS block in Brazil. All proxies are working fine using Telegram X and Desktop. If I force a custom DNS they also become available in the default Telegram app.
This is happening with all users that are using mobile networks in Brazil.
All proxies in the screenshots should be working and are not blocked in Brazil.
Steps to reproduce
Connect to a brazillian mobile network (Vivo/Claro)
Add any working proxy with custom domain
Notice it doesn't connect with Telegram's main app
Notice it does connect normally with Telegram X
Device info
Telegram Android 9.6.3 (33449), Asus ZenFone 8/ ASUS 8Z, 13 (33)
All proxies in the screenshot are working normally in Telegram X and Telegram Desktop.
V
Viktor K.
I can reproduce a very similar issue with a private MTProto/FakeTLS proxy.
Setup: Private MTProto proxy using TeleMT/MTProxyMax FakeTLS EE secret Public hostname has only an A record, no AAAA DNS record is DNS-only, not proxied The hostname resolves to the same IPv4 address that works when used directly Same port and same secret are used in both tests
Observed behavior: server=<direct IPv4> works in Telegram Android server=<hostname> shows “Unavailable” in Telegram Android The same server=<hostname> works in Telegram Desktop Proxy metrics show traffic only when using direct IPv4 from Android Proxy metrics stay at zero when using the hostname from Android
Expected behavior: Telegram Android should resolve the hostname and connect to the same IPv4 address, like Telegram Desktop does.
Setup:
Private MTProto proxy using TeleMT/MTProxyMax
FakeTLS EE secret
Public hostname has only an A record, no AAAA
DNS record is DNS-only, not proxied
The hostname resolves to the same IPv4 address that works when used directly
Same port and same secret are used in both tests
Observed behavior:
server=<direct IPv4> works in Telegram Android
server=<hostname> shows “Unavailable” in Telegram Android
The same server=<hostname> works in Telegram Desktop
Proxy metrics show traffic only when using direct IPv4 from Android
Proxy metrics stay at zero when using the hostname from Android
Expected behavior:
Telegram Android should resolve the hostname and connect to the same IPv4 address, like Telegram Desktop does.