How to Fix a Discord Awaiting Endpoint Error
You click into a voice channel and your friends are already talking. Your status sits on a waiting message and never connects. What’s more annoying than hearing nothing while everyone else is mid-game?
The Discord Awaiting Endpoint error usually means Discord’s voice servers are struggling, so your first move is a 30-second status check before you touch your own settings. You can follow this guide whether you use the Windows app, the Mac app, or Discord in a browser.
Here’s the short answer. Discord’s Voice Connection Errors support article puts this wait state in the server-side group, which means the trouble is usually on Discord’s end.
Check discordstatus.com first. A clear status page is a good sign, but it can’t rule out a localized or newly developing issue, so work through the fixes below in order if the problem continues.
Quick Decision Tree
Work through these in order before diving into the detailed steps below:
- Check discordstatus.com for open incidents.
- Fully quit and reopen Discord, then restart your router and computer.
- Test a different network, like a phone hotspot, to isolate the problem.
- Turn off your VPN and confirm Discord is allowed through your firewall.
- If several members in one server are affected, an admin with the Manage Channels permission can try a different Region Override.
- Reinstall Discord if nothing above helps.
- Contact Discord Support with console log screenshots if the error persists.
Discord Awaiting Endpoint Error: Quick Reference
| Symptom or Scenario | Recommended Fix |
|---|---|
| Stuck on Awaiting Endpoint or similar wording | Check discordstatus.com for open incidents |
| Status page looks fine, error persists | Fully quit and reopen Discord, then restart your modem, router, and computer |
| Works on a phone hotspot but fails on school or work Wi-Fi | That network is the likely problem, so ask its admin about Discord |
| VPN is turned on | Disconnect it, since Discord voice needs a VPN that supports UDP |
| Several server members hit the same error in one channel | An admin with Manage Channels can change that channel’s Region Override |
| Your screen says RTC Connecting instead | See our RTC Connecting guide, since that’s often a different, local-network issue |
Awaiting Endpoint vs. RTC Connecting: Which One Do You Have?
These two look alike (a voice call that just won’t connect), but Discord files them in different buckets.
- Awaiting Endpoint: Discord’s support article says this points to trouble with one of Discord’s own voice servers. Your device is usually fine.
- RTC Connecting, ICE Checking, No Route, Connecting: These statuses often point to a local network, firewall, or VPN issue on your end, though Discord’s guidance doesn’t treat that as certain in every case.
Some users see the wording “Waiting for Voice Server” instead of “Awaiting Endpoint.” Discord’s support article doesn’t use that exact phrase, so treat it as different wording for a similar voice-connection wait rather than a confirmed official synonym.
If your screen says RTC Connecting, ICE Checking, or No Route, stop here and head to our Discord RTC Connecting error guide, since those statuses usually call for the same local network, firewall, and VPN checks. Those steps are different, and this article won’t repeat them.
Quick Fixes to Try First
Run these in order. Each one takes a minute or two.
- Check Discord’s Status Page: Open discordstatus.com and look for any open incidents.
- Fully Quit Discord: Closing the window isn’t the same as quitting the app, so quit it all the way and reopen it.
- Restart Your Network Gear: Discord’s own guidance says to restart your modem, router, and computer together.
- Run a Speed Test: Use any browser-based speed test to confirm your internet works at all.
- Turn Off Your VPN: Disconnect it and try the voice channel again.
Common Issues and Solutions
Problem: Discord’s Voice Servers Are Having Trouble
Symptoms:
- The voice status sits on Awaiting Endpoint or similar wording
- Text chat works fine, but voice never connects
- Friends in the same region report the same problem
Why it happens: Discord’s support article groups this wait state as a server-side issue. Restarting your router won’t fix a Discord outage.
Fix:
- Open a browser and go to
https://discordstatus.com. - Look at the overall status banner at the top of the page.
- Scroll through the component list and any open incidents for anything related to voice connectivity.
- If Discord reports an incident, wait it out and check back periodically.

Verify: The status page is a useful first check, but it isn’t definitive about every localized or newly developing incident.
If it shows no open incident or shows one as resolved, rejoin the voice channel to see if voice reconnects. If the error persists despite a clear status page, continue with the network and firewall checks below.
Problem: Discord Is Still Running in the Background
Symptoms:
- You closed Discord and reopened it, but the error came right back
- Discord’s icon is still in the Windows system tray or the Mac menu bar
Why it happens: Closing Discord’s window doesn’t always quit the app completely, which can leave a stuck voice session active. Quitting all the way clears it out.
Fix:
- On Windows, right-click the Discord icon in the system tray near the clock and choose Quit Discord.
- On a Mac, click the Discord window and press
Cmd+Q. - In a browser, close the Discord tab, then open
https://discord.com/appin a fresh tab. - Restart your modem, router, and computer. Unplug the modem and router, count to 30, and plug them back in.
For a more detailed walkthrough, see our guide on how to restart Discord.

Verify: Reopen Discord and join the voice channel. If it connects, you’re done.
Problem: Your Internet Connection Is Unstable
Symptoms:
- Web pages load slowly or time out
- Video streams buffer constantly
- Discord voice fails on and off
Why it happens: This error points at Discord, but a flaky home connection makes every voice server look broken. A speed test is a quick way to spot a slow or unstable connection, though it can’t confirm that Discord’s voice path works.
Fix:
- Open any speed test site in your browser and run the test.
- Compare the results to the plan you pay for.
- If speeds are way off, restart your router again or move closer to it. Walls and floors block Wi-Fi signals like nobody’s business.
- For a steadier connection, plug your PC directly into the router with a Cat6 Ethernet cable. If dead zones are a regular problem, a mesh Wi-Fi system is worth a look.
Verify: If the call works after restarting your router or switching networks, compare the conditions to figure out what actually changed.
A normal speed test result by itself doesn’t prove your connection caused the original failure, since a typical speed test doesn’t directly check UDP reachability, firewall behavior, or Discord’s voice service.
Problem: The Error Only Happens on One Network
Symptoms:
- Voice works at home but fails on school or work Wi-Fi
- Voice works on your phone’s hotspot but fails on your regular network
Why it happens: Discord’s support article warns that work and school networks sometimes block Discord’s traffic.
Fix:
- Turn on your phone’s mobile hotspot and connect your computer to it.
- Rejoin the voice channel.
- If voice works on the hotspot, the original network is the likely culprit, whether that’s a firewall policy, DNS, or routing difference. Ask the network admin whether Discord is allowed. (Spoiler: at a lot of schools, it isn’t.)
Verify: Voice connects on the hotspot and fails on the original network. That points strongly at the original network, though it doesn’t prove exactly what on that network is interfering.
Problem: A VPN Is Blocking Voice Traffic
Symptoms:
- Voice fails only when your VPN is on
- Text chat loads normally
Why it happens: Discord’s support article says voice only works through VPNs that support UDP. UDP is a fast way of sending data that live voice and video depend on. Some VPNs block it or don’t support it.
Fix:
- Disconnect your VPN from its app.
- Fully quit and reopen Discord.
- Join the voice channel again.
- If voice works now, either leave the VPN off while you chat or switch to a UDP-capable VPN. Check your VPN app’s protocol settings for a UDP option, too.
Verify: Voice connects with the VPN off and fails with it on.
Problem: Firewall or Antivirus Is Blocking Discord
Symptoms:
- Voice fails on every network you try
- You recently installed or updated security software
Why it happens: Security software can silently block the UDP traffic voice calls need. Discord’s troubleshooting steps call this out directly.
Fix:
- Check that Discord is on your firewall’s allowed-apps list (steps for each OS are below).
- Open your antivirus app and look for an allowlist, exceptions, or trusted-apps section. Add Discord there.
- As a short test only, you can pause the firewall or antivirus, retry the call, and turn protection back on right away.
I’d skip step 3 unless steps 1 and 2 didn’t help. Leaving protection off is a bad trade for one voice call.
Verify: If voice works with Discord allowlisted, leave your protection on and move on.
Problem: Your Discord App Is Outdated or Damaged
Symptoms:
- The error keeps coming back after everything above
- Discord acts glitchy in other ways, too
Why it happens: An old or corrupted install can misbehave in odd ways.
Fix:
- Fully quit Discord and reopen it to rule out a temporary glitch.
- If that doesn’t help, uninstall Discord (Settings > Apps on Windows, or drag it from Applications to the Trash on a Mac).
- Download a fresh copy from
https://discord.com/downloadand install it. - On the web, try a different browser to rule out a browser problem.
Verify: Sign back in and join the voice channel.
Problem: One Server’s Voice Channel Keeps Failing for Several Members
Symptoms:
- Multiple members hit the same error in one voice channel
- Other servers’ voice channels work fine for you
Why it happens: By default, a voice channel’s region is set to Automatic, so Discord picks a server region for you. Switching the override can help if the automatically selected region is having trouble, though Discord’s guidance doesn’t guarantee that’s the cause in every case.
Fix (requires the Manage Channels permission):
- Hover over the voice channel and click the gear icon, or right-click it and choose Edit Channel.
- Stay on the Overview tab.
- Scroll to Region Override.
- Pick a region close to most of your members.
- Click Save Changes, then have everyone leave and rejoin the call.

Discord’s support article describes Region Override as a voice channel setting, so you change it channel by channel. Private calls have their own region option as well.
Verify: Members should connect normally after rejoining. If not, try a second nearby region.
Error Messages Explained
| Message | What It Means | Whose Side | Where to Start |
|---|---|---|---|
| Awaiting Endpoint | Waiting on a Discord voice server | Discord’s | discordstatus.com |
| Waiting for Voice Server | Wording some users see for a similar wait | Likely Discord’s | discordstatus.com |
| RTC Connecting | Often a local network, firewall, or VPN issue | Often yours | Our RTC Connecting guide |
| ICE Checking | Same group as RTC Connecting | Often yours | Our RTC Connecting guide |
| No Route | Same group as RTC Connecting | Often yours | Our RTC Connecting guide |
Platform-Specific Fixes
On Windows
Allow Discord Through Windows Firewall
Exact menu names can vary slightly between Windows versions, but the general steps are similar.
- Open Windows Security from the Start menu.
- Click Firewall & network protection.
- Click Allow an app through firewall.
- Click Change settings, find Discord, and check the box for the network profile you actually use (Private for home or work networks, Public for open or unsecured ones). Check both only if you regularly use Discord on both types of network.
- Click OK.
Don’t disable the firewall entirely as a routine fix. If Discord still fails after allowlisting it correctly, move on to the other fixes below instead of turning off protection.

On macOS
Check the macOS Firewall
- Open System Settings > Network > Firewall.
- If the firewall is on, click Options.
- Find Discord in the list and make sure it’s set to allow incoming connections. Use the + button to add it if it’s missing.
- Click OK.
On macOS 12 Monterey or earlier, open System Preferences > Security & Privacy > Firewall instead.

On the Web
The browser version has fewer moving parts. Close every Discord tab, reopen https://discord.com/app, and try again. If that fails, sign in from a different browser. The status page check and Region Override work the same way here.

Optional Last Resort: Clear the DNS Cache
DNS is your computer’s address book for websites. Flushing it is a general networking fix, not something Discord’s support article lists for this error.
It mainly affects name resolution, not an already-established Discord voice-region connection or UDP path, so it’s unlikely to fix a genuine Discord-side Awaiting Endpoint incident. Try it only after the other fixes above haven’t worked.
On Windows:
- Right-click the Start button and choose Terminal or Windows PowerShell.
- Type this command and press Enter:
ipconfig /flushdns
- Look for the message “Successfully flushed the DNS Resolver Cache.”

On macOS:
This command works on most recent versions of macOS, though the exact syntax can vary slightly across releases.
- Open Terminal from Applications > Utilities.
- Paste this command and press Return:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- Type your Mac password when asked. Nothing shows as you type, which is normal. You won’t see a success message.

Settings to Check
- Region Override: Go to Voice Channel Settings > Overview and check whether it’s set to Automatic or a specific region. Changing it requires the Manage Channels permission.
- Firewall allowed apps: Make sure Discord is allowed on the network profile you use, on both Windows and macOS.
- VPN protocol: Look in your VPN app for a UDP option if you plan to keep it on.
Getting Help
Contact Discord Support when:
- The status page shows no incident, but the error lasts for hours
- Voice fails on several networks with your VPN off and Discord allowlisted
- A fresh reinstall and a Region Override change didn’t help
Discord Support may ask for screenshots of the app’s console logs. To capture these, download the Discord PTB or Canary test version from https://discord.com/download, open it, press Ctrl+Shift+I on Windows or Cmd+Option+I on Mac to open developer tools, click the Console tab, reproduce the error, and screenshot any red error lines.
Don’t share screenshots that show your account token, email, or other account details. Crop or blur that information before sending it to support.
Prevention Tips
- Bookmark the Status Page: Make discordstatus.com your first stop every time voice acts up.
- Pick a UDP-Friendly VPN: If you need a VPN while gaming, choose one that supports UDP.
- Allowlist Discord Once: Add it to your firewall and antivirus now so updates don’t trip it later.
- Use a Wired Connection: A Cat6 Ethernet cable beats Wi-Fi for steady voice calls.
Frequently Asked Questions
Is Awaiting Endpoint my problem or Discord’s problem?
Usually Discord’s. Its support article groups this wait state with server-side errors, so check the status page first.
How is this different from RTC Connecting?
RTC Connecting often points to something on your end, like a firewall, antivirus, or VPN. Awaiting Endpoint points to Discord’s voice servers.
Do I need a VPN or firewall change to fix this?
Usually not. Turn off your VPN as a test, and make sure Discord is allowed through your firewall. Don’t add a VPN to fix this error.
What does changing the voice region actually do?
It sends that channel’s voice traffic to a Discord server region you choose, instead of the one Discord picks automatically.
That can help if the automatically selected region is struggling, though Discord’s guidance doesn’t guarantee that’s the cause every time.
What should I do if nothing fixes it?
Wait a few hours and check the status page again. If it’s still failing, contact Discord Support with your console log screenshots.
Wrapping Up
The Awaiting Endpoint error is usually Discord’s mess to clean up, so the status page saves you the most time. After that, a full quit, a network restart, and a VPN check clear up the rest.
Region Override is the admin’s best tool, though I’d only reach for it when several members hit the same wall.
| Step | Action | Applies To |
|---|---|---|
| 1 | Check discordstatus.com | All platforms |
| 2 | Fully quit and reopen Discord, restart network gear | Windows, macOS, web |
| 3 | Run a speed test and try a hotspot | All platforms |
| 4 | Disconnect your VPN | All platforms |
| 5 | Allowlist Discord in firewall and antivirus | Windows, macOS |
| 6 | Update or reinstall Discord | Windows, macOS |
| 7 | Clear the DNS cache (optional, last resort) | Windows, macOS |
| 8 | Change Region Override (Manage Channels permission required) | Server admins |
One last tip for admins. Once Discord’s status page shows things are healthy again, set Region Override back to Automatic. Otherwise a forced region you forgot about could keep members on a far-off server long after the original problem cleared.
Last updated: November 15, 2026 | Applies to Discord on Windows, macOS, and the web
The post How to Fix a Discord Awaiting Endpoint Error first appeared on Online Tech Tips.