search

ferdium / ferdium-app

All your services in one place, built by the community
https://ferdium.org
Apache License 2.0
2.93k stars 176 forks source link

Bug: Telegram Call never connects and is stuck at a "Exchanging encryption keys" message #832

Open gaylie opened 1 year ago

gaylie commented 1 year ago

Avoid duplicates

Ferdium Version

6.2.3-nightly.5

What Operating System are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Ferdium version

A month or two ago

Expected Behavior

When calling someone on Telegram it connects and we can voice-chat.

Actual Behavior

When calling someone on Telegram it gets stuck on a "exchanging encryption keys" screen endlessly and never properly connects. Voice-chatting on Telegram via Ferdium is impossible.

Steps to reproduce

  1. Start Ferdium
  2. Set up a Telegram Service
  3. Start a call
  4. Get the call accepted

Debug link

https://debug.ferdium.org/6b6b82aa-2016-43c4-8ba1-b4164d72c6f7

Screenshots

image

Additional information

This issue has persisted after various updates, cache-clearings and restarts. However the same issue doesn't exist on a different PC.

Alphrag commented 1 year ago

Hi, this can be related to the WebRTC IP handling policy. Can you please check which settings is it on (in settings->privacy)? If it is on "do not expose public or local IPs", please try the other possibilities. (we might need to modify our collection of debug information as this section of the settings doesn't appear in there so I couldn't just look at it, even though you did well by including it... 😞 )

gaylie commented 1 year ago

@Alphrag This fixed it! Thank you very much :)

gaylie commented 1 year ago

After the most recent update (6.5.3) this issue came back... My WebRTC IP Handling is set to, "Expose user public IP, but not expose user local IP", which used to work till before the update.

idomusha commented 1 year ago

I think this time the issue is on Telegram side: https://bugs.telegram.org/c/33619 Tested directly on web.telegram.org and I could reproduce it. Rolled back to a previous version of Ferdium didn't fix it either.