tdesktop
tdesktop copied to clipboard
telegramdesktop
telegram call stuck at exchanging encryption keys
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
[2022.01.20 16:06:34] Audio Info: recreating audio device and reattaching the tracks
[2022.01.20 16:06:37] Audio Info: Closing audio playback device.
[2022.01.20 16:06:58] Audio Info: recreating audio device and reattaching the tracks
[2022.01.20 16:07:00] Audio Info: Closing audio playback device.
[2022.01.20 16:07:37] Audio Info: recreating audio device and reattaching the tracks
[2022.01.20 16:07:39] Audio Info: Closing audio playback device.
[2022.01.20 16:12:17] Audio Info: recreating audio device and reattaching the tracks
[2022.01.20 16:12:18] OpenGL: [TRUE] (Window)
[2022.01.20 16:12:18] RPC Error: request 356 got fail with code 400, error FILE_REFERENCE_EXPIRED
[2022.01.20 16:12:24] Call Info: Creating instance with version '3.0.0', allowP2P: [TRUE]
[2022.01.20 16:12:25] Audio Info: Closing audio playback device.
[2022.01.20 16:12:25] Call Error: Unexpected state in handleStateChange: 4
[2022.01.20 16:12:31] Audio Info: recreating audio device and reattaching the tracks
[2022.01.20 16:12:33] Audio Info: Closing audio playback device.
[2022.01.20 16:43:25] Export Info: Panel Hide By Cancel.
[2022.01.20 16:43:25] Export Info: Panel Hide Requested.
[2022.01.20 16:43:25] Export Info: Panel Closed.
[2022.01.20 16:43:25] Export Info: Stop requested.
[2022.01.20 16:43:25] Export Info: Destroying.
[2022.01.20 16:43:25] Export Info: Destroy top bar by controller removal.
[2022.01.20 16:43:25] Export Info: Controller destroyed.
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?
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? I am going to try to find the right issue