Discord web is stuck on RTC connecting.
I am using firefox 76 and the problem occurs when joining voice chat on discord web. The status will be stuck on RTC connecting and i cant hear or speak to other people. I have tried using discord web on google chrome and it works fine so the problem isn't with my device hardware or internet.
Todas as respostas (4)
I have the same problem. I used Edge to verify discord works on my PC and it works fine in Edge so there is no router or external internet problem. There is some setting in firefox which is preventing this from working. Discord was working in firefox last week in version 73. I did make some change to firefox 73 settings because I wanted autoplay disabled. I *think* it quit working after I made the settings change. I used about:support to check what config had been changed and changed the media.autplay.default from 0 back to 1 but it still doesn't work. I cleared the cache and cookies and that didn't help. I tried installing the update to 76 and it still doesn't work. I have verified that other people in the chat can both hear and speak to each other. No one can hear me and I can't hear them. The mic is enabled in firefox. I ran the discord mic test and that works. It just will not connect to the RTC server.
I also went through the steps to reset firefox by clicking menu, troubleshooting, reset firefox and it is still stuck on RTC Connecting.
Hello bryon timon and B.R.,
See this bug report (last two comments posted only a few hours ago) :
https://bugzilla.mozilla.org/show_bug.cgi?id=1367049
This is what Discord has to say :
https://support.discord.com/hc/en-us/articles/115001310031-Voice-Connection-Errors
SOLVED! I contacted discord about the problem and they suggested three steps to try:
1. Make sure the computer has no virus by running malwarebytes. 2. Try setting my DNS to google public DNS. 3. Refresh and renew my IP address by opening a command prompt in administrator mode and typing three commands:
a. ipconfig /release b. ipconfig /flushdns c. ipconfig /renew
Given that my computer works with Edge, I took the liberty of assuming the first two steps really weren't necessary because 1. If it had a virus it is likely to affect all browsers (notice I said 'likely'). 2. They both should be using the same DNS, so changing that shouldn't affect anyting. So I jumped immediately to step three. Step three also happens to be the easiest and least intrusive to do, and I could always go back and do steps 1 & 2 and then step 3 again if necessary. I closed my discord connection (closed Edge) and then typed in those three instructions. It started working immediately. The only thing I didn't do was verify that there was still a problem before I typed in those instructions because it had been several days since I'd tried it.