به Univista خوش آمدید - خوشحالیم که اینجا هستید. اگر چیزی نامشخص است، Help را باز کنید یا از طریق پشتیبانی در این سایت با ما تماس بگیرید و ما به شما کمک خواهیم کرد تا با هم ارتباط برقرار کنید.
چهکار کنیم وقتی گیتهاب در روسیه باز نمیشود / کند شده: توضیح صادقانه (روسکومنادزور رسماً گیتهاب را مسدود نکرده و در فهرست ممنوعه نیست، اما از مه ۲۰۲۶ دسترسی «بهطور زیرساختی خفه» میشود، بهعلاوهٔ ۱۳۰+ صفحهٔ جداگانه که نقطهای مسدود شدهاند؛ این مسدودسازی کل سایت نیست) و راهی مطمئنتر برای ورود (کلاینت VLESS+Reality)
بهروزرسانی
Diagram: GitHub is not formally blocked in Russia (RKN denies it, not in the banned registry), but since May 2026 access is 'infrastructure-throttled' — the homepage opens while git clone / release / raw-file downloads often fail; git CLI / SSH don't go through the browser, so you need a system-level (TUN) VLESS+Reality client that routes the whole device through a clean foreign IP
First, the honest part: what actually happened to GitHub in Russia (not a site-wide block, but 'infrastructure throttling')
In practice developers see: GitHub's homepage opens, but git clone / git push stalls and downloading a release archive or raw file fails repeatedly. The honest distinction: GitHub was not formally blocked by RKN — officials explicitly deny blocking it and it's not in the banned registry; but since May 2026 access to GitHub has been systematically 'infrastructure-throttled' (anomalous / failed connections up from ~4% to 10-16%), the same slow-strangle tactic used earlier on Telegram and YouTube (see "YouTube throttled in Russia"). On top of that, 130+ individual pages / repos have been court- or agency-blocked (blocked by content, not the whole site). So the state is "throttling + per-page blocks", not a blacklisting of github.com as a whole.
Why 'the homepage opens but git clone / release downloads fail'
The key is that GitHub's different traffic uses different domains and infrastructure: the web lives on github.com, but cloning / downloads go through a CDN and object storage — codeload.github.com (release / source archives), objects.githubusercontent.com, raw.githubusercontent.com (raw files / LFS). Throttling often targets these download / CDN channels specifically, so you see "the homepage opens, but cloning a big repo or downloading a release stalls". Your git config isn't broken — the download path is being deliberately slowed / disrupted.
Why a free VPN browser extension can't save git
The first instinct is a free VPN browser extension. But for GitHub that especially doesn't work, for a hard reason: git clone / push / pull, SSH, and downloads from IDEs / package managers (npm, pip, go get, cargo) don't go through the browser — they're system processes connecting directly. A browser extension only protects traffic in the browser tab; your git clone in the terminal still goes over the real network and is still throttled. On top of that, free extensions / proxies use public shared IP ranges that are congested and drop, so big clones and large downloads suffer first; on privacy, a free extension can see all your browser traffic — especially dangerous for developers who log into private repos and paste tokens.
The key point: to keep GitHub stable, cover the whole device (TUN mode)
To route git, SSH, package managers and the web abroad at once, the channel must be system-level — that is, TUN mode (which captures the whole device's traffic into the tunnel), not a browser-only extension and not just one app's proxy setting (see "TUN vs system proxy"). The good news: GitHub / Git is relatively tolerant of foreign datacenter IPs (unlike Netflix, which actively bans them), so as long as the channel is stable with enough bandwidth, cloning big repos and downloading releases usually goes smoothly. As a bonus, a system-level solution also covers ChatGPT, Docker Hub, npm, Hugging Face and the like that you may also need.
A more reliable alternative: a VLESS + Reality client
VLESS is a lean transport protocol and Reality is its TLS camouflage layer, disguising your traffic as ordinary HTTPS to a real public website. This matters especially for anti-throttling: throttling requires the censorship gear to "identify" the traffic as GitHub-bound, and Reality makes it unrecognizable, so it can't be selectively slowed — the same principle as beating YouTube throttling. Running VLESS+Reality in a real client (sing-box / v2rayN / Shadowrocket) in TUN mode is system-level: git / SSH / CDN downloads / web all go through the tunnel; a dedicated node makes cloning big repos steadier with fewer drops; and it's harder to auto-throttle than a free proxy with a public entry point. The trade-off is you need a subscription and a client. Three honest caveats: first, a specific page / repo blocked by content may not open even on a new IP if the block is content- rather than IP-based; second, GitHub's restrictions on specific US-sanctioned accounts / entities under export controls are account-level and a tunnel can't lift them; third, no method guarantees it works forever — during a regional shutdown no foreign channel connects.
How to use GitHub reliably in Russia: concrete steps
Copy your subscription link from the dashboard (prefer VLESS+Reality nodes for Russian conditions).
Install a mature client: Shadowrocket on iOS, sing-box or v2rayN on Android / desktop, and import the subscription URL (don't add single nodes by hand).
Be sure to enable TUN / 'virtual NIC' mode (not just a system proxy), so that git, SSH and package managers in the terminal go through the tunnel.
Pick a stable node in a non-Russian region (low latency, low loss) and run a latency test; cloning big repos is sensitive to bandwidth / loss, so favour a stable line.
Use Rule mode: send Russian banking / government (Gosuslugi) apps direct (they reject foreign IPs) and route github.com, *.githubusercontent.com, codeload.github.com through the tunnel.
Verify: git clone a big repo and download a release archive to confirm they no longer stall. SSH users can use ssh.github.com:443 as a fallback port.
Honest expectations
GitHub is unstable in Russia mainly due to infrastructure throttling + some individually blocked pages, not RKN blocking the whole site; a stable foreign IP whose traffic is disguised (Reality) restores reliable clone / push / download.
git / SSH / package managers don't go through the browser — you must use a system-level (TUN) channel; a browser VPN extension can't fix git in the terminal.
A specific page / repo blocked by content may not open on a new IP; GitHub's restrictions on US-sanctioned accounts / entities are account-level and a tunnel can't solve them.
During a regional shutdown or a "sovereign internet" drill, any foreign channel (including VLESS) may fail to connect and GitHub won't work either — that's unrelated to the protocol.
Comply with local laws and third-party terms of service; this article is a technical tutorial only, responsibility for security and compliance rests with the user, and no guarantee can be made about the long-term availability of third-party services (including GitHub).
سؤالات متداول
Is GitHub blocked by RKN in Russia?
Strictly, not a site-wide block. RKN officially denies blocking GitHub and it's not in the banned registry; but since May 2026 access has been systematically 'infrastructure-throttled' (anomalous connections up to 10-16%), plus 130+ individual pages / repos have been ordered blocked. This is 'throttling + per-page blocks', not blacklisting the whole site — the same slow-strangle tactic used earlier on Telegram / YouTube. Running VLESS+Reality in a system-level client (TUN mode) disguises the traffic as ordinary HTTPS so the censorship gear can't identify and selectively slow it, and clone / downloads usually become stable again.
Why does GitHub's homepage open but git clone always stalls?
Because the web is on github.com while cloning / downloads go through a CDN and object storage (codeload.github.com, objects.githubusercontent.com, raw.githubusercontent.com). Throttling often targets those download channels specifically, so 'the homepage opens but cloning a big repo or downloading a release stalls'. Your git config isn't broken — the download path is being deliberately slowed.
Can't I just install a free VPN browser extension?
It's basically useless for GitHub. git clone / push / SSH, and downloads from npm / pip / go get / cargo don't go through the browser — they're system processes connecting directly. A browser extension only protects the browser tab; your git in the terminal still goes over the real network and is still throttled. To route git abroad too, you must use a system-level (TUN) channel that captures the whole device's traffic.
With a foreign IP, will an individually blocked repo open too?
Not necessarily. If a page / repo is blocked by content specifically, a new IP may not restore it; that's separate from site-wide throttling. Also, GitHub's restrictions on specific US-sanctioned accounts / entities under export controls are account-level and a tunnel can't solve them. A system-level VLESS+Reality mainly addresses the 'infrastructure throttling' category, restoring overall access stability.
کانال تلگرام Univista
آخرین کانفیگهای سالم، وضعیت سرورها و آموزش رفع اشکال در کانال ما.
