Discord Proxies · 1 min read

Proxies for Discord

Discord keys everything to your connecting IP. A proxy lets a bot or client present one clean, stable egress instead of your server's real address.

Why route Discord through a proxy

The configured s4m service uses datacenter proxy exits rather than a residential pool. Discord API, gateway and voice traffic may use different client transports. Configure supported paths and test them; changing an IP does not resolve account moderation.

Authenticated SOCKS5 (1080) and HTTP (3128) use the configured endpoint. Proxy credentials remain required when you choose another available exit. s4m has selectable public exit configurations. Use the endpoint or profile issued for the protocol and location selected in your account.

An exit IP can have a prior history. Accounts, cookies and browser signals may still identify a user; changing an address does not guarantee a clean reputation. A dedicated IP is exclusive during its assignment under the service terms. Prior history, assignment duration, availability and supported bindings still matter.

Credentials use USER:PASS. HTTP uses port 3128; SOCKS5 uses 1080. In Requests, socks5h requests remote DNS resolution; it does not encrypt proxy authentication. Related topics: datacenter SOCKS5 and HTTP proxies, dedicated personal IP, WireGuard VPN, VPN vs proxy comparison, guides.

What you get

One credential pair, two protocols, and an optional static IP built for long-lived connections.

Authenticated SOCKS5 + HTTP

The same USER:PASS works on port 1080 (SOCKS5) and 3128 (HTTP CONNECT). No IP allow-lists to babysit, no per-app account juggling.

Stable egress IP

Add a dedicated personal IP so your gateway connection keeps one address across reconnects instead of hopping a shared pool, associated with your s4m account.

No-logs by design

RAM-first infrastructure means no persistent record of what your bot connects to. Pay by card or crypto; anonymous accounts are supported.

Metered, pay-as-you-go

Proxy traffic is billed by usage, which suits a lightweight bot that mostly idles on the gateway and only bursts on events.

Set it up

Create an account

Start on a paid plan or go pay-as-you-go. Card or crypto both work, and anonymous accounts are fine.

Grab your proxy credentials

You get a USER:PASS pair for proxy.s4m.online: SOCKS5 on 1080, HTTP on 3128.

(Optional) attach a dedicated IP

Bind a static personal IP for a stable gateway connection instead of a shared, more-detectable range.

Point your bot or client at it

Set the HTTP proxy for discord.py, or use socks5h for SOCKS-aware clients. Test with curl before you wire it into the bot.

Config and quick test

Replace USER:PASS and the token with your own. proxy.s4m.online is the fixed host; nothing here is a real IP.

bash
# 1) Test reachability through the HTTP proxy (CONNECT tunnel)
curl -x http://USER:[email protected]:3128 \
  https://discord.com/api/v10/gateway

# 2) Same test over SOCKS5, DNS resolved proxy-side (socks5h)
curl --proxy socks5h://USER:[email protected]:1080 \
  https://discord.com/api/v10/gateway

# 3) discord.py bot through the HTTP proxy
#    pip install -U discord.py
python - <<'PY'
import discord

client = discord.Client(
    intents=discord.Intents.default(),
    proxy="http://USER:[email protected]:3128",
)
client.run("YOUR_BOT_TOKEN")
PY

# 4) SOCKS5 for aiohttp-based clients
#    pip install aiohttp_socks
#    from aiohttp_socks import ProxyConnector
#    connector = ProxyConnector.from_url(
#        "socks5://USER:[email protected]:1080")
FAQ

Questions, answered

Are these residential Discord proxies?

No. s4m sells datacenter SOCKS5 and HTTP proxies. They're fast and inexpensive, but Discord and similar consumer platforms detect datacenter ranges more easily than residential ones, so a shared IP can be challenged. A dedicated personal IP is the most stable option we offer.

Will a proxy unban my account or bot?

No, and don't count on it. Discord's enforcement isn't defeated by changing IPs, and evading bans violates Discord's Terms. Use a proxy to keep a legitimate bot online behind a clean, stable IP, not to dodge moderation.

Should I use SOCKS5 or HTTP for Discord?

Either works. HTTP on port 3128 is simplest for libraries like discord.py that take a proxy URL. Use SOCKS5 on port 1080 with socks5h when you want DNS resolved proxy-side, or when your client is SOCKS-aware via aiohttp_socks.

Can I keep the same IP across reconnects?

Yes. Request a dedicated IP for a consistent proxy exit. Its allocation stays associated with your s4m account. Discord Gateway reconnects, session resumption, and rate limits still depend on Discord's protocol and policies.

Do you log what my bot connects to?

No-logs by design. The infrastructure is RAM-first, so there's no persistent record of your bot's traffic. Billing works by card or crypto, and anonymous accounts are supported.

Run Discord behind a clean, stable IP

Start on a paid plan or go pay-as-you-go, add a dedicated personal IP when a long-lived gateway connection needs one, and test your bot in minutes. See /pricing/ for proxy rates and the dedicated IP add-on, or /proxy/ for the full setup.

People found this page by searching for

Real search phrases this page answers — the linked ones open the page that covers them in depth.