explaingit

igareck/vpn-configs-for-russia

4,783Audience · generalComplexity · 2/5Setup · moderate

TLDR

A regularly updated collection of free VPN configurations verified to work inside Russia, using obfuscated protocols like VLESS and Shadowsocks to bypass Roskomnadzor blocking.

Mindmap

mindmap
  root((vpn-configs-russia))
    What it is
      VPN config collection
      Auto-tested configs
      Free and updated
    Protocols
      VLESS
      VMess
      Shadowsocks
      Hysteria2 and Trojan
    Clients
      v2rayN
      Streisand
      NekoBox Karing
    Features
      Split routing
      Auto-tested speeds
      Mobile safety tips
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Import a working VPN config into v2rayN or NekoBox to bypass Russian internet censorship.

USE CASE 2

Find active configs using obfuscated protocols like VLESS or Shadowsocks that evade Russian blocking.

USE CASE 3

Configure split routing so Russian sites go direct while everything else uses the VPN.

USE CASE 4

Apply client-side authentication settings to protect against Russian apps identifying your VPN server.

Getting it running

Difficulty · moderate Time to first run · 30min

Requires a compatible VPN client such as v2rayN, Streisand, or NekoBox to import and use the configs.

In plain English

This repository is a regularly updated collection of free VPN connection configurations that have been verified to work inside Russia, where the internet regulator Roskomnadzor blocks many standard VPN services. The project is primarily documented in Russian but also provides README files in English, Chinese, and Farsi. The configurations use protocols designed to disguise VPN traffic so it is harder to detect and block. These include VLESS, VMess, Shadowsocks, Hysteria2, Tuic, and Trojan. Ordinary VPN protocols like OpenVPN and WireGuard are noted in the README as no longer functional in Russia regardless of whether you have a paid subscription. Each configuration is formatted as a text subscription file that can be imported into a compatible VPN client, including v2rayN, Streisand, Throne, Karing, and NekoBox. The collection is filtered using lists of blocked and allowed IP ranges and domain names, which helps route Russian services directly without going through the VPN while routing everything else through it. Before each update is published, every configuration is automatically tested for actual connectivity from within Russia, including checks for speed, latency, and reachability. Configurations that are slow or non-functional are removed. The README notes that free public configurations tend to appear and disappear quickly, so the automated testing and frequent updates are central to the project's usefulness. The project also discusses a documented security concern for mobile users in Russia: certain Russian apps can potentially identify the proxy server address used by common VPN clients on the same device. The README recommends specific clients and settings that add authentication to the local proxy to mitigate this. Note: The README for this repository is provided mainly in Russian and the full content extends well beyond what was available in the excerpt shown here. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
How do I import a VPN subscription file from vpn-configs-for-russia into v2rayN to bypass restrictions?
Prompt 2
Which protocols in vpn-configs-for-russia work in Russia and why do OpenVPN and WireGuard no longer work?
Prompt 3
How do I configure split routing using these VPN configs so Russian domains bypass the VPN tunnel?
Prompt 4
What client settings does vpn-configs-for-russia recommend to prevent Russian apps from detecting my proxy server?
Open on GitHub → Explain another repo

← igareck on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.