Discord can load servers, messages, and channel lists, then still freeze on ICE Checking. That screen appears while the app is trying to open a working path for real-time voice traffic. Discord places ICE Checking in the same family as No Route, RTC Connecting, and Connecting, and says these errors often mean something on the local side is interfering with the connection, such as a firewall or a VPN.[✅Source-1]
Discord reports 90M+ daily active users and says over 200 million friends and communities use the platform every month. At that scale, a small mismatch between the app, the browser, the router, or the security layer shows up often enough to deserve a fix path that is technical, short, and easy to follow.[✅Source-2]
Start With Two Fast Checks
- Open Discord Status and rule out a live service issue before changing local settings.
- Join the same voice channel on another network (a phone hotspot is enough). If voice works there, the Discord account is usually fine and your home, school, office, or public network is where to look next.
That split test saves time. A lot of it.[✅Source-3]
On This Page
What ICE Checking Means
ICE stands for Interactive Connectivity Establishment. In plain language, it is the stage where a real-time call gathers possible network routes, tests them, and tries to settle on one route that can actually carry audio. If that route test does not finish, Discord remains on ICE Checking instead of entering the voice channel cleanly.[✅Source-4]
Two terms matter here: STUN and TURN. STUN helps a device discover its public-facing address and whether the router allows a direct path. TURN is the fallback relay path when a direct path does not work. So when Discord stalls on ICE Checking, the block is often not your microphone at all. It is the route negotiation between your device, your network edge, and the voice path.[✅Source-5]
The technical state behind that screen is literally checking. MDN describes it as the period where the ICE agent is testing candidates and has not yet moved to a connected or completed state. Until that happens, live audio does not begin. Simple as that.[✅Source-6]
What This Tells You Right Away
- The call has not finished route setup yet.
- The problem is often network-facing, not microphone-facing.
- Changing voice effects first is usually wasted effort.
What the Pattern Usually Points to
Read the symptom before changing settings. It narrows the fault much faster than random tweaking.
| What You See | What It Usually Points to | What to Do Next |
|---|---|---|
| Text chat works, voice stalls on ICE Checking | The real-time route setup is blocked or not completing | Go straight to VPN, firewall, router, and alternate-network tests |
| Works on mobile data, fails on Wi-Fi | Your local network or router policy is the bottleneck | Restart the router, renew IP/DNS, test a wired connection if possible |
| Discord web fails, desktop app works | Browser permission, browser data, or extension issue | Review mic permission, try another browser, remove stale site blocks |
| Desktop app fails, web works | Local app cache, update issue, or broken install state | Fully quit Discord, clear cache, update, then reinstall if needed |
| Many users report voice trouble at the same time | Service-side incident | Wait on local changes and monitor Discord Status |
If you want the wider map of related voice connection problems, this Discord error page helps place ICE Checking next to similar connection states without mixing it up with unrelated audio settings.
Fixes That Usually Work First
Work through these in order. Each one is short. Each one also tells you something useful about the fault.
- Check Discord Status first. If voice traffic is already under incident, leave your setup alone for the moment.
- Turn off any VPN or proxy. Discord explicitly ties voice connection errors to local interference, and VPN routing is a frequent place to simplify first.
- Fully close Discord, then reopen it. On desktop, quit it from the tray/menu and make sure the process is actually gone.
- Restart your modem, router, and device. This clears stale leases, stale routes, and short-lived local network faults.
- Try one voice join on another network. A hotspot test is enough to separate an app issue from a network issue.
- Only after that, split web versus app. If one works and the other fails, you have already narrowed the fix path.
Discord’s own troubleshooting flow starts with the basics for a reason: check the connection, restart the app, and test another network when possible. Boring, yes. Useful, also yes.[✅Source-7]
If Discord Web Is the One Failing
When the browser version gets stuck on ICE Checking, look at permissions before anything else. Discord’s browser troubleshooting points directly to microphone and camera permission checks, browser compatibility, and trying another supported browser. If you blocked Discord once and forgot about it, the browser may keep reusing that bad permission state.[✅Source-8]
- Open the site permission panel for Discord and confirm Microphone = Allow.
- Test the same channel in another supported browser.
- Temporarily disable browser extensions that filter traffic, privacy scripts, or site permissions.
- If Chrome is the browser in use, remove any old blocked mic exception and allow access again.
Discord has a dedicated Chrome permission article because this block is common enough to deserve its own fix path. Rarely is the browser error random; more often, it is a permission or site-state issue that survived from an older session.[✅Source-9]
If the Desktop App Is the One Failing
If the browser joins voice but the desktop app stalls, move your attention to the local app state. Fully quit Discord, reopen it, clear cache if needed, and make sure the build is current. Discord also says its desktop clients are the preferred way to use the service, which makes the web-versus-app split a very useful diagnostic test.[✅Source-10]
- Quit Discord completely.
- Reopen and retry one voice channel only.
- Clear cache if the app was behaving oddly after an update.
- Reinstall if the app keeps failing while the browser stays fine.
Network and Router Checks That Matter
STUN exists to discover your public address, port, and connectivity state behind a NAT device. That is why home routers, strict firewall rules, security suites, managed Wi-Fi, and some VPN routes matter so much here. If they interfere with candidate discovery or with the path test itself, ICE Checking can sit there until it times out.[✅Source-11]
- Disable VPN or proxy first. It is the fastest route simplifier.
- Restart the router. Do not just restart Discord and stop there.
- Test wired instead of Wi-Fi if the device allows it.
- Review firewall or security software rules. Discord and the browser/app should not be filtered by a restrictive outbound rule set.
- Try another network. If the problem disappears instantly, stop chasing microphone settings.
TURN is the relay fallback when a direct path will not work. If direct routing is messy on your network, the session may need that relay path to become the winner. When even the fallback cannot be reached cleanly, the call does not settle. That is the part many short fix pages skip over.[✅Source-12]
What Usually Does Not Move This Error
An ICE candidate is about the protocols and routing needed to establish the connection. So when the app is still stuck at that stage, changing input sensitivity, echo cancellation, noise suppression, or mic volume usually misses the actual fault. Helpful later, maybe. First move, no.[✅Source-13]
- Do not start with microphone gain.
- Do not start with voice activity threshold.
- Do not start with camera settings.
- Do not spend ten minutes inside cosmetic audio options before you test another network.
Windows and Mac Network Refresh Steps
If the fast checks failed and the hotspot test points to your local network, a network refresh is a reasonable next move. Microsoft’s Windows troubleshooting steps include a small sequence that resets Winsock, resets IP state, renews the address, and flushes DNS.[✅Source-14]
netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns
On Mac, Apple documents the direct path to Renew DHCP Lease: System Settings → Network → select the network service → Details → TCP/IP → Renew DHCP Lease. If your local address or lease state is stale, this can clear it without changing unrelated Discord settings.[✅Source-15]
When Reinstalling Helps
Reinstalling helps when the desktop app itself is the weak point: bad update remnants, broken local folders, or a client that behaves differently from the browser on the same network. Discord’s Windows installer article explicitly tells users to terminate Discord processes and remove the local Discord folders before reinstalling when installer state is broken.[✅Source-16]
- Reinstall is worth it when Discord web works but the desktop client keeps hanging.
- Reinstall is not the first move when Discord fails on one network and works instantly on another.
- Reinstall is usually not enough when the fault is clearly in the router, VPN, firewall, or managed network path.
Can a Voice Region Override Help?
Sometimes, yes. Discord still allows a channel-level Region Override, and server admins can set it manually in voice channel settings. It is not the first fix for raw ICE Checking, though. Use it after you already know the problem is region or route related, not before.[✅Source-17]
FAQ
What does ICE Checking mean in Discord?
It means Discord is still trying to establish a working route for live voice traffic. The app has not yet completed the path test needed to move from route negotiation into a connected voice session.
Is ICE Checking usually a Discord server problem or my network?
It can be either, but many cases are local. Check Discord Status first. If the same account works on another network, your router, VPN, firewall, or managed Wi-Fi is the stronger suspect.
Can a VPN cause Discord to stay on ICE Checking?
Yes. Discord’s own voice connection error article points to local interference such as a firewall or VPN. Turning the VPN off for one test is one of the fastest ways to simplify the route.
Why does Discord web fail while the desktop app works?
That pattern usually points to browser permissions, blocked site data, or an extension issue. Review microphone permission first, then test another supported browser.
Will reinstalling Discord fix ICE Checking?
Sometimes. It helps when the desktop client is damaged or stuck in a bad local state. It does not usually fix a network path block that only appears on one Wi-Fi or router.
Is ICE Checking the same as No Route or RTC Connecting?
No. They are related voice connection states, but they describe slightly different failure points. Discord groups them together because they often come from the same family of connection-path problems.[✅Source-18]