Streaming help · Discord

Discord Stuck on RTC Connecting or No Route

Separate service problems from network restrictions, test a permitted connection and collect useful evidence without disabling protections broadly.

START HERE

Check Discord service status and the exact connection state, then compare a permitted network path. Discord documents that voice requires a UDP-capable VPN and may be blocked by managed networks. Review the specific app allowance with the network owner instead of disabling security controls across the computer.

A changed result helps identify the network or regional path involved.

In this guide
Before you start
  • The exact displayed connection error and approximate time.
  • Permission to use the network and any alternative connection tested.
  • An authorized server administrator if region changes are needed.

Identify the result you need

RTC Connecting, No Route and Waiting for Voice Server do not all imply the same fault. The checked Discord guidance distinguishes common local-path errors from a service-side waiting state. Record the actual wording rather than describing every problem as microphone failure.

If text chat works but voice cannot connect, changing microphone gain is unlikely to address the connection stage. Establish whether the client reaches a voice server before investigating what audio it sends.

Work through the setup

  1. Check status and scope

    Look at Discord's current status and ask whether others in the same call are affected. Note whether every voice channel fails or just one.

    Look for: You can distinguish a broad outage or channel-specific problem from a single-device path issue.

  2. Reconnect and restart deliberately

    Leave and rejoin the channel. If appropriate, restart the client and your own network equipment without interrupting a shared network unexpectedly.

    Look for: A transient session problem is tested before changing lasting configuration.

  3. Review the permitted network path

    If using a VPN, confirm that it supports UDP for Discord voice. On work or school networks, ask the administrator about permitted voice access rather than trying to evade restrictions.

    Look for: The path's requirements and policy are known.

  4. Compare an authorized alternative

    Where permitted, test another normal network or a supported region change by the authorized channel administrator. Keep the client/account constant.

    Look for: A changed result helps identify the network or regional path involved.

Check the actual result

For an Automatic voice region, Discord's region guidance suggests reconnecting first. A region override affects the channel and should be temporary during diagnosis. Note the original setting and restore it if it does not improve the result.

If firewall or endpoint protection is involved, review the specific Discord allowance using the product's supported controls or your administrator's help. Do not leave protections broadly disabled as a permanent workaround for a voice call.

Make the next session predictable

If the failure persists, provide support with the error, client/OS versions, time, affected channels and which authorized comparisons changed the result. Follow their current diagnostic collection instructions and redact unrelated personal data before sharing screenshots.

Keep account secrets out of logs or public troubleshooting posts. A useful network report describes the path and behavior; it does not require publishing tokens, session cookies or an account password.

Still stuck?

The state is Waiting for Voice Server

Check Discord status first; the official guide treats this as a possible service-side issue.

It happens only through a VPN

Confirm UDP support and the VPN's permitted configuration. Use a normal allowed connection for comparison rather than bypassing a managed-network rule.

One channel fails but others work

Have the authorized administrator inspect region behavior and channel conditions. Preserve the original configuration while comparing.

Try it on your own setup

Start small: try the free files or continue with a guide for the part you’re working on.

Discord Mic Test Works but Nobody Hears You in a Channel ↗

Sources & references

Documentary review of current first-party help pages and indexed first-party excerpts, checked November 4, 2026. The diagnostic sequence and rehearsal examples are original editorial guidance; Foxdip did not operate a private account, run these broadcasts or measure performance. Expected results are checks for the reader to perform, not claimed test results.

  1. Discord — Voice Connection Errors ↗Checked 2026-11-04
  2. Discord — Voice Regions FAQ ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

Discord Mic Test Works but Nobody Hears You in a Channel

Check transmission mode, mute state and channel permission after proving that Discord can receive your microphone.

Discord Keeps Selecting the Wrong Mic: Choose an Explicit Input

Stop relying on an ambiguous default and trace whether the device changed in Discord, Windows or an audio mixer.