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
Connection through SOCKS5 proxy is dropped every 10 seconds #1323
Comments
Are you sure the proxy is SOCKS5 and not HTTP-only? |
Yes, it's NordVPN proxy and anything with 1080 port is SOCKS5: Also if it was a proxy issue, it will likely won't be able to establish the connection. In my case the connection is established, and the bot actually manages to send messages to chats. BUT, it cannot receive any messages. So handlers never get executed. And just to make sure this is not a proxy issue - I have another bot using different framework (in golang) that works without any issues with this proxy. I also tried HTTP proxy option (with a right port obviously) like that:
But it doesn't work:
And maybe a related question - howcome official telegram client connects without any proxies in Russia? They have some obfuscation methods embedded, or a different set of server IP addresses that are updated constantly? |
Can I maybe try v2 branch? Is it working? Will it break much besides the change from pysocks to python-proxy? |
You can try it, but it's pretty stale otherwise (ironically). |
Tried v2 - same problem:
|
Experiencing the same problem also:
|
I'm cleaning up proxy-related issues, so closing in favour of the new issue. |
Checklist
pip install -U https://github.com/LonamiWebs/Telethon/archive/master.zip
and triggered the bug in the latest version.Code that causes the issue.
Connection drops and re-establishes every 10 seconds
Note that this is based in Russia, so might be related with government blocking attempts of Telegram. Any potential workarounds? I'm already connected through SOCKS5 proxy and other telegram frameworks don't cause this type of issues.
The text was updated successfully, but these errors were encountered: