If Discord is stuck on “RTC Connecting” during a call, your voice channel won’t connect and you’ll hear silence. This guide walks through the most reliable fixes, from quick network resets to deeper system tweaks, so you can get back to talking.
What You’ll Need
- Access to Discord settings (desktop app or browser)
- Ability to restart your router/modem (if network issues are suspected)
- Admin rights on your computer (for some firewall/network steps)
Step-by-Step
- Switch voice regions manually. In a voice channel, click the channel name at the top, then select “Voice Settings” (gear icon). Under “Region Override,” pick a region close to you — for example, if you’re in the US, choose “US East” or “US Central.” Auto is often the culprit; forcing a nearby server can bypass the stuck connection.
- Toggle the voice channel. Leave the voice channel and rejoin. If that doesn’t work, switch to a different voice channel in the same server, then switch back. This forces a fresh connection attempt.
- Restart Discord completely. Right-click the Discord icon in the system tray (bottom-right on Windows, top-right on Mac) and select “Quit Discord.” Then reopen it. On mobile, swipe the app away from recent apps and relaunch.
- Restart your router and modem. Unplug both for 30 seconds, plug the modem back in, wait for it to fully boot, then plug in the router. Once the internet is back, relaunch Discord. This clears any stale NAT or UDP mappings.
- Disable VPN or proxy. If you use a VPN or a proxy (like a school/work filter), turn it off temporarily and try connecting again. Discord’s voice uses UDP, which many VPNs handle poorly. If you must use a VPN, switch to a different server location or enable split tunneling for Discord.
- Change Discord’s voice settings. Go to User Settings (gear icon) → Voice & Video. Set “Voice Activity Processing” to “Standard” (if it’s on “Krisp” or “Experimental”). Also, turn off “Echo Cancellation” and “Noise Suppression” temporarily — these can occasionally cause connection loops. Then rejoin the voice channel.
- Flush DNS and reset network stack (Windows). Press Win+R, type
cmd, and press Enter. In the Command Prompt, run these commands one by one, pressing Enter after each:
ipconfig /flushdns
netsh winsock reset
netsh int ip reset
Restart your PC afterward. This is a common fix for stuck RTC connections caused by corrupted network cache. - Allow Discord through your firewall. On Windows, search for “Allow an app through Windows Firewall” in the Start menu. Click “Change settings,” then “Allow another app,” browse to Discord’s executable (usually in
AppData\Local\Discord\app-{version}\Discord.exe), and add it. Ensure both Private and Public boxes are checked. On macOS, go to System Settings → Network → Firewall, and make sure Discord is allowed. - Update your network drivers. Outdated or buggy network drivers can cause UDP issues. On Windows, open Device Manager, expand “Network adapters,” right-click your Wi-Fi or Ethernet adapter, and select “Update driver.” Choose “Search automatically.” If that finds nothing, check your manufacturer’s website for the latest driver.
- Use Discord’s browser client as a test. If you’re on the desktop app, try opening Discord in a browser (like Chrome) and joining the same voice channel. If it works there, the problem is likely with the app’s cache. Clear Discord’s cache by pressing Win+R, typing
%appdata%\discord, deleting the “Cache” folder, and restarting Discord.
Common Mistakes
- Only restarting Discord, not quitting it. Closing the window doesn’t kill the process; you must right-click the tray icon and choose “Quit” or use Task Manager.
- Ignoring the region override. Many users leave it on “Auto,” which can route you to a congested server. Manually setting a region often fixes it instantly.
- Forgetting to restart after firewall/DNS changes. Several fixes require a full system restart to take effect; skipping it makes you think the fix failed.
- Assuming it’s a Discord server issue. While Discord occasionally has outages, “RTC Connecting” is more often a local network or app issue. Check Discord’s status page before deep troubleshooting.
Tips
- Use an Ethernet cable. If you’re on Wi-Fi, a wired connection reduces packet loss and jitter, which are common triggers for RTC connection failures.
- Set a static DNS. Using Google’s DNS (8.8.8.8 and 8.8.4.4) or Cloudflare’s (1.1.1.1) can improve connection stability. Set it in your router’s settings or in Windows network adapter properties.
- Disable hardware acceleration. In Discord, go to User Settings → Advanced, and turn off “Hardware Acceleration.” This reduces GPU/network conflicts on some systems.
- Keep Discord updated. Old versions have known RTC bugs. Discord auto-updates, but you can force a check by restarting the app.
- Test with a different account. If you have a second Discord account, try joining the same server with it. If that works, the issue is tied to your account’s voice settings or region override.
Troubleshooting
If you’ve followed all steps and still see “RTC Connecting,” try these deeper checks:
- Check if your ISP is blocking UDP. Some networks (especially public Wi-Fi or mobile hotspots) block the UDP ports Discord uses (50000-65535). Try using a mobile hotspot from your phone — if Discord works there, your ISP or router is the problem.
- Reset Discord’s voice settings to default. In User Settings → Voice & Video, scroll to the bottom and click “Reset Voice Settings.” This clears any corrupted audio device or bitrate settings.
- Reinstall Discord. Uninstall Discord completely (including the AppData folder on Windows), then download the latest version from the official website. This fixes corrupted installation files.
- Try a different server. Create a temporary server and join its voice channel. If that works, the original server’s voice region or permissions may be misconfigured.
- Check your router’s QoS settings. Some routers have Quality of Service features that can misclassify Discord traffic. Disable QoS or add Discord as a high-priority application.
Frequently Asked Questions
Why does Discord say “RTC Connecting” but never connect?
This usually means Discord’s voice server can’t establish a UDP connection. Common causes include network congestion, VPN interference, or a misconfigured firewall blocking the required ports.
Does changing my Discord region actually help?
Yes. Auto region selection sometimes picks a server that’s far away or overloaded. Manually selecting a nearby region reduces latency and often fixes connection timeouts.
Will clearing Discord’s cache delete my messages?
No. The cache only stores temporary files like images and voice data. Your messages, servers, and settings are stored on Discord’s servers and remain untouched.
Can a VPN cause RTC Connecting?
Absolutely. VPNs often route UDP traffic poorly or block it entirely. Disabling the VPN or using a different protocol (like WireGuard instead of OpenVPN) usually resolves the issue.
Why does it work on my phone but not my PC?
This points to a PC-specific issue, such as a firewall rule, outdated network driver, or corrupted Discord installation. Follow the Windows-specific steps (DNS flush, firewall, driver update) to isolate the cause.
Is Discord’s “RTC Connecting” a sign of a ban?
No. It’s a technical connection error, unrelated to account bans or restrictions. Bans typically show a different message when trying to join a server.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Unfortunately App Has Stopped: Step-by-Step
- Restart a Frozen Samsung Galaxy A12
- HomePod Stereo Pair with AirPlay 2 from iPhone
- Fix 0x8e5e0247 Error on Windows
- Pixel & Pixel XL No Sound: Solved?
- How to Edit Playlists on iPhone