Discord Stuck at RTC Connecting? Fixes That Work

If Discord is stuck at “RTC Connecting,” your voice chat can’t establish a connection, and the fix usually involves clearing your network cache, changing your server region, or adjusting your firewall. This error appears when Discord’s WebRTC (Real-Time Communication) can’t reach its voice servers, and while it’s frustrating, it’s typically resolved in a few minutes. Below, we’ll walk through the most common causes and the step-by-step fixes that actually work.

What Does “RTC Connecting” Mean?

RTC stands for Real-Time Communication, the technology Discord uses to transmit your voice and video with low latency. When you see “RTC Connecting” under a voice channel name, it means your client is trying to establish a WebRTC connection to Discord’s voice servers but hasn’t succeeded yet. This can happen for a few seconds during a normal join, but if it persists, something is blocking or misrouting that connection.

The status appears in the bottom-left corner of the voice channel panel, often with a yellow or red indicator. A yellow icon means it’s still trying; a red icon usually means it’s failed and will retry. The key thing to understand is that this is a network-level issue, not a problem with your Discord account or your headset.

Why Does This Happen? (Common Causes)

Several factors can cause the RTC Connecting loop. The most frequent culprits are:

Network congestion or packet loss: Your ISP or local network might be dropping the UDP packets that voice chat relies on.
Firewall or antivirus interference: Security software sometimes blocks Discord’s voice ports (UDP 50000-65535) while allowing the main app to load.
VPN or proxy issues: A VPN can route your traffic through a server that Discord’s voice system doesn’t handle well, or it can add too much latency.
Outdated DNS cache: Your computer may be trying to connect to an old or unreachable Discord server IP.
Server region problems: The Discord server you’re in might have its region set to a location that’s far away or temporarily overloaded.
Corrupted Discord cache: Temporary files in Discord’s cache folder can sometimes cause connection loops.

How to Fix It: Step-by-Step

Try these fixes in order, testing your voice connection after each one. Most users resolve the issue with the first or second step.

Change your voice region (quickest fix): In a server, go to Server Settings > Overview > Server Region and pick a different region that’s close to you. This forces Discord to connect to a different voice server. If you’re in a DM call, you can’t change the region, but you can leave and rejoin the call.
Toggle your voice device: Go to User Settings > Voice & Video and change your input and output devices to something else, then switch back. This resets the audio subsystem and sometimes kicks the RTC connection.
Clear Discord’s cache: Close Discord completely (check the system tray). Press Windows+R, type %appdata%/discord and press Enter. Delete the Cache, Code Cache, and GPUCache folders. Restart Discord. On Mac, use ~/Library/Application Support/discord.
Flush your DNS and reset network: Open Command Prompt as administrator and run ipconfig /flushdns. Then restart your router by unplugging it for 30 seconds. This clears any stale IP mappings.
Disable your VPN or proxy: Temporarily turn off your VPN and try joining a voice channel again. If it works, your VPN is the problem. You may need to switch to a different VPN server or use split-tunneling to exclude Discord.
Add Discord to your firewall exceptions: Ensure Discord is allowed through Windows Defender Firewall (or your third-party firewall) for both private and public networks. Look for “Discord” in the allowed apps list and enable both checkboxes.
Reinstall Discord: If nothing else works, uninstall Discord completely (including the %appdata%/discord folder) and download a fresh copy from the official website. This resets all settings and cache.

Advanced Fixes for Persistent Issues

If the basic steps don’t help, you can try a few more technical approaches. These are safe but require a bit more comfort with system settings.

Switch to a different DNS server: Use Google’s (8.8.8.8 and 8.8.4.4) or Cloudflare’s (1.1.1.1) DNS. This can resolve issues where your ISP’s DNS returns a bad voice server address.
Adjust QoS settings: In Discord, go to User Settings > Voice & Video and enable “Enable Quality of Service High Packet Priority.” This tells your router to prioritize voice traffic, but it can backfire on some routers. Try toggling it.
Change your network adapter’s MTU: If you’re on a wired connection, lowering the MTU from 1500 to 1492 (or 1400) can help if you’re on a PPPoE connection. This is a router setting, not a Discord one.
Use the browser client: As a temporary workaround, you can use Discord in your web browser (discord.com/app). If it works there, the issue is likely with your desktop client’s local configuration.

Why Does It Happen on Mobile?

The RTC Connecting error also occurs on the Discord mobile app, but the causes are slightly different. On Android and iOS, the most common triggers are:

Poor Wi-Fi signal: Voice chat needs a stable connection; a weak Wi-Fi signal can cause constant reconnecting.
Battery saver mode: Some phones aggressively kill background network activity, which disrupts the voice connection. Disable battery optimization for Discord.
Outdated app: An old version of the app might have bugs that were fixed in a later update. Always update to the latest version.

For mobile, the fix is usually: toggle airplane mode on and off, restart the app, or switch between Wi-Fi and cellular data to see which one works.

How to Prevent It in the Future

While you can’t completely eliminate the chance of RTC Connecting, you can reduce how often it happens:

Keep Discord and your operating system updated.
Use a wired Ethernet connection instead of Wi-Fi when possible.
If you use a VPN, choose a server that’s geographically close to you, or exclude Discord from the VPN tunnel.
Regularly restart your router (once a month is a good habit) to clear its memory.
Check your server’s region setting and make sure it’s set to a location that’s close to most members.

Frequently Asked Questions

Why does Discord say RTC Connecting but I can still hear people?

Sometimes the voice connection partially establishes, and you can hear audio, but your own mic doesn’t work. This usually means the outbound UDP path is blocked. Try changing your voice region or disabling your firewall temporarily to test.

Does RTC Connecting mean I’m banned?

No. A ban would prevent you from accessing the server at all, not just voice. RTC Connecting is purely a network connectivity issue between your device and Discord’s voice servers.

Can I fix RTC Connecting by restarting Discord?

Sometimes, yes. A quick restart clears temporary glitches and re-establishes the connection. If it doesn’t work after a restart, move on to the other fixes.

Why does it only happen on one server?

If the issue is server-specific, the server’s region might be set to a location with poor connectivity for you. Ask the server admin to change the region, or try joining a different voice channel on that server.

Is there a way to force Discord to use a specific voice server?

Not directly. Discord chooses the best server based on your region and network. Changing your server region is the closest you can get to forcing a different server.

Does using a mobile hotspot help?

If your home network is the problem, yes. A mobile hotspot uses a different network path and can bypass ISP-level issues. If it works, you’ll know the problem is with your home network.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →