mtg: Some media doesn't load

Without proxy everything works good. Logs are reporting connection to DC 203: mtg[974]: {"level":"warn","logger":"proxy","error":"cannot dial to Telegram: cannot dial to 203 dc: %!w(<nil>)","timestamp":1631898230591,"message":"cannot dial to telegram"}

What could be wrong? I use simple-run mode and run it like that: mtg simple-run 0.0.0.0:443 eeSECRETHERE7777772e676f6f676c652d616e616c79746963732e636f6d -d

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 5
Comments: 20 (14 by maintainers)

Most upvoted comments

So, after some research I want to make a following conclusion:

203 DC is something that is coming from CDN and should not leak into mtproto proxy. So, this is definitely a bug in a client
I can’t use gotd because it is required to have api key. mtg won’t embed or require keys from Telegram
getProxyConfig from core.telegram.org returns only those proxies that support middle ones.

So far, I do not know how I could help. If one has any idea where to map these unknown DCs, this help is appreciated. I would try out to fallback to default DC for now which is 2. Thus, I close this issue.

Feel free to reopen if something will change.

9seconds on Dec 10, 2021