Proxy not working when i set AD_TAG
See original GitHub issueHi, 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"
Issue Analytics
- State:
- Created 5 years ago
- Comments:44 (22 by maintainers)
Top Results From Across the Web
mtg is much slower than official MTProxy implement · Issue #220
I run both mtg and official MTProxy implement on a same server, mtg is much slower. For ping, mtg always 50-100ms slower.
Read more >Link tag in React is not working with devserver-proxy
I'm following this tutorial to make my React app (localhost:3000) communicate with Node server (localhost:5000) .. so instead of typing ...
Read more >[ANDROID] Loading ads from local server - Google Groups
I'm trying to play video ads based on VAST xml stored on my local server. To be exact, on runtime, I start local...
Read more >IMAAdsRequest - Google Developers
Specifies the full URL to use for ads loading from an ad server. Required for any adsRequest . For details on constructing the...
Read more >ORD values - Campaign Manager 360 Help - Google Support
However, with caching, the browser or proxy server stores the ad image in a cache ... As a result, Campaign Manager 360 does...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks to @K900, who implemented the intermediate version of the protocol.
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