mtprotoproxy: Proxy not working when i set AD_TAG

Hi, When AD_TAG is set proxy not working anymore…

PORT = 3259

# name -> secret (32 hex chars)
USERS = {
    "tg":  "0123456789abcdef0123456789abcdef"
}

# Tag for advertising, obtainable from @MTProxybot

AD_TAG = "02b86204e28dfceda581080dd966179c"

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 44 (22 by maintainers)

Most upvoted comments

Thanks to @K900, who implemented the intermediate version of the protocol.

alexbers on Jun 18, 2018

Quarx2k: could you test the latest version of the program in master branch. The https://github.com/alexbers/mtprotoproxy/commit/a6e39a66d160de5055232c35f5fd7fa6e85697be should fix work in the Telegram X beta for Android

alexbers on Jun 18, 2018

When you enable advertising, other servers are used for communication to pass AD_TAG. The protocol of communication with that other servers requires knowing your current external ip. One of the reason the configuration with tags doesn’t work is a problem with external ip determination. That is why I asked to check if external ip is detected properly in string tg://proxy?server=<IP_ADDR>&port=3259&secret=0123456789abcdef0123456789abcdef

Also, it your server is behind NAT and NAT equipment changes the source port, it won’t work (official proxy also likely won’t work in this case).

alexbers on Jun 4, 2018

Hi, I checked a proxy with this config and it works for me.

Do your server is behind NAT? After launch the proxy should tell the ip address tg://proxy?server=<IP_ADDR>&port=3259&secret=0123456789abcdef0123456789abcdef

Does this ip address is the same as your external address?

Also, it is interesting on which platform the telegram client is running: ios/android/windows.

alexbers on Jun 4, 2018