When Discord is stuck on RTC Connecting, the client has not completed its connection to voice transport. Check Discord status, then compare another channel, official client, device, and network before changing firewall or router settings. Discord groups RTC Connecting with ICE Checking, No Route, and Connecting, and points to local interference such as a firewall or VPN as well as service-side faults.［1］

Key Takeaways

Confirm the exact connection state; microphone and speaker problems happen later.

Compare one other channel or private call before changing the whole device.

A second network is the fastest test for firewall, router, or managed-network scope.

Discord says VPN connections used for voice need UDP support.［1］

Preserve logs and versions before reinstalling or changing advanced settings.

The streaming and gaming hub covers broader failures. This guide is only for the connection state, not channel permission, microphone selection, robotic audio, or screen sharing.

1. Check that Discord is stuck on RTC Connecting, not another state

Read the status shown near the voice controls and note whether it stays on RTC Connecting, cycles through ICE Checking or No Route, or reaches connected but produces silence. Record the server, channel or private call, start time, client, and network. Do not combine distinct states into “voice broken.”

If Discord reaches connected, use the generic voice-chat guide for microphone or output issues, or the robotic audio guide for quality. RTC Connecting concerns establishing the transport.

Leave and rejoin once, then fully quit and reopen Discord. Avoid repeated rapid reconnects while an incident is active; they add little evidence and may obscure the original timing.

2. Is Discord reporting a service-side voice incident?

Check Discord’s official status page for voice, regional, or API incidents and compare a private call or another server. Discord says “Waiting for Voice Server” generally indicates broader service trouble and directs users to its status page.［1］ RTC Connecting can still be local, so status and scope should be considered together.

Ask one participant on another connection whether they can join the same channel. If several unrelated users fail at the same time, preserve the region and timestamp and wait before reinstalling. If everyone else connects, continue with your client and network.

Do not treat an unofficial outage chart or one social post as final proof. A service recovery that coincides with a local restart does not establish that the restart fixed it.

3. Does another channel, call, or official client connect?

Try one private call and one voice channel you are allowed to join. If only one channel fails, ask its administrator to check the channel and Region Override rather than changing system networking. Discord permits administrators to temporarily change a voice region in channel settings and also supports region changes in private calls.［1］

Compare the current desktop app with Discord in a supported browser, or the mobile app on the same account. Keep the network fixed. Update Discord and the operating system and fully restart the client; Discord’s broader guide recommends both.［2］

If only the browser fails, inspect site permissions and browser extensions. If only desktop fails, focus on app installation, firewall entry, and hardware-specific conditions. Do not run multiple Discord builds simultaneously during the baseline.

4. Does another network remove RTC Connecting?

Use the same device and client on one trusted alternate connection, such as mobile data instead of Wi-Fi. Discord’s mobile guide recommends switching between Wi-Fi and data to compare behavior.［2］ If the alternate works, the original router, ISP, firewall, DNS, proxy, or managed policy owns the difference.

Restart the modem, router, and computer once if you control them; Discord lists that sequence among its connection recommendations.［1］ Avoid factory resets, port-forwarding guesses, or disabling an organization’s controls.

If both connections fail on one device but another device works, focus on the first device. If every device fails on one connection, contact the network administrator or ISP with the exact test matrix.

5. Is a firewall, antivirus, or managed network blocking voice?

Confirm the official Discord application is allowed by the operating-system firewall and endpoint security. Discord recommends checking firewall and antivirus controls and notes that work or school networks may block voice.［1］ Use a temporary, documented test only if you own the device and can restore the prior state.

Do not permanently disable protection, add broad inbound rules, or open arbitrary router ports. On a managed network, ask the administrator whether real-time voice and required UDP traffic are permitted. A blocked policy is not an invitation to bypass it.

If the security product logs a block, preserve the timestamp, executable path, destination category, and rule name without sharing sensitive addresses publicly. Allow only the signed official client through the product’s supported workflow.

6. Does the VPN or proxy support Discord voice UDP?

Record whether a VPN, proxy, secure DNS filter, parental filter, or traffic inspection tool is active. Disconnect one reversible layer at a time and retry the same call. Discord states that its voice service only works with VPNs that support UDP.［1］

If Discord works without the VPN, confirm the VPN’s UDP capability and app-routing settings rather than cycling random regions. AethoVPN is one reversible diagnostic variable when it is already in the path, but it cannot guarantee a fix, override a managed network, repair Discord service, or change channel permission.

Restore the original network posture after the test. Do not send voice traffic through unknown free proxies or disable organizational inspection without permission.

7. Would a region override or documented client exception apply?

If you administer the affected voice channel, temporarily choose another Region Override and test once; record the old value so it can be restored. Discord explicitly recommends a region change as a connection test.［1］ Ordinary members should ask an administrator rather than changing unrelated server settings.

Only use hardware-specific guidance when the hardware and symptom match. Discord maintains an AMD GPU/CPU RTC_CONNECTING troubleshooting page for that conditional case.［3］ Confirm the actual processor or graphics hardware and current driver before applying it; do not install AMD software on unrelated systems.

Avoid mass-resetting Voice & Video options when the client never connects. Input mode, microphone gain, and noise suppression usually affect media after transport is established, not the RTC handshake itself.

8. What evidence should you provide to Discord or the administrator?

Provide the exact state sequence, timestamps, server and region without private invite links, client and operating-system versions, device, ISP or managed-network context, and results across another channel, official client, device, and network. Add whether firewall, VPN, proxy, and UDP support were tested.

Discord asks users with persistent connection errors to contact support and provide console-log screenshots; its broader guide also requests a detailed description, affected clients, versions, settings screenshots, device lists, and debug logs.［1］［2］ Review every screenshot for account identifiers, tokens, private messages, server names, and IP addresses before sharing.

Use official support channels. Do not paste raw logs into public forums or run commands supplied by strangers. A concise reproduction matrix helps the correct owner distinguish service, channel, client, device, and network scope.

Restore every temporary network or security change after the comparison and confirm one ordinary call still connects.

Summary

RTC Connecting is a transport-establishment problem. Confirm the state, check official status, compare channel and client, then isolate device and network. Change firewall, VPN, UDP, region, or hardware-specific settings only when the comparison points there, and preserve evidence for support.

FAQ

What does RTC Connecting mean in Discord?

It means Discord has not completed the real-time voice connection. It is different from being connected with a muted microphone or wrong output.

Is RTC Connecting always a Discord outage?

No. Discord groups it with errors commonly caused by local interference, while some waiting states can reflect service-side trouble.［1］

Can a school or work network block Discord voice?

Yes. Discord explicitly advises checking with the network administrator.［1］ Do not bypass managed policy.

Does Discord voice need UDP through a VPN?

Discord says VPNs used with Discord voice must support UDP.［1］

Should I change the voice region?

It is a useful temporary test for an administrator or private call. Save and restore the prior setting.［1］

Why does mobile data work but Wi-Fi does not?

The Wi-Fi path may differ in router state, ISP routing, firewall, proxy, filtering, or UDP policy.

Is microphone permission the cause of RTC Connecting?

Usually microphone permission affects capture after connection. If the transport connects but nobody hears you, use microphone troubleshooting.

Should every user follow the AMD guide?

No. Use it only when the affected system actually has the matching AMD hardware and symptom.［3］

Sources:

Discord Support - Voice Connection Errors — https://support.discord.com/hc/en-us/articles/115001310031-Voice-Connection-Errors
Discord Support - Voice and Video Troubleshooting Guide — https://support.discord.com/hc/en-us/articles/360045138471-Discord-Voice-and-Video-Troubleshooting-Guide
Discord Support - AMD GPU and CPU RTC_CONNECTING Troubleshooting — https://support.discord.com/hc/en-us/articles/4978019693463-AMD-GPU-CPU-RTC-CONNECTING-Troubleshooting

Sources checked 8 September 2026.

Related Articles:

Discord Is Stuck on RTC Connecting: What to Check