Discord web app not working on pre-installed firefox

Hi! I’m having problems with firefox (wayland) and discord (using it as a web app). Whenever I join a call the ping skyrockets to 50,000 ms, and i get constantly connected and disconnected from ti. when i ping externally my connection is fine, and when I log in through other browsers/the electron app everything seems fine. I’ve noticied that on the electron app it says my calls are end-to-end encrypted while on firefox it defaults to secure connection. My theory is that theres a problem with my input-firefox that is not configured correctly,or perhaps a privacy setting.

Either way, i’ve tried the following and hasn’t fixed the issue:

  • disabled ipv6
  • media.peerconnection.default_address_only set to true
  • media.peerconnection.ice.no_host set to true
  • changed my dns settings (cloudfare, google, nextdns)
  • launched firefox on x11 profile
  • installed other versions of firefox (aur, flathub)
  • changed my network profile from public to home

Most people use the electron app to avoid such headaches, but I’d like to minimze mbs used on my system, and I know for a fact that discord calls work through web on other setups (for example, arch, official repo, and wayland), so there must be something unique going on in mine. My theory is that it’s a combination of the firewallid and the firefox settings, but I’m not really sure.

Any guidance is appreciated.

Oh and maybe this is tangentally related (and perhaps more common) issue that i get on firefox is that sometimes pages say “unable to load” or “not found” even if i am connected to the internet, reloading the page of waiting a few seconds fixes this, but this could possibly also be something related to dns or the resolver, or even NM or systemd networking.

1 Like

Are you using Quad9 for DNS? It started misbehaving for me a few days ago.

I am, just removed it, let’s see if it stops showing “unable to connect”.

Digged a bit into this and turns out firefox was automatically selecting a dead POP for discord calls, i’m using a hotspot and using internet through ethernet-usbc, so forcing firefox to recognize the interface as eth0 fixed the issue for me. Should I fill a bug report? if so where? is this a firefox issue or a systemd-network issue?

EDIT:
Oh, and it seems to be unrelated to the “unable to connect” issue, this seems to be random and a dns issue, still happens to me even after not using quad9.

1 Like

I also have this issue since monday, though my internet is really sh*t, but it looks like Firefox issue, I use floorp and I can reproduce it easily, but it rarely happens on brave browser

Again, my connection is :poop:, but after reading your topic I guess it’s not because of my Internet after all

It turns out that it may be due to a kernel issue.

oh thanks, looks like theres a patch incomming, excited to see this fixed.