Relay failed: bad response. #451

Activity

1. w0l4i commented on Apr 28, 2026

   

   w0l4i

   on Apr 28, 2026

   More actions

   • last code.gs
   • executables ver 1.8.3
   • operating system : windows 11
   • ISP mobinnet

   I don't know what would be the actual parameters and expectations but these are my observation so far in case of the functionality:

   • no live video on youtube plays more than 30 sec
   • slow updating and constant reconnecting in Telegram
   • unable to login to x.com via chrome browser or any where else.
   • inconsistent functionality on Pinterest, almost unavailable
   • windows update catch error
   • no video play on Pornhub, XHamster other porn services
   • nothing on Github so far

   this is the warning log I get,

   2026-04-28T20:54:22.450729Z ERROR Relay failed: bad response: no json in:

   !DOCTYPE html <title>Web App</title>

   The script completed but did not return anything.

   did you tried to redeploy and add new deployment id to client ?
2. w0l4i commented on Apr 28, 2026

   

   w0l4i

   on Apr 28, 2026

   More actions

   اگر کانفیگ درست باشد در ورژن 1.8.3 مشکلتون باید حل شده باشه
3. therealaleph commented on Apr 28, 2026

   

   therealaleph

   on Apr 28, 2026

   Owner

   More actions

   @AliMovahednia — your symptom list points strongly at a mix of three issues:

   1. The body string is the v1.8.x decoy/placeholder pattern.

   Per v1.8.3's diagnostic taxonomy, The script completed but did not return anything matches one of 6 candidate causes:

   1. AUTH_KEY mismatch in your config.json vs Code.gs
   2. Apps Script execution timeout (per-invocation 6-min cap or 30s soft cap)
   3. Apps Script per-100s rolling soft quota
   4. ISP-side response truncation (App script Unresponsive ERROR #313 pattern, common on Iranian ISPs)
   5. Apps Script's Persian-localized soft-quota body (if your Google account locale is fa-IR)
   6. Workspace landing HTML (account flagged for phone-verification — see Google account action required #421)

   Mobinnet ISP is not typically as aggressive as TCI/مخابرات for the #313 throttle, but it does happen. So either AUTH_KEY mismatch (#1) or quota tear / Iran ISP truncation (#3 / #4) is most likely for you.

   2. The _2026-04-28T20:54:22_ timestamp is in the v1.8.x window so you're getting the new soft-detection messages. Good.

   3. Your specific symptoms map to:

   • YouTube live video doesn't play >30s → SABR cliff (لود نشدن ویدیو های یوتیوب بیشتر از 59 ثانیه #300). Architectural; can't be fixed in apps_script mode. Workaround: Full mode + VPS, or accept short-video-only.
   • Slow Telegram + reconnects → addressed in v1.8.4 (just released ~5 minutes ago) via PR fix(tunnel-node): raise long-poll to 15s, adaptive straggler settle #446 raising tunnel-node long-poll from 5s to 15s. Persistent connections (Telegram XMPP) won't reconnect every 5s anymore. Upgrade to v1.8.4 and Telegram should be much smoother.
   • x.com login fails → CF CAPTCHA / bot detection. Cloudflare flags traffic from Google IPs as suspicious. Closed thread Cloudflare error #382 covers workarounds. Roadmap Feature Request: Support Cloudflare WARP as an Outbound for Geo-blocking and Captcha Mitigation #309 (CF WARP integration).
   • Pinterest / GitHub partial functionality → likely combination of CF detection + the response cliff for image-heavy pages.
   • Adult video sites not working → typically these use CDNs that flag Google IPs aggressively. Also: video streaming hits the SABR-style cliff. Same architectural ceiling.
   • Windows Update errors → Windows Update uses HTTPS, but the binaries are large (sometimes >500 MB). The 30s response cliff truncates the binary downloads. Same as the IDM download issue (A way to download? #441) — Range-aware splicing in v1.8.x roadmap will help; Full mode + VPS is the immediate fix.

   Recommended diagnostic sequence:

   Step 1: Upgrade to v1.8.4 (just released — DoH bypass + adaptive coalescing + tunnel-node fix should help several of your symptoms).

   Step 2: Direct curl test to disambiguate AUTH_KEY mismatch vs quota/ISP:

   curl -L -X POST "https://script.google.com/macros/s/YOUR_DEPLOYMENT_ID/exec" -H "Content-Type: application/json" -d "{\"k\":\"YOUR_AUTH_KEY\",\"u\":\"https://httpbin.org/get\",\"m\":\"GET\"}" --max-time 30

   Run 5-10 times. If JSON success >80% → not ISP throttle, likely AUTH_KEY mismatch. If timeouts >50% → ISP throttle (#313 / Mobinnet variant).

   Step 3: If AUTH_KEY mismatch likely, set DIAGNOSTIC_MODE = true at the top of Code.gs in Apps Script editor + redeploy as new version (not edit existing). Then re-test:

   • If you now see {"e":"unauthorized"} JSON → confirmed AUTH_KEY mismatch. Align values + redeploy.
   • If you still see the same decoy HTML → it's NOT AUTH_KEY (one of causes 2-6).

   Step 4: If ISP throttle, in config.json:

   {
     "disable_padding": true,
     "google_ip": "172.217.16.46"
   }

   (disable_padding: true saves ~25% bandwidth, which compounds favorably under throttle. The alternate google_ip is one of the 12-entry pool — try a few from DEFAULT_GOOGLE_SNI_POOL in src/domain_fronter.rs if your default fails handshake.)

   Step 5: For long-running content (live video, Windows updates, large downloads): only Full mode + VPS resolves these. The 30s response cliff is architectural in apps_script mode. See #310 / #333 for VPS setup.

   Report back with:

   • Result of the curl test (success rate / typical time)
   • Whether v1.8.4 changes the Telegram experience
   • Whether DIAGNOSTIC_MODE flip changes the body content

   We can narrow further with that data.

   ---

   _{[reply via Anthropic Claude | reviewed by @therealaleph]}
4. therealaleph commented on May 15, 2026

   

   therealaleph

   on May 15, 2026

   Owner

   More actions

   Closing this for now because there has not been a follow-up from the original reporter for more than 7 days.

   If this is still happening on the latest release, please comment here or reopen with the current version, mode, relevant config shape, and fresh logs.

   ---

   Answered via LLM, Supervised @therealaleph
5. therealaleph

   closed this as completedon May 15, 2026