English
日本語English简体中文暂无翻译，前往中文首页EspañolSin traducción: ir al inicio en español

If this page is not translated, the link opens that language’s home page.

Discord

Discord Stuck on RTC Connecting: Device, Network and Channel Checks

For Windows desktop Discord stuck on RTC Connecting when joining a voice channel or DM. Browser and phone comparisons help narrow the scope.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-18
Saved articles →
No account needed. Saved only in this browser.

The short answer

Check incidents, then compare another destination, browser Discord on the same PC, and an available second device/network one at a time. Network-only failure prioritizes that connection; app-only failure prioritizes app settings. AMD-specific guidance is an additional check when the hardware matches and browser voice works.

Different symptom or still not fixed? Find the next check →

Key facts

Record the exact error
RTC Connecting, No Route and Awaiting Endpoint are observations, not a hardware diagnosis
Success means a real call
Confirm a short conversation, not merely loading text chat
Keep comparisons separate
Change the client, device or network individually

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
Several people fail together, or Awaiting Endpoint appearsCompare the time with Discord Status and wait for a relevant incident to recover.Step 1
One channel fails; a DM or another channel worksAsk its administrator to compare the voice region.Step 4
Browser voice works on the same PC and connectionInspect app updates/settings; use AMD checks only for the matching hardware.Step 5
Another device fails on the same Wi-Fi; another network worksPrioritize the original connection, router path and VPN.Step 3
Another device works on the same Wi-Fi; only the PC failsCompare app/browser, PC VPN and targeted connection permissions.Step 2
The same destination fails across devices and networksCompare another destination and share results with its administrator.Step 4
The connection completes but voices are missingSeparate output/microphone issues from connection failure.Step 1

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Check the error and incidents, then rejoin

A prolonged RTC Connecting message does not identify a failed router or GPU.

Time: Compare one change at a time

  1. Record the exact message and time, then inspect Discord Status for a matching incident.
  2. During a relevant incident, retry the same call after recovery. If nothing is posted, ask whether other participants failed at the same time; an empty status page is not proof that every service is healthy.
  3. Leave and rejoin once. If unchanged, quit Discord from the notification area and reopen it to apply updates.
  4. After connection, confirm a short conversation. For a connected but silent call use the output/microphone guides; for later disconnections use the call-disconnection guide.

Results that did not fix the problem help the next reader too.

Step 2｜Compare destination, browser and device

Keep account, destination and connection unchanged wherever possible.

Time: Compare one change at a time

  1. On the same PC/network, try another permitted voice channel or a DM with a willing person. If only one destination fails, use Step 4.
  2. End the app call and open https://discord.com/app on the same PC. Join the same destination/account with required microphone permission. Opening the chat page alone is not a successful voice test.
  3. If browser voice works, use Step 5. If both clients fail, compare a phone on the same Wi-Fi if one is available.
  4. Confirm whether the phone actually uses Wi-Fi or mobile data. Same-Wi-Fi phone success prioritizes the PC; both failing prioritizes the network comparisons in Step 3.
  5. Record results separately, for example app fails / same-PC browser works / phone on Wi-Fi works. That example prioritizes the app without proving a cause. Mark unavailable tests as untested.

Results that did not fix the problem help the next reader too.

Step 3｜Inspect network, VPN and PC permissions

Another connection working narrows the path; it does not prove a particular router setting is wrong.

Time: Compare one change at a time

  1. Where permitted, compare the same PC and call on another connection, such as your own hotspot. Keep it brief, account for data limits and restore the original connection afterward.
  2. For a personal VPN you control, temporarily compare it disconnected. If that helps, ask its provider about UDP support/configuration; Discord documents that voice requires a UDP-capable VPN.
  3. For home-network-only failure, inspect the provider’s incidents. Check shared users before restarting the modem/router by its manufacturer’s instructions. Do not press factory reset.
  4. For PC-only failure, inspect security software’s block history for Discord at the relevant time. Give a managed PC/network administrator the comparison results instead of bypassing their rules.
  5. If Voice & Video shows enabled high-priority QoS, record it, disable it temporarily and compare the same call. Skip an absent setting and restore it if unhelpful.

Do not disable the whole firewall, guess ports to open or bypass school/work restrictions. Use another-network results as evidence for the administrator/provider.

Results that did not fix the problem help the next reader too.

Step 4｜For one channel, compare its voice region

Coordinate with its administrator because the change affects other participants.

Time: Compare one change at a time

  1. Confirm a DM or another channel works on the same PC/network and share the affected channel and other participants’ results with its administrator.
  2. With management permission, right-click the voice channel → Edit Channel → Overview → Region Override. Record Automatic or the existing region.
  3. After coordinating with participants, temporarily select another available region. Without permission, ask the administrator to make the comparison.
  4. Rejoin with the same people and verify a short conversation. Restore the original region if unchanged; if improved, agree on the ongoing setting with the administrator.

Results that did not fix the problem help the next reader too.

Step 5｜For app-only failure, check updates and AMD conditions

The AMD-specific official article dates from 2022 and describes rare cases, mainly on older hardware. It is not a universal RTC repair.

Time: Compare one change at a time

  1. Fully quit/reopen Discord and restart the PC, then compare app and browser again using the same call destination.
  2. Check whether the PC has an AMD CPU or GPU. Windows Settings → System → About identifies the processor; Windows+R → dxdiag → Display identifies GPU/driver details.
  3. Only with matching AMD hardware and working browser voice, inspect the official AMD article. If OpenH264 Video Codec provided by Cisco Systems, Inc. is present and enabled under Voice & Video, record it, disable it and compare.
  4. If the control is absent, skip it rather than guessing a replacement. Restore an unhelpful change. Check drivers through the PC/GPU manufacturer’s instructions separately from codec changes.
  5. App-only failure can also occur without AMD hardware. After recording input/output devices, levels and keybinds, consider the optional Reset Voice and Video Settings control under Debugging. Reselect devices and retest; consider reinstalling only if the problem persists.

AMD hardware alone does not establish the cause. Before reinstalling, preserve your login email/password and MFA access and use the not-opening guide’s specific instructions.

Results that did not fix the problem help the next reader too.

Copy a support-notes template

Summarize comparisons for the administrator or official support. Copy the blank template and fill it in locally. This area does not accept or submit your answers.

Do not include passwords, tokens, authentication codes, public IP addresses, email addresses or invite links. Hide personal information in screenshots and logs too.

Fictional completed example

This illustrates record keeping only. Browser success does not prove the cause or lasting recovery.

Fictional example — not an actual incident or recovery report
Time: 20XX-XX-XX 20:00 UTC
Display: RTC Connecting; no additional error
Windows 11; app and browser versions unconfirmed
Status: checked 20:05; no voice incident found at that time
Same destination: PC app fails; same-PC/same-network browser works
Other same-Wi-Fi device and same-PC other network: untested
DM and another channel both fail in the app (names omitted)
No VPN; home network
QoS on → off: no improvement; restored to on
After restart: app fails; a short browser conversation works
Long sessions and later recurrence: untested

Avoid

  • Do not infer router/GPU failure from the error alone or change several network settings together.
  • Do not broadly disable protection or apply the AMD codec check to every PC.

Important cautions

  • Record exact error/time, client versions, same-PC app/browser, same-Wi-Fi device, other-network results, DM/channel differences, VPN and each changed/restored setting. Use the blank memo on this page without including secrets.
  • The official connection-error guide includes PTB/Canary console-log collection if needed. First gather ordinary-client comparisons; submit logs privately through official support with personal information removed.

FAQ

Why does browsing work while RTC Connecting stays stuck?

Loading websites or text chat does not verify a voice connection. Compare real conversation in the same-PC browser and, where available, another network.

How many minutes should I wait?

There is no universal recovery time. For a relevant incident wait for recovery; otherwise record the error/time and proceed through comparisons after rejoining fails.

Should every AMD PC disable OpenH264?

No. The dated official article concerns some AMD environments. First verify browser voice works, then check the hardware and whether that exact control exists.

Does hotspot success prove my router is broken?

No. The original connection, routing, VPN and router configuration differ. Share the same-PC/same-destination comparison with the administrator/provider.

Sources

English adaptation preserving the Japanese guide’s step IDs, comparisons, precautions and official sources. Examples describe how to record results; they are not measured outcomes or promises of recovery.

Discord: voice connection errorsDiscord: voice, video and screen-share troubleshootingDiscord: conditional AMD RTC troubleshooting (2022)Discord Status: service incidentsDiscordJapanese version of this page