Discord Worked Everywhere Except the Voice Channel

The voice channel showed six people already inside. I clicked it, heard the joining sound and waited for their names to light up. Instead, Discord displayed RTC Connecting beneath the channel title. Ten seconds passed. Then twenty. I left, rejoined and restarted the app. The same message returned. In twelve minutes, I was supposed to run an online game session for a group that had arranged three time zones around it. Text chat worked, the campaign files opened and everyone could see me typing apologies. I simply could not speak to them.

I was staying in university accommodation in Rotterdam for a short research programme. The building supplied fast Wi-Fi, but residents had no access to the router, and nobody answered the support number after 8 p.m.

At first, I blamed Discord.

The platform had experienced a voice-connection incident on July 22, 2026, so another service problem seemed plausible. But the status page showed no active voice outage, and the people waiting in my channel were already talking to one another. (Discordstatus)

The problem was at my end.

I changed the voice region, closed every other application and restarted the laptop. Discord still stopped at the same two words:

RTC Connecting.

Then I disconnected the VPN.

The voice channel opened immediately.

I heard five people speaking at once.

That identified the cause but did not give me a usable solution. I was on a shared residential network, handling work accounts and personal messages on the same laptop. Leaving the VPN disabled for a three-hour call meant solving the voice problem by giving up the protection I wanted.

I needed Discord to connect with the VPN still on.

A green VPN icon did not mean voice was working

My established VPN was the reasonable first choice.

It had years of public history, a large server network and a mature desktop app. I reconnected through the nearest available city, returned to Discord and clicked the channel.

RTC Connecting.

I selected another nearby server.

This time Discord moved from RTC Connecting to No Route, then returned to RTC Connecting.

The third server looked more promising. I heard the joining sound and one second of someone’s voice before the connection dropped.

Text chat continued working throughout.

That difference narrowed the problem. Discord was not completely blocked, and the VPN was not completely disconnected. The route could carry messages but could not complete the live voice connection.

Discord groups RTC Connecting, ICE Checking and No Route together as voice-connection errors. Its support guidance also notes that Discord voice requires a VPN capable of carrying UDP traffic. (Discord)

That matched what I was seeing. The VPN icon remained green, and Discord’s text channels stayed active, but the path needed for real-time audio never finished connecting.

With the session getting closer, changing servers stopped feeling like troubleshooting. It felt like repeating the same failure in different cities.

Restarting Discord only restarted the wait

With seven minutes left, I worked through the familiar fixes.

I ran Discord as an administrator.

I disabled its high-packet-priority setting.

I signed out and back in.

I switched from the desktop app to the browser.

Each attempt changed the appearance of the problem without changing the result.

The browser stayed on Connecting.

The desktop app alternated between RTC Connecting and No Route.

Restarting the laptop appeared to help for a moment. I entered the channel, heard the end of a sentence and disappeared again before I could answer.

That brief success encouraged one more restart, followed by one more server change. It was also a familiar pattern in public user discussions: a restart might open one call, but RTC Connecting soon returns. (Reddit)

The rest of Discord made the failure especially persuasive.

I could type.

I could upload an image.

I could see everyone waiting.

It always felt as though one more small adjustment would make the voice channel behave like the rest of the app.

It never did.

By then, the comparison had changed. I did not need more settings to try. I needed one protected route that Discord voice could use immediately.

The nearest server was not the useful server

Discord voice has to establish a live path through the local network, the VPN and Discord’s voice infrastructure. If that path fails, text can continue working while voice remains stuck at RTC Connecting. (MDN)

That was enough technical explanation to understand the problem.

It also exposed the weakness in my approach.

I had been choosing servers by distance, assuming the nearest city would produce the easiest connection. But the server map could not tell me which route would cooperate with the accommodation network and complete the Discord call.

The established provider offered dozens of nearby choices.

With five minutes left, every extra choice meant another disconnect, another restart and another wait beneath the same message.

I closed the server map.

The task was no longer finding the closest VPN server.

It was getting into the room.

The smaller app began with the conversation

OnlydogVPN was already installed on the laptop as a travel backup.

It had fewer server locations, a shorter public history and fewer independent reviews than the larger provider. Those were the reasons I had not opened it first.

But it approached the problem differently.

Instead of asking me to choose another country or protocol, the app organised its options around situations. I selected the preset for voice and gaming and connected.

Then I clicked the Discord channel.

The joining sound played.

The RTC Connecting message disappeared.

I heard someone say, “He’s back.”

My microphone indicator turned green when I answered.

The connection held.

That was the result I had been searching for.

Not another VPN server that claimed to be connected.

Not one second of audio before No Route returned.

I was inside the voice channel, speaking normally, with the VPN still active.

The smaller app used HTTP/3-based transport with traffic obfuscation, giving Discord a different route from the paths that had repeatedly failed. More importantly, it made that route available through one task-based preset instead of another round of manual server selection.

The technical explanation could remain brief because the useful evidence was already in front of me.

Six people could hear me.

The Wi-Fi changed, but the call stayed open

We began the session four minutes late.

For the first half hour, Discord remained connected. Voices arrived clearly, and the latency indicator stayed steady enough that no one spoke over delayed versions of one another.

Then the accommodation Wi-Fi weakened.

My browser stopped loading the campaign map. One participant’s voice stretched into a metallic fragment and vanished.

I expected Discord to return to RTC Connecting.

The laptop switched to my phone hotspot, which was already configured as its backup connection. The call paused for a moment.

Then the voices returned.

I was still in the channel.

There was no server-selection screen. Discord did not send me through ICE Checking or No Route again. I continued from the same sentence and reopened the campaign map over mobile data.

The app’s HTTP/3-based transport was designed to preserve the connection when the underlying network changed, and here it did exactly what the situation required. (IETF)

The established VPN had failed to open a dependable voice connection while the Wi-Fi was still active. The smaller app opened the channel and then carried it through an actual change of network.

I could not observe the accommodation’s internal filtering rules or the service’s complete server-side routing. I could observe the outcome: Discord connected, the conversation continued and the VPN remained active.

From that point on, I stopped watching the connection label.

The call ended before the connection did

The session lasted just under three hours.

Discord stayed connected while I shared images, played background audio and moved between text and voice. When someone joined late, I heard the notification immediately. When another participant left, the rest of the channel continued normally.

Nothing dramatic happened.

That was the advantage.

I did not ask six people to wait while I tested another city. I did not disable the VPN and promise myself I would remember to turn it back on later. I did not restart Discord every time the conversation paused.

When the session ended, I left the voice channel deliberately.

The connection had never forced me out.

What RTC Connecting was actually telling me

RTC Connecting did not mean that all of Discord had failed.

It meant the voice channel had not found a usable path.

That was why the symptoms seemed so selective:

Text messages still sent.

Servers and channels still loaded.

Friends were visibly inside the call.

Voice remained stuck on RTC Connecting or No Route.

The established provider offered more locations, but every new location created another guess.

The smaller app reduced the problem to the task in front of me. Its voice-and-gaming preset opened the channel with the VPN still active, and its connection recovery kept the conversation alive when the laptop moved from residence Wi-Fi to mobile data.

The important test was never whether the VPN said Connected.

It was whether Discord connected too.

The error changed what I expected from a VPN

I began the evening assuming the larger VPN gave me more control.

When Discord failed, I had countries, cities, protocols and settings to change. Each option created another attempt, but none completed the call.

The smaller app did not give me more decisions.

It gave me the conversation.

The established provider connected my laptop to a VPN server.

The smaller app connected me to the people already waiting in the room.