Why Discord RTC Connecting Gets Stuck at 100%
When Discord displays “RTC Connecting” and hangs at 100%, it means the application has successfully completed the initial handshake sequence but cannot finalize the Real-Time Communication channel. This typically occurs when UDP hole-punching fails, when firewall rules block the outgoing RTP packets, or when Discord’s media servers are experiencing partial outages.
Technical Breakdown
Discord uses a hybrid TURN/STUN system for voice communication. The 100% stuck state indicates the STUN binding request succeeded (device is reachable) but the subsequent DTLS handshake with Discord’s edge relay servers failed. This failure commonly originates from VPN interference, port 50002–60000 UDP being blocked, or outdated Discord routing tables cached on your local machine.
Solutions
1. Toggle Voice Settings
Open Discord Settings → Voice & Video. Under Input Mode, switch from Voice Activity to Push to Talk (or vice versa). This forces Discord to reinitialize the voice engine and renegotiate the RTC session. If that fails, toggle Echo Cancellation and Noise Suppression off and on again to reset the audio pipeline.
2. Disable VPN or Split Tunnel VPN Traffic
VPNs with aggressive routing policies often interfere with Discord’s UDP-based voice paths. Temporarily disconnect your VPN and attempt to connect to a voice channel. If the problem resolves, configure your VPN to exclude Discord’s media servers by adding the IP range 162.249.0.0/16 to your VPN’s split tunnel exclude list.
3. Add Discord to Firewall Allow-List
Windows Defender Firewall can block Discord’s outbound UDP connections silently. Open Control Panel → Windows Defender Firewall → Allow an app. Ensure Discord is listed with both Private and Public access enabled. For custom firewall software (Norton, McAfee, GlassWire), manually add an inbound and outbound rule for UDP ports 50000–60000.
4. Reset Discord’s Network Cache
Close Discord completely (right-click taskbar icon → Quit). Press Win+R and type %AppData%discord. Delete the Cache folder and all files in the logs folder. Restart Discord. This forces Discord to perform a fresh CDN lookup for voice server endpoints rather than relying on potentially stale cached routing data.
5. Run Discord as Administrator
Right-click the Discord shortcut → Run as administrator. Elevated permissions allow Discord to bind to privileged ports and establish raw socket connections required for the DTLS handshake. If the 100% loop resolves after this, adjust the shortcut properties permanently.
6. Check Discord Server Status
Visit Discord Status. During partial outages, voice server regions may be degraded while text channels remain functional. Subscribe to status updates for your region to determine if the issue is infrastructure-side rather than local.
Advanced: Port Forwarding for Strict NAT
If you have a strict or symmetric NAT type, standard UDP hole-punching fails. Access your router and forward UDP ports 50000–60000 to your PC’s local IP address. You can check your NAT type in Discord under Settings → Voice & Video → Scroll to NAT Type — “Moderate” or “Open” are sufficient; “Strict” or “Symmetric” indicates a NAT configuration problem.