Why Discord Voice Channel RTC Endpoint Cannot Be Reached on VPN

When you use a VPN and try to join a Discord voice channel, you may see the error “RTC endpoint cannot be reached.” This happens because the VPN interferes with Discord’s real-time communication protocol. RTC stands for Real-Time Communication, and it relies on direct peer-to-peer connections. This article explains why the VPN blocks these connections and how to fix it.

Discord uses WebRTC technology to establish voice connections. The app tries to find a direct route between you and other users. A VPN reroutes your traffic through a remote server, which breaks this direct path. The result is a failed connection with the RTC endpoint error.

You will learn the exact cause of this error and three methods to resolve it. Each method works with most VPN services. No technical knowledge is required beyond following the steps.

Why Discord RTC Endpoint Cannot Be Reached on VPN

The error “RTC endpoint cannot be reached” occurs because Discord’s voice system cannot establish a direct peer-to-peer connection when your traffic is routed through a VPN server. Here is the technical breakdown.

Discord uses WebRTC for voice and video. WebRTC requires UDP ports 50000 to 65535 to be open for peer connections. When you use a VPN, your device’s public IP address is replaced with the VPN server’s IP. The other users in the voice channel see the VPN server’s IP, not your real IP. Discord’s connection logic then tries to reach you at that VPN IP, but the VPN server may not forward the UDP traffic correctly.

Many VPNs use NAT or firewalls that block incoming UDP connections. Some VPN protocols, like OpenVPN over TCP, do not support the high-speed UDP packets that Discord requires. Additionally, the VPN kill switch feature can block Discord’s traffic entirely if the VPN connection drops and reconnects.

How Discord Handles Voice Connections

Discord uses a central server to coordinate voice channels. Once you join, the server provides a list of IP addresses for all participants. Your client then tries to connect directly to each participant using UDP. If that fails, it falls back to TCP through Discord’s relay servers. The VPN can block both UDP and TCP attempts.

Why the Error Message Appears

The error message appears when your client cannot reach any of the endpoints for the voice channel. The client sends a request to the Discord server, but the server cannot verify that your IP is reachable. This is different from a general internet outage because other Discord features like text chat still work.

Steps to Fix Discord RTC Endpoint Error on VPN

Follow these methods in order. Each method increases the chance of a successful connection.

Method 1: Use Split Tunneling in Your VPN

Split tunneling lets Discord bypass the VPN while other apps stay protected. This is the most reliable fix. The steps vary by VPN provider, but the general process is the same.

1. Open your VPN app settings
   Look for a section called “Split Tunneling,” “Bypass VPN for Apps,” or “App Exclusion.”
2. Add Discord to the exclusion list
   Select Discord from the list of installed apps. If your VPN does not show apps, enter the Discord executable path: C:\Users\YourUsername\AppData\Local\Discord\app-1.0.9003\Discord.exe. The version number may differ.
3. Save the settings and restart Discord
   Close Discord completely from the system tray. Right-click the Discord icon in the notification area and select “Quit Discord.” Then reopen Discord.
4. Test the voice channel
   Join a voice channel. If the error is gone, you are done. If not, proceed to Method 2.

Method 2: Change VPN Protocol to UDP

Some VPNs default to TCP, which breaks Discord voice. Switching to UDP fixes this.

1. Open your VPN app settings
   Find the protocol selection option. It is usually under “Connection” or “Advanced.”
2. Select a UDP-based protocol
   Choose OpenVPN UDP, WireGuard, or IKEv2. Avoid OpenVPN TCP or SSTP.
3. Reconnect to the VPN
   Disconnect and reconnect to apply the new protocol.
4. Test Discord voice
   Join a voice channel. If the error persists, try Method 3.

Method 3: Disable VPN Kill Switch

The kill switch blocks all internet traffic if the VPN drops. This can prevent Discord from reconnecting.

1. Open your VPN app settings
   Find the kill switch or network lock option.
2. Turn off the kill switch
   Set it to disabled. Some VPNs call this “Internet Kill Switch” or “Network Lock.”
3. Reconnect the VPN
   Disconnect and reconnect.
4. Test Discord voice
   Join a voice channel. If the error persists, the VPN may not support Discord voice at all.

If Discord Still Has Issues After the Main Fix

Discord Voice Drops Intermittently on VPN

If voice works but drops after a few minutes, the VPN may be changing IP addresses. Some VPNs rotate IPs for privacy. This breaks the persistent connection. To fix this, select a static IP server in your VPN settings. Many VPNs offer dedicated IP addresses for an extra fee.

Discord Voice Has High Latency on VPN

Even if the RTC endpoint error is gone, you may experience lag. This happens because the VPN adds extra travel time for packets. To reduce latency, connect to a VPN server that is geographically close to your Discord voice region. You can check the voice region in the channel settings. Also, close bandwidth-heavy apps like streaming services while using Discord voice.

Discord Cannot Connect to Voice at All Without VPN

If the error occurs both with and without VPN, the issue is not the VPN. Check your firewall or antivirus settings. Windows Defender Firewall may block Discord. Go to Windows Security > Firewall & network protection > Allow an app through firewall. Ensure Discord is allowed for both private and public networks.

Discord Voice Connection Methods: Direct vs Relay

Item	Direct Connection (UDP)	Relay Connection (TCP)
How it works	Peer-to-peer via UDP ports 50000-65535	Through Discord relay servers on port 443
Latency	Lowest latency	Higher latency due to extra hop
VPN compatibility	Breaks easily with VPN	Works with most VPNs
Stability	Depends on NAT and firewall	More stable across networks
When used	Default when direct path is available	Fallback when direct fails

Discord automatically switches to relay if direct connection fails. However, the relay may still fail if the VPN blocks port 443 or if the VPN’s DNS resolution is slow. If you see the RTC endpoint error, Discord cannot establish either connection type.

The best solution is to use split tunneling so that Discord can use direct UDP connections. This gives you the lowest latency and most stable voice quality. If your VPN does not support split tunneling, consider switching to a VPN that does, such as NordVPN, ExpressVPN, or ProtonVPN.