-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
telegram call stuck at exchanging encryption keys #23939
Comments
Hey! It's not impossible that this is the same bug I face on my issue #23916. I have the exact same problem (But not sure if it's due to Root CA) with my Firewall as I use a free proxy and it stays on exchanging keys. Hope you will find a solution to see if it works! Can I ask where did you find those Telegram logs? |
I am having the same problem with my MX-Linux 21. Has anyone found a workaround to this problem? |
Same problem on Arch Linux. No workaround still? |
Windows 11, same thing happens |
Same problem (behind socks5 proxy / vmess server) |
I don't think trusting custom CAs will be ever allowed as this effectively a MITM. @Aokromes maybe close this with wontfix? |
Same issue here Windows 11, tried with 2 different connections, mobile sharing and fiber... (I have a premium account if it changes anything) |
@raphaelcasimir this issue is about proxies with MITM feature, are you sure you have same issue? |
No sorry, do I delete my comment? |
Steps to reproduce
start Telegram Desktop behind Firewall / Proxies like Zscaler
Expected behaviour
successful exchange of encryption keys to initiate the call
Actual behaviour
stuck at exchanging encryption keys
cannot find documentation to make Telegram trust the custom Root CA of Zscaler Procy
Operating system
Win 10
Version of Telegram Desktop
v 3.4.8 19.01.22
Installation source
Static binary from official website
Logs
The text was updated successfully, but these errors were encountered: