How to Use a Proxy With Discord: Desktop, Browser, Voice and Bots

Discord has no proxy setting, and it says it does not work with proxies. Its Help Center tells anyone with a proxy error that "Discord doesn't work with Proxies, so make sure to disable any Proxies". The desktop app still takes a proxy two ways: from the system settings, or from a Chromium switch on its shortcut.

Two limits decide almost every setup. The switch cannot carry a username and password. And voice uses UDP, which neither an HTTP nor a SOCKS proxy carries for the app. We checked both on our own machine, with the browser engine Discord's desktop app is built on and stub proxies on 127.0.0.1.

What does Discord say about proxies?

Discord's own help articles are short and consistent on this:

• On proxy errors: "Discord doesn't work with Proxies, so make sure to disable any Proxies." The error it names is ERR_PROXY_CONNECTION_FAILED.
• On a stuck connecting screen: go to the Windows Internet Options, then LAN settings, and "Uncheck 'Use a Proxy'". So the desktop app reads the system proxy.
• On voice errors: RTC Connecting and No Route usually mean "a firewall or possibly a VPN", and "Discord only works on VPNs that have UDP".

So a proxy with Discord is an unsupported setup. Discord's support will tell you to switch it off. Everything below works with that in mind, and none of it changes how Discord treats an account. Our page on Discord IP bans covers what an address can and cannot do there.

How does the desktop app take a proxy?

The system proxy

Discord's desktop app follows the proxy set in Windows or macOS, as its own help article implies. Set it once and every app that reads the system setting follows, including your browsers. Our guides for Windows and macOS show where the fields are. Quit Discord fully from the system tray, then start it again, so it reads the setting on launch.

The Windows proxy settings have no field for a login. So use a proxy that authenticates by your IP address, or a small relay on your machine that adds the login, as the authentication guide shows.

The switch, for Discord alone

Discord's desktop app is an Electron app, and Electron accepts Chromium's --proxy-server switch. It "overrides the system setting", by Electron's documentation, so Discord alone uses the proxy and the rest of the computer keeps its own connection.

The catch is where the switch goes. On a Windows install we checked (Discord 1.0.9264, October 2026), the Start menu shortcut does not start the app directly:

Target:    %LocalAppData%\Discord\Discord.exe
Arguments: --processStart Discord.exe

That first program is Discord's launcher, built on the Squirrel installer. It starts the newest installed version of the app. A switch added after --processStart Discord.exe goes to the launcher, which is not the app. Squirrel's source names the option that hands arguments on: --process-start-args, short -a, "Arguments that will be used when starting executable". So the shortcut's arguments become:

--processStart Discord.exe --process-start-args="--proxy-server=http://203.0.113.10:8080"

For a SOCKS5 proxy, change the scheme to socks5://. Quit Discord fully, then start it from that shortcut.

On a Mac, open -a Discord --args --proxy-server="http://203.0.113.10:8080" passes the same switch at launch.

Why can the switch not take a login?

Because Chromium does not support it. Electron's documentation says so in one line: "The proxy URL does not support username and password authentication."

We tested what happens if you write one in anyway. Our script started Chrome 155, the engine inside Discord's desktop app, against stub proxies on 127.0.0.1. Nothing was forwarded, so no request reached Discord:

Four results matter for Discord:

• No login travels. With a plain HTTP proxy, Chrome asked for discord.com:443 without any Proxy-Authorization header. When the stub asked for a login, the page failed.
• A login in the switch breaks it. Writing user:pass@ into the address made Chrome reject the proxy outright, with ERR_NO_SUPPORTED_PROXIES, for HTTP and for SOCKS5. It never connected.
• SOCKS5 offers no login method. Every SOCKS5 greeting offered one method, "no authentication". Chromium's documentation agrees: "No authentication methods are supported for SOCKSv5 in Chrome".
• UDP went around the proxy. With the HTTP proxy set, a local page that started WebRTC sent its UDP requests straight to our stub, without the proxy.

So the switch needs a proxy that lets you in without a login. Two kinds do: a proxy that authenticates by your IP address, or a small relay on your own machine that adds the login for you. The authentication guide shows both.

Why does voice skip the proxy?

Voice in Discord runs over UDP, and the proxy carries web traffic only. Three sources line up:

• Discord: voice works only "on VPNs that have UDP", and RTC Connecting points to something blocking it.
• Electron: the switch "only affects requests with HTTP protocol, including HTTPS and WebSocket requests".
• Chromium: SOCKS5 in Chrome "cannot be used to relay UDP traffic".

Our test shows the same thing from the other side: the UDP went straight out, past the proxy. With a proxy, voice either fails to connect or leaves from your own connection while the text goes through the proxy. If voice has to use another address, a VPN that carries UDP is the tool for it. We sell proxies, and a proxy cannot do this part.

How do you run Discord in a browser through a proxy?

The web app at discord.com/app follows the proxy of the browser it runs in. That lets you give Discord one address and the rest of the computer another. A browser extension such as ZeroOmega or FoxyProxy can send only Discord's sites through the proxy.

The same limits apply there. Chrome and Edge take no SOCKS5 login. Voice in the browser uses WebRTC, which our test saw leave over UDP around the proxy.

How do you run a Discord bot through a proxy?

A bot on a server behind a firewall, or one that should leave from a fixed address, needs two proxies. The discord.js guide names them: "a REST proxy and a WebSocket proxy". REST calls go through undici's ProxyAgent, and the WebSocket through the global-agent package:

// discord.js: REST through undici, the gateway WebSocket through global-agent
const { ProxyAgent } = require("undici");
const { bootstrap } = require("global-agent");
const { Client } = require("discord.js");

bootstrap();
global.GLOBAL_AGENT.HTTP_PROXY = "http://YOUR-LOGIN:YOUR-PASSWORD@HOST:PORT";
global.GLOBAL_AGENT.HTTPS_PROXY = "http://YOUR-LOGIN:YOUR-PASSWORD@HOST:PORT";

const client = new Client({
  intents: [],
  rest: { agent: new ProxyAgent("http://YOUR-LOGIN:YOUR-PASSWORD@HOST:PORT") },
});
client.login(process.env.DISCORD_TOKEN);

Unlike the desktop switch, these libraries accept a login in the address. A bot holds its gateway connection open for as long as it runs, so give it an address that stays put: a sticky session, or a static ISP proxy billed per IP.

What is the Discord Activities proxy?

A different thing with the same name. Activities, the apps that run inside Discord, cannot reach the internet directly. Discord's developer documentation says "all network traffic is routed through the Discord Proxy", built on Cloudflare Workers, and "WebRTC is not supported". Developers map their outside addresses to paths under /.proxy on their Activity's own discordsays.com host. No proxy you buy is involved.

How many people look for this?

Searches for a Discord proxy are small and steady:

The demand did not move with the months. People who want Discord on another address keep running into the same two limits.

What this page could not check

• We did not run Discord itself with a proxy. We read its shortcut and installed files without starting it, and tested the engine it runs on against stubs on 127.0.0.1.
• No real proxy and no voice call were tested, ours included.
• Discord's desktop voice runs in its own voice engine. Our UDP test used Chrome's WebRTC, so it shows how Chromium treats UDP under the switch, not Discord's voice code itself.
• Updates change things. Discord's launcher, Electron's switches and Chrome's behavior move with new versions; we will check this page again by January 23, 2027.

Sources

• Discord Help Center: Troubleshooting Console Log Errors, Voice Connection Errors, and Stuck on the Main Connecting Screen, each updated October 22, 2026, read October 23, 2026 through the Help Center API.
• Electron, Supported command line switches: --proxy-server, read October 23, 2026.
• Squirrel.Windows, Update.exe startup options, read October 23, 2026.
• Chromium, Proxy support in Chrome, read October 22, 2026.
• Discord Developer Documentation, Activities: Networking, modified February 6, 2026.
• discord.js Guide, Using a Proxy, read October 23, 2026.
• Google Ads Keyword Planner, Discord proxy terms, read October 23, 2026.
• HProxy test run: headless Chrome 155 against stub proxies on 127.0.0.1, Windows 11, October 23, 2026.