How to Fix Discord Error Code 1000 (Voice Connection / RTC Connecting Error)

Quick Fix

Fastest fix: Fully quit Discord (not just close the window) and reopen it.

1. On Windows: right-click the Discord icon in the system tray near the clock and choose ‘Quit Discord’, then wait a few seconds before reopening it.
2. Leave the voice channel completely and rejoin it after restarting.
3. If it still hangs on ‘RTC Connecting’ or shows Error Code 1000, temporarily disable your VPN, since Discord does not support VPN connections without UDP and dynamic VPN IPs commonly trigger this error.

Step-by-Step Guide

What Discord Error Code 1000 Means

Error Code 1000 on Discord is most commonly associated with a failed real-time voice/video connection – it shows up alongside messages like ‘RTC Connecting’ or ‘Awaiting Endpoint’ when your app cannot finish connecting to Discord’s voice servers. According to Discord’s own support documentation, these voice connection errors generally fall into two categories: something on your end (like a firewall or VPN) or something on Discord’s end (a server-side issue). In the vast majority of cases the cause is local – your network, firewall, antivirus, or VPN interfering with the WebRTC/UDP traffic Discord needs for voice and video.

Step 1: Fully Restart Discord

1. Leave the voice channel or call you’re in.
2. On Windows, right-click the Discord icon in the system tray (bottom-right near the clock) and select ‘Quit Discord’ – simply closing the window often leaves it running in the background.
3. On Mac, use Cmd+Q or Activity Monitor to fully quit the process.
4. Wait about 10-15 seconds, then relaunch Discord and rejoin the voice channel.

This forces Discord to rebuild its connection from scratch and resolves a large share of temporary RTC/1000 errors.

Step 2: Restart Your Router and Computer

1. Power off your modem/router completely for about 30 seconds.
2. Power it back on and wait for a full, stable connection.
3. Restart your computer or phone as well, since this clears stuck network services and background processes.

Step 3: Check for a VPN, Proxy, or Firewall Interference

1. If you use a VPN or proxy, disable it and try Discord voice again. Discord’s support team notes you should check your VPN, since Discord only works on VPNs that have UDP, and a dynamic/changing VPN IP address is a frequent trigger for this exact error.
2. Check your firewall or antivirus software and make sure Discord.exe is allowlisted or temporarily disabled to test, since you should check your Firewall/Antivirus and make sure that Discord is allowlisted or temporarily disabled.
3. If you’re on a work, school, or public network, ask your network admin – Discord voice traffic (UDP ports in the 50000-65535 range) is sometimes blocked outright on managed networks.

Step 4: Change the Server’s Voice Region (If You’re an Admin)

1. Open Server Settings on the affected server.
2. Go to Overview and find the Region Override / Server Voice Region section.
3. Switch to a different region (or Auto) – Discord support specifically recommends this: if you’re the admin, temporarily switch to try a different voice region in Voice Channel Settings, Overview, Region Override.
4. Rejoin the voice channel and see if the error clears.

Step 5: Adjust In-App Voice Settings

1. Open Discord Settings (gear icon, bottom-left) and go to Voice & Video.
2. Scroll to Quality of Service (QoS) High Packet Priority and toggle it off, since some home routers mishandle this setting and it can cause connections to hang.
3. In the same menu, try switching the Audio Subsystem to ‘Legacy’ if you’re on Standard or Experimental.
4. Restart Discord after each change and test again before moving to the next fix – change one setting at a time so you know what actually solved it.

Step 6: Change Your DNS and Flush the Cache

1. On Windows, open Network Connections (Win+R, type ncpa.cpl), right-click your active connection, choose Properties, select Internet Protocol Version 4 (TCP/IPv4), and set custom DNS servers (such as a well-known public DNS provider) instead of your ISP’s default.
2. Flush your DNS cache afterward from Command Prompt.
3. Close Discord fully and delete its Cache, Code Cache, and GPUCache folders from the Discord data directory (found under your user AppData/Roaming/discord folder on Windows) so the app rebuilds them fresh.

Step 7: Update Network Drivers and Try the Browser Version

1. Open Device Manager (Win+R, Devmgmt.msc), expand Network Adapters, right-click your adapter, and choose Update Driver.
2. If the desktop app still fails, try Discord in a web browser to determine whether the issue is specific to the desktop client or your network as a whole.

When to Escalate to Official Support

If none of the above works, or if other people in the same server are simultaneously stuck on the same error, the problem is likely on Discord’s servers rather than your setup. Discord’s own guidance is direct about this: if you’re sitting and staring at an awaiting endpoint error, you’ll need to reach out to Discord’s support team either via Twitter or their Support Center. Before contacting them, join the affected voice channel, open Developer Tools (Ctrl+Shift+I on Windows, Option+Cmd+I on Mac), check the Console tab, and screenshot any visible error messages – this speeds up their diagnosis considerably. Also check Discord’s status page or community reports to rule out a wider outage before assuming the problem is unique to your account or device.