ارور میده

[Morrigan-Ship]

2026-05-07T18:44:03.008610Z INFO test: probing https://api.ipify.org/?format=json via SNI=www.google.com @ 216.239.38.120
2026-05-07T18:44:03.192997Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.254384Z INFO h2 connection established to relay edge
2026-05-07T18:44:03.322342Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.412705Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.418027Z INFO HTTP POST http://91.108.56.177:80/api

والا من بیگوناهم

v1.9.17

[w0l4i]

2026-05-07T18:44:03.008610Z INFO test: probing https://api.ipify.org/?format=json via SNI=www.google.com @ 216.239.38.120
2026-05-07T18:44:03.192997Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.254384Z INFO h2 connection established to relay edge
2026-05-07T18:44:03.322342Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.412705Z ERROR Relay failed: relay error: Exception: سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch.
2026-05-07T18:44:03.418027Z INFO HTTP POST http://91.108.56.177:80/api

والا من بیگوناهم

v1.9.17

quota limit reached try to increase deployment IDs as 1 on each google account

[therealaleph]

Reviewed via Anthropic Claude.

سرویس در طول یک روز به دفعات زیاد فراخوان شده است:urlfetch = daily UrlFetch quota exhausted on the Apps Script side. @w0l4i is right — single-account daily quota is ~20K UrlFetch calls (often closer to 10K for accounts created from Iran).

Workaround:

1. Add multiple script_id entries (one per Google account) in config.json. mhrv-rs round-robins across them.
2. Each new script_id from a different Google account gets its own daily 20K bucket.
3. Set parallel_relay: 2 to fan out across two scripts per request — kills long-tail latency at the cost of 2× quota per non-cached request.

Quotas reset at 00:00 PT (Pacific Time). Closing as expected behavior — opening separate accounts is the documented workaround.