Fake and broke as in no longer functionally working ?

[imanbarati]

it was good i was running it
Now
look like it is not working at all stuck or super slow
not opening any sites

2026-05-04T09:08:38.857436Z INFO Both the glow and wgpu renderers are available. Using glow.
2026-05-04T09:08:45.228135600Z [ui] starting proxy...
2026-05-04T09:08:45.229037Z INFO Loaded MITM CA from C:\Users\Pas18\AppData\Roaming\mhrv-rs\config\ca/ca.crt
2026-05-04T09:08:45.229107500Z [ui] listening HTTP 127.0.0.1:8085 SOCKS5 127.0.0.1:8086
2026-05-04T09:08:45.231041Z WARN Listening HTTP on 127.0.0.1:8085 — set your browser HTTP proxy to this address.
2026-05-04T09:08:45.231051Z WARN Listening SOCKS5 on 127.0.0.1:8086 — xray / Telegram / app-level SOCKS5 clients use this.
2026-05-04T09:09:04.650991Z INFO pool pre-warmed with 3 connection(s)

12:30:37 • INFO [Main ] DomainFront Tunnel starting (Apps Script relay)
12:30:37 • INFO [Main ] Apps Script relay : SNI=www.google.com → script.google.com
12:30:37 • INFO [Main ] Script ID : ati
12:30:37 • INFO [Main ] MITM CA is already trusted.
12:30:37 • INFO [Main ] LAN sharing enabled — listening on all interfaces
12:30:37 • INFO [LAN ] LAN HTTP proxy : 192.168.50.247:8085
12:30:37 • INFO [LAN ] LAN SOCKS5 proxy : 192.168.50.247:1080
12:30:37 • INFO [Fronter ] HTTP/2 multiplexing available — all requests will share one connection
12:30:37 • INFO [Fronter ] SNI rotation pool (3): mail.google.com, accounts.google.com, www.google.com
12:30:37 • INFO [Fronter ] Execution monitor enabled: reporting total every 5s
12:30:37 • INFO [Fronter ] Batch config: micro=15ms macro=120ms max=64
12:30:37 • INFO [Fronter ] Response codecs: gzip, deflate, br, zstd
12:30:37 • INFO [MITM ] Loaded CA from C:\Users\Pas18\Desktop\MasterHttpRelayVPN-python_testing\MasterHttpRelayVPN-python_testing\ca
12:30:37 • INFO [Proxy ] Relay warmup in progress... waiting up to 20s before opening listeners
12:30:40 • INFO [Fronter ] SNI probe kept order: mail.google.com (493ms), accounts.google.com (522ms), www.google.com (595ms)
12:30:41 • INFO [H2 ] H2 connected → 216.239.38.120 (SNI=mail.google.com, TCP_NODELAY=on)
12:30:41 • INFO [Fronter ] H2 multiplexing active — one conn handles all requests
12:30:41 • INFO [Fronter ] Pre-warmed 30/30 TLS connections
12:30:41 • INFO [Proxy ] Relay warmup complete — enabling HTTP/SOCKS listeners
12:30:41 • INFO [Proxy ] HTTP proxy listening on 0.0.0.0:8085
12:30:41 • INFO [Proxy ] SOCKS5 proxy listening on 0.0.0.0:1080
12:30:42 • INFO [Fronter ] Apps Script pre-warmed in 228ms
12:30:42 • INFO [Fronter ] Apps Script executions used so far: 2
12:34:42 • INFO [Fronter ] Apps Script executions used so far: 3

[therealaleph]

@imanbarati — your log shows you're running two different clients hitting the same Apps Script deployment at the same time. The first block is mhrv-rs (pool pre-warmed with 3 connection(s)); the second block — 12:30:37 • INFO [Main] DomainFront Tunnel starting (Apps Script relay) from MasterHttpRelayVPN-python_testing/ on your Desktop — is the upstream Python client running in parallel.

Both clients are sending requests to your Apps Script. Apps Script has a 30-concurrent-request limit per Google account, so when both clients fight for the same pool, requests queue and time out. That's why it's "stuck or super slow" even though it was working before.

Fix: pick one client, kill the other:

• If you want mhrv-rs: stop the Python MasterHttpRelayVPN-python_testing (close that terminal) and only run mhrv-rs
• If you want the Python upstream: stop mhrv-rs and only run the Python client

Don't run both pointing to the same script_id. If you really want two clients running, you need two different Apps Script deployments (one per client) so each gets its own 30-concurrent budget.

Closing — open back if you've stopped the Python client and mhrv-rs is still slow.

---

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

[imanbarati]

NO it is looking a lot like script.google is not with us any more and it is blocked by gfw of china irn irgc