Discord has a particular way of failing. It rarely goes down cleanly — instead the text chat works, the voice channel sits on RTC Connecting forever, screen share shows a black rectangle, and your friend on the same server hears everything perfectly. That asymmetry is the whole story: Discord's text runs over an ordinary web connection, while voice and video run over UDP, which is far pickier about the network it crosses.

This guide is organized the way the failures actually happen — by device. PC, phone, PS5 and Xbox each break for different reasons and need different fixes. Along the way we cover the settings that genuinely matter for voice quality, the ones that are cargo cult, and the point at which the problem stops being something you can fix in Discord's settings at all.

Why is Discord not working right now?

Start by separating three very different situations, because the fix for each is nothing like the others.

Everyone is affected. Check discordstatus.com. If there is an active incident, nothing you do locally will help — the fix is patience.

Only you are affected, on every device. Text sends, voice fails, images will not load, on both your laptop and your phone. Since the two devices share nothing except the network, the network is the suspect.

Only one device is affected. Everything works on your phone but the desktop app hangs on Connecting…. Now it is a client problem: cache, an audio subsystem setting, a firewall rule, or a stale version.

That triage takes a minute and saves you from reinstalling an app that was never the problem. The single most informative test: switch your phone from Wi-Fi to mobile data. If voice suddenly works, Discord and your account are fine and the home network is the issue.

Discord not working on PC

The desktop client is the most fixable of the lot, because almost everything lives in settings you control.

  • Clear the client cache. On Windows, close Discord completely (check the system tray), press Win+R, type %appdata%\discord and delete the Cache, Code Cache and GPUCache folders. On macOS the equivalent lives in ~/Library/Application Support/discord. This alone fixes a startup hang on Connecting… more often than anything else.
  • Switch the audio subsystem. Open User Settings → Voice & Video, scroll to Audio Subsystem and try Legacy. If you get dropped from voice channels every few minutes, or your mic dies while the app keeps running, this is the setting.
  • Turn off Quality of Service High Packet Priority. Same page. Discord marks voice packets as high priority, and a surprising number of routers and ISPs handle those marked packets badly — sometimes dropping them outright. Turning it off is the standard fix for choppy voice that no amount of bandwidth explains.
  • Disable hardware acceleration under Advanced if screen share is a black screen or the app stutters.
  • Check the firewall and your antivirus. Discord needs outbound UDP on a wide port range. A firewall rule that only permits TCP gives you exactly the symptom set of working text and dead voice.
  • Run the web client as a test. Open discord.com/app in a browser. If voice works there but not in the desktop app, the problem is the installed client — reinstall it. If both fail identically, it is the network.

Discord not working on phone (iPhone and Android)

Mobile failures are usually power or data policy, not Discord.

On iPhone, check Settings → Cellular → Cellular Data Options → Low Data Mode and the same toggle on your Wi-Fi network — Low Data Mode interferes with the continuous stream that voice requires. Then check Settings → General → Background App Refresh, and make sure Discord has microphone permission under Settings → Discord. If you use iCloud Private Relay, note that it and a VPN cannot both be active, and the interaction sometimes leaves connections half-established.

On Android, the usual suspect is battery optimization. Open the app's info page, go to Battery and set Discord to Unrestricted — otherwise the system suspends it the moment you switch apps, which is exactly when you are gaming and talking. Then check Data Saver in network settings, and clear the app cache via App info → Storage → Clear cache (not Clear data, which logs you out).

Discord not working on PS5 and Xbox

Console Discord is a different product from the desktop app and fails in its own ways. Two things to know up front: on consoles the integration is voice only — there is no text chat, no server browsing, no screen share — and it depends on your account link, not on an app you can reinstall.

On PS5: the link lives in Settings → Users and Accounts → Linked Services → Discord. If voice will not start, unlink and relink the account there, then sign out of Discord on your phone and back in. A stale link is the most common cause of "the join button does nothing".

On Xbox: the equivalent is under your account's linked social accounts. The same relink cycle applies.

On both: check your NAT type in the console's network settings. Strict NAT — common behind double NAT, carrier-grade NAT on some ISPs, or a router with UPnP disabled — is a textbook cause of voice that connects and then produces silence in one direction. Enabling UPnP on the router, or putting the console in the DMZ, usually resolves it. Also confirm the console is on 5 GHz Wi-Fi or, better, a cable: voice chat and a game download competing on a congested 2.4 GHz band is an unwinnable fight.

Discord not working on Wi-Fi but fine on mobile data

If this describes you, the finding is valuable: your account, your device and Discord's servers are all fine, and the difference is the network path.

Work through it in this order. Reboot the router — consumer routers degrade after weeks of uptime and UDP session tables are the first thing to fill. Move to the 5 GHz band. Change DNS to 1.1.1.1 or 8.8.8.8. Check whether the router has any "gaming mode", QoS or traffic-shaping feature enabled and turn it off as a test, since those features frequently mangle exactly the traffic they claim to prioritize. If the network is one you do not control — an office, a campus, a hotel — then UDP is often restricted by policy, and that is the administrator's decision to make, not a setting you can fix from the client.

If all of that leaves you with working mobile data and broken Wi-Fi, the remaining variable is the route between your provider and Discord's voice servers.

Discord stuck on "RTC Connecting": what it actually means

RTC Connecting means the client has authenticated fine and is now trying to open the real-time media connection to a voice server — and failing. No Route means the same thing after it gave up. The text side of Discord is unaffected, which is why everything looks half-alive.

In order of likelihood: a firewall or antivirus blocking outbound UDP; a VPN or proxy that routes TCP but not UDP; strict NAT; a router QoS feature interacting badly with Discord's packet priority marking; or a genuinely congested path to the voice region you were assigned.

The fastest targeted fix is a region override. Discord picks a voice region automatically per channel, and its pick is not always the best one. On a server where you have permission, hover the voice channel, open Edit Channel → Overview, and set Region Override to a specific nearby region instead of Automatic. If you have no permission, ask whoever runs the server — it takes them ten seconds, and it fixes a startling share of "only our server has bad voice" complaints.

Discord voice chat settings that actually matter

Setting Where it lives Fixes
Audio Subsystem → Legacy Voice & Video Random disconnects, mic dying mid-call
QoS High Packet Priority → off Voice & Video Choppy voice on routers that mishandle priority marks
Region Override Channel → Edit Channel → Overview High latency, RTC Connecting on one server
Input mode → Push to Talk Voice & Video Background noise, half-open mic
Hardware acceleration → off Advanced Black screen share, app stutter
Reset Voice Settings bottom of Voice & Video A broken config you can no longer trace

Try them one at a time. Changing five settings at once means you learn nothing about which one mattered.

How to choose a VPN for Discord voice chat

If the fixes above left you with the conclusion that your network path is the problem, routing Discord through a different path is the remaining lever. A VPN sends your traffic through a server you choose and on to Discord from there, which gives you a consistent, encrypted route instead of whatever chain of intermediate networks you happened to get. On public Wi-Fi in a café or a hotel it also means nobody on that network can see your traffic.

For voice specifically, the requirements are narrower than for general browsing:

  • Low latency and nearby servers. Voice tolerates modest bandwidth but punishes delay. A distant server adds ping you will hear.
  • Full UDP support. A tunnel that only carries TCP will leave you on RTC Connecting forever. This is the single most important question to ask.
  • A modern protocol. VLESS and WireGuard add minimal overhead compared with older options.
  • Genuine capacity. An overloaded free server turns choppy voice into unusable voice. This is where free services fail hardest.
  • No logs, and every device on one subscription. Gaming PC, phone, laptop — one account.

Orris VPN fits that profile: up to 1 Gbit/s, the VLESS protocol, unlimited traffic, a no-logs policy, servers in several countries, and Windows, macOS, Linux, iOS and Android from a single subscription — from about $1.7/month, with a free trial and payment by card or crypto.

Discord myths that waste your time

  • "It's my PC." If voice fails on your phone too, the hardware is not the variable — the network is.
  • "Any free VPN will do." Free servers are oversubscribed and often drop UDP entirely. For voice chat that is worse than no VPN at all.
  • "A VPN always adds lag." It adds one hop. Whether your total latency goes up or down depends on whether your original route was good; on a bad route, a clean path can measurably lower ping.

FAQ

Why is Discord not connecting to voice chat? Almost always outbound UDP: blocked by a firewall, mangled by router QoS, or degraded on the path to the voice server. Try a region override and disable QoS High Packet Priority first.

What does RTC Connecting mean in Discord? The client cannot establish the real-time media connection to the voice server. Text still works because it uses a different connection entirely.

Why does Discord work on mobile data but not Wi-Fi? Your home network or its route is the difference. Reboot the router, move to 5 GHz, change DNS, and turn off any router QoS or gaming mode.

Why is Discord voice not working on PS5? Most often a stale account link. Unlink and relink Discord in the console's linked services, and check that your NAT type is not strict.

Does Discord on Xbox and PS5 include text chat? No. The console integration is voice only; text chat stays on phone, desktop and web.

Will a VPN make my Discord ping worse? Only if the server is far away or overloaded. A nearby server on a fast service usually keeps ping flat and can improve it when your default route is congested.

Conclusion

Discord failures are almost always a UDP story. Text survives nearly any network; voice and video do not. So triage by device first — status page, then a second device, then a different network — and only then start changing settings. On PC, clear the cache, try Legacy audio and turn off QoS priority. On phone, look at battery optimization and data saver. On console, relink the account and check your NAT type.

When the conclusion is that the network path itself is the problem, a fast VPN with real UDP support and servers close to you is the clean fix — Orris gives you an encrypted, predictable route on every device at once. If you are setting it up on a phone first, see our VLESS guide for iPhone; for a whole household of consoles and PCs, a router-level install covers everything in one go, and if you are still deciding, start with what a VPN actually does.