RTC Connecting Discord: Fix Voice Chat Stuck Fast (2026)
Fix Discord stuck on RTC Connecting or No Route by isolating the network, app, firewall, and UDP path—then use only the solution your test proves.
Quick answer
Fully quit Discord, install any update, check Discord Status, then join the same voice channel on a phone hotspot. If the hotspot works but your Wi-Fi does not, the original network or ISP route is the problem: turn off any existing VPN first; if it still fails, connect NordVPN with NordLynx, reopen Discord, and rejoin. If both networks fail, reset Voice & Video settings and allow Discord through the firewall before buying anything.
Fix Discord stuck on RTC Connecting in 60 seconds
Fully quit Discord
End every Discord process, install any pending update, and reopen it.
Check Discord Status
If Voice is degraded, wait. Local network changes will not repair a service outage.
Try a phone hotspot
Join the same channel on the same device while changing only the network.
Use the result
Hotspot works: fix the original route. Both fail: fix the app or device.
Where does Discord RTC Connecting happen?
Your result
The original network path is the likely cause
Discord voice fails on one Wi-Fi connection but works on a phone hotspot or another network.
Likely cause
The router, ISP route, network policy, or an existing VPN is disrupting the UDP path.
Do this next
Turn off any existing VPN first. If the call still fails only on this network, connect a paid VPN with UDP or WireGuard, fully reopen Discord, and rejoin.
What RTC Connecting means in Discord
RTC means real-time communication. Discord uses WebRTC connection techniques to find a usable route for voice; ICE tests candidates, STUN helps discover the public-facing network address, and TURN can relay traffic when a direct candidate is not usable.
Your device
Discord captures audio and begins a real-time connection attempt.
ICE checks
WebRTC tests possible paths with help from STUN and, when needed, a TURN relay.
UDP route
A firewall, restrictive network, or bad ISP route can stop the preferred voice path.
Discord voice server
Once a usable route is selected, the voice session can start.
Why UDP matters
Best VPNs when the hotspot test proves a Discord route problem
NordVPN offers NordLynx, Proton VPN is the open-source alternative, and PureVPN has a 31-day initial refund window. Free VPNs often limit the protocol, server choice, or capacity needed to compare Discord voice routes.
NordVPN
- Sixth independent no-logs assurance completed by Deloitte in 2025
- NordLynx is built around WireGuard for a fast UDP-capable route
- One account protects up to 10 devices at the same time
- 30-day refund window for eligible initial purchases
Proton VPN
- Apps are open source and independently audited
- WireGuard UDP is available across major desktop and mobile apps
- Paid plans cover 140+ countries and up to 10 devices
- 30-day refund window for eligible paid purchases
PureVPN
- KPMG can inspect the no-log systems without advance notice
- WireGuard and explicit UDP protocol choices are available
- 6,000+ servers in 65+ countries with up to 10 logins
- 31-day refund window for eligible initial purchases
Audit, protocol, device, server, and refund facts checked July 31, 2026. Refund eligibility depends on purchase channel and current terms. VPN features, network access, and refund rules can change, so verify the linked official terms before purchase.
Discord RTC Connecting fix: the complete sequence
- 1
Update Discord and restart the device
Install the current client before deeper changes. Discord began rejecting voice calls from clients that do not support its required DAVE voice encryption on March 3, 2026.
- 2
Check status, then run the hotspot test
Check Discord’s Voice status. If it is healthy, join the same channel on a phone hotspot. This single comparison separates a route problem from a device problem.
- 3
Turn off an existing VPN or proxy
Discord officially notes that a VPN must support UDP. Disconnect the current tunnel first. If voice starts, keep it off or switch that app to UDP or WireGuard.
- 4
Restart the router and remove network conflicts
Power down the modem and router, wait briefly, and start them again. Remove duplicate proxies, captive-portal sessions, or security filters before retesting.
- 5
Reset Voice & Video settings
In User Settings → Voice & Video, choose Reset Voice Settings. If the connection still stalls, disable Quality of Service High Packet Priority and test again.
- 6
Allow Discord through the firewall
Allow the current Discord executable on the active network profile. Do not turn off the entire firewall; that creates risk without proving which rule is wrong.
- 7
Refresh DNS and the Windows network stack
If websites work but voice routing remains stale, flush DNS and reset Winsock from an administrator terminal, then restart Windows.
Windows Terminal (Admin)ipconfig /flushdns netsh winsock reset - 8
Ask an admin or server moderator
Work and school networks may intentionally block real-time UDP traffic. A server moderator can also try a Voice Region Override while Discord investigates a regional route.
Discord RTC Connecting on browser, phone, or desktop
| Platform | Check first | Then test |
|---|---|---|
| Windows desktop | Update Discord, allow the current executable through Firewall, reset Voice & Video. | Flush DNS and reset Winsock, then restart. |
| macOS desktop | Update Discord, disable the current VPN or proxy, confirm microphone permission. | Create a fresh network location or test the browser client. |
| Discord in browser | Allow microphone access; try a private window with extensions disabled. | Clear discord.com site data or use another current browser. |
| iPhone / Android | Force-close Discord, allow microphone and mobile data, turn off the phone VPN. | Switch between Wi-Fi and cellular data. |
| Work / school network | Ask whether outbound UDP or WebRTC is restricted. | Use an approved alternative network or ask the administrator. |
RTC Connecting, ICE Checking, No Route, and voice server errors
Discord groups RTC Connecting, ICE Checking, No Route, and Connecting as related user-side voice connection errors. Waiting for Voice Server is more likely to reflect a Discord-side service issue.
| Message | What it usually means | Best first move |
|---|---|---|
| RTC Connecting | Discord has not completed a usable real-time voice route. | Run the hotspot comparison. |
| ICE Checking | WebRTC is still gathering and testing connection candidates. | Wait briefly; then check UDP, firewall, and VPN. |
| No Route | The connection checks found no viable route. | Change networks, then inspect policy, NAT, or routing. |
| Waiting for Voice Server | Discord allocated or is waiting on voice infrastructure. | Check Discord Status before local changes. |