Discord (PC) Doesn't open.

[Sakura23151]

Hello, unfortunately I was signed out of my google accounts and since Iran's internet is currently severely restricted, I cannot sign back in (There's an error during the 'phone verification' section, it keeps saying something went wrong and 'try again'.)
As a result I can't Web Discord (Since I've been logged out of the gmail account I had it on and it's been 2 months since I logged in, hence I'll need to access it to get a 'verification' code).
On Discord, the client gets stuck around the "Starting..." part, and that's it.
But my Discord Client on PC Is still logged in. Any solutions with this app?
If not, any other tunnels I could use? (My ISP is Irancell)
Much appreciated if I could get an answer because I can't really access any other forums, thank you in advance for this great app.
I apologize if this question is not exactly relevant to the 'issues' section, but I have no other sources to use for info I'm afraid.

[therealaleph]

Hi @Sakura23151 — Discord stuck at "Starting..." on the desktop client is a known shape of failure on Irancell + DPI. The Discord client tries to hit gateway.discord.gg via WebSocket on startup, and on heavy DPI that handshake either gets blocked or stalled.

Try this path first (apps_script mode):

1. Run mhrv-rs in apps_script mode (Connection mode: Proxy only is fine for Discord PC)
2. Note the HTTP port: 127.0.0.1:8085
3. In Windows, set the system proxy (not just per-app):
   • Settings → Network & internet → Proxy → Manual proxy setup
   • Address: 127.0.0.1, Port: 8085
   • Save
4. Fully quit Discord (right-click tray icon → Quit Discord — not just close window)
5. Re-launch Discord

Discord PC respects the system HTTP proxy. With mhrv-rs catching all HTTPS traffic and routing through Apps Script, the gateway connection should succeed.

If it still hangs at "Starting...":

Discord uses HTTP/3 (QUIC) in newer builds. QUIC is UDP and can't be tunneled through apps_script mode (Apps Script is HTTP-only). The fallback to TCP usually works, but on aggressive DPI, Discord retries QUIC indefinitely instead of falling back. Workaround: in Discord's %appdata%\discord\settings.json, add "DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING": true then in the app press Ctrl+Shift+I → Console → run localStorage.setItem("disableHardwareAcceleration", true) (less elegant: just edit the launch command to add --disable-quic if you can launch with flags).

For Discord voice / video: that's UDP, won't work through apps_script mode at all. You'd need Full mode with a VPS for voice.

On the "can't sign in to Google because of phone verification": that's a separate problem and unfortunately unsolvable from this side — Google's anti-fraud requires SMS to a non-Iranian number for some accounts. If your account is locked behind that, mhrv-rs can't help; the verification call comes from Google's servers to your phone, which is independent of the proxy. People sometimes use a temporary number from getsmscode.com or similar, but YMMV and it can permanently flag the account.

Try the system proxy + Discord restart first and report back if Discord still hangs. The "Starting..." part will tell us which subsystem is failing.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[Sakura23151]

Thank you very much, unfortunately it's still hanging at the 'Starting...' section.
To clarify yes, obviously I'm not stupid enough to try to open up Discord without 'proxying' my entire windows, I already have done that, unfortunately, same results as you might expect. And yes I am using the newest Discord version (1.0.9234)

So here's what I did, first of all I changed the settings.json file found in the %appdata% in the 'Roaming' section, in the Discord folder.
I'm no software geek but I put it in the same section (brackets) as the other commands.
Unfortunately no dice, I couldn't open the console via CTRL SHIFT I.
The next step was adding flags, which I did, I went inside the Discord folder located in the 'Local' appdata, made a shortcut, changed the target to this:
C:\Users\XXX\AppData\Local\Discord\app-1.0.9234\Discord.exe --disable-quic

Again, no dice on this end... sadly.
Though something strange did happen, for some reason after I used the flag you gave me, the settings.json file was shortened to this:
{ "IS_MAXIMIZED": false, "IS_MINIMIZED": false, "WINDOW_BOUNDS": { "x": 640, "y": 151, "width": 1280, "height": 725 } }

And about the google thing, I figured it would be unsolvable on your end, because I did manage to get a linkedin message but not one from google, it just keeps giving me errors regardless of whether I use your app or not.
It's mostly related to the internet outage in that case, so the only viable solution is to wait.

[Sakura23151]

Small update : I used one of your configs to see if I could log into my gmail, after inputting my number, same thing happened, I was told to piss off.
Again to clarify, I'm simply trying to log into a gmail account that I've had for Eons, and whenever I input my number for it to send me an SMS, it just tells me to go away.
As for how this (How I was logged out) happened : I Cleared my browser cache. Pretty stupid, I know...

So far (With tunneling, am using V2RAY for your configs) it doesn't appear to be able to make Discord work.
And sadly now the config stopped working, I'm assuming my ISP caught up to me.
Can I ask, could your https://github.com/therealaleph/sni-spoofing-rust help? (Though currently, I've had no luck connecting to cloudflare, since it's blacklisted)
(at least I'm assuming my ISP caught up since when I use the 'test real delay' it gives me these : An existing connection was forcibly closed by the remote host.)