-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mtproto and ad tag problem #304
Comments
then ad tag enabled, the proxy uses middle proxy. Please check the server has connectivity to servers specified here: https://core.telegram.org/getProxyConfig I also updated outdated default address of server in the master branch: c894790 may be it will help |
@alexbers looks like the IPs and ports were changed again. Not only proxies but main IPs too. |
I've rechecked, they are still working. The main IP's also the same: https://github.com/telegramdesktop/tdesktop/blob/master/Telegram/SourceFiles/mtproto/mtproto_dc_options.cpp#L32 |
@alexbers you're right. I've checked another source, the pyrogram lib's docs. Btw, there's no middle proxies with 80 port open anymore in the list by the link you've given above. All the proxies are on 8888. |
fixed, thanks. |
Got same problem. I've installed two same copies of proxies on different VPS, first one is working well, but second only works when AD_TAG is empty. TG_MIDDLE_PROXIES_V4 = { |
My mt proto proxy is working just fine but when I add a Ad Tag to it in config file it just stop working in official versian it keeps flickering connecting and connected
Im on Ubuntu 22
Using direct ip for proxy
Please advise
The text was updated successfully, but these errors were encountered: