mirror of
https://github.com/therealaleph/MasterHttpRelayVPN-RUST.git
synced 2026-05-18 07:44:47 +03:00
therealaleph
aba539395d
v1.7.4 added googlevideo.com to SNI_REWRITE_SUFFIXES on the theory that video chunks should bypass the Apps Script relay. Multiple users (#275 amirabbas117, #281 mrerf) reported total YouTube breakage on v1.7.4: SNI-rewriting googlevideo.com:443 to a GFE IP returned TLS handshake failure / wrong-cert error. Root cause: googlevideo.com is served by Google's separate "EVA" edge IPs, not the regular GFE IPs that the user's `google_ip` typically points at. The SNI-rewrite tunnel TLS handshake against a GFE IP for googlevideo.com SNI fails because the GFE IP doesn't hold a googlevideo.com cert. Pre-v1.7.4 behaviour restored: video chunks fall through to the Apps Script relay path. Slower but reliable on every GFE IP. The other v1.7.4 youtube_via_relay carve-out fixes (ytimg.com correctly stays on SNI rewrite, youtubei.googleapis.com correctly goes through relay) remain intact — those were a separate improvement and still correct. Future: if we want direct googlevideo.com routing, it needs a separate `eva_edge_ip` config knob — users can populate from their own EVA scan, defaulting to "use relay" if not configured. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 lines
2.5 KiB
Markdown
5 lines
2.5 KiB
Markdown
<!-- see docs/changelog/v1.1.0.md for the file format: Persian, then `---`, then English. -->
|
|
• Revert غلط v1.7.4 برای `googlevideo.com` ([#275](https://github.com/therealaleph/MasterHttpRelayVPN-RUST/issues/275)، [#281](https://github.com/therealaleph/MasterHttpRelayVPN-RUST/issues/281)): v1.7.4 تلاش کرد `googlevideo.com` رو به لیست SNI rewrite اضافه کنه به این تئوری که chunkهای ویدیو باید از Apps Script relay دور بزنن. **چندین کاربر گزارش دادن که v1.7.4 YouTube رو کاملاً شکست داد** — علت: `googlevideo.com` توسط edge IPهای جدا "EVA" گوگل serve میشه، نه GFE IP عادی که `google_ip` کاربر معمولاً به اون اشاره میکنه. SNI-rewrite کردن `googlevideo.com:443` به یه GFE IP باعث TLS handshake failure یا wrong-cert error برای اون کاربرها شد. **رفتار قبل از v1.7.4 برگشته** (chunkهای ویدیو از مسیر Apps Script relay میرن — کندتر ولی روی هر GFE IP قابل اعتماد). تغییرات `youtube_via_relay` carve-out از v1.7.4 (که `ytimg.com` رو از relay پاک کرد) دست نخورده — اون regression جدا بود و درست شده باقی مونده. اگه کاربری در آینده EVA edge IP خودش رو پیکربندی بکنه، یه knob مجزا اضافه میکنیم.
|
|
---
|
|
• Revert v1.7.4 `googlevideo.com` SNI rewrite ([#275](https://github.com/therealaleph/MasterHttpRelayVPN-RUST/issues/275), [#281](https://github.com/therealaleph/MasterHttpRelayVPN-RUST/issues/281)): v1.7.4 added `googlevideo.com` to the SNI rewrite list on the theory that video chunks should bypass the Apps Script relay. **Multiple users reported v1.7.4 broke YouTube entirely** — root cause: `googlevideo.com` is served by Google's separate "EVA" edge IPs, not the regular GFE IPs that `google_ip` typically points at. SNI-rewriting `googlevideo.com:443` to a GFE IP got TLS handshake failures or wrong-cert errors for those users. **Pre-v1.7.4 behaviour is restored** (video chunks go via the Apps Script relay path — slower but reliable on every GFE IP). The other v1.7.4 `youtube_via_relay` carve-out changes (which removed `ytimg.com` from the carve-out) are intact — those were a separate fix that's still correct. If a user ever wants direct googlevideo.com routing, that needs a separate config knob letting them specify their EVA edge IP independently.
|