# Epodonios/v2ray-configs: a subscription feed of public proxy configs, refreshed by GitHub Actions > The repository is not a client and not a server. It is a Python-driven pipeline that republishes thousands of vless, vmess, trojan and shadowsocks endpoints as plain text subscription files, and the judgement depends entirely on what you plan to do with untrusted endpoints. **Epodonios/v2ray-configs** — Free vless-vmess-shadowsocks-trojan-xray-V2ray Configs Updating Every 5 minutes. - Repository: https://github.com/Epodonios/v2ray-configs - Stars: 3,251 · Forks: 444 - Language: Python - License: GPL-3.0 - Published: 2026-08-08 · Updated: 2026-08-18 · Language: en - Canonical page: https://hysenlabs.com/projects/epodonios-v2ray-configs ## What the repository actually ships: text files, not software The name suggests a tool. The repository is a distribution channel. Its top level holds All_Configs_Sub.txt, All_Configs_base64_Sub.txt, a Base64/ directory, a Files/ directory, a Splitted-By-Protocol/ directory, and fourteen files named Sub1.txt through Sub14.txt. The README describes the contents as "thousands of free V2Ray configuration files" covering VMess, VLess, Trojan, TUIC, Shadowsocks and ShadowsocksR, and states the collection updates every 5 minutes. Python is listed as the primary language, which points at the scanner and writer scripts behind those files rather than at anything a user runs. Who this is for: someone who already has a client such as v2rayNG, Hiddify Next, Nekoray or v2rayN installed and wants a subscription URL to paste into it. It is not for someone who wants to run their own server, and it is not for someone who needs to know who operates the endpoint on the other side. The README never identifies the operators. That absence is the whole story of this project. ## How the pipeline works: a scanner writes protocol-split files The layout implies the data flow. A scanner collects candidate endpoints, tests them, and writes the survivors into the repository, from which GitHub serves them as raw files. The output is deliberately duplicated into several shapes so that different clients can consume it. The combined file is one long list. The base64 variant is the same list encoded, because many clients expect a base64 subscription body. Splitted-By-Protocol/ breaks the pool into vless.txt, vmess.txt, ss.txt, ssr.txt and trojan.txt, which matters when your client handles one protocol family better than another. The Sub1.txt through Sub14.txt files are 250-config packs, and the README's own table links them through raw.githubusercontent.com rather than through the /raw/main/ path used for the combined files, so the two link styles are not interchangeable if you script the download. The recent release tag is named scanner1.011 and carries the same timestamp as the last push, 2025-07-16T07:43:22Z. That is consistent with a scanner being versioned alongside the data it produces. What the repository does not document is the test the scanner applies before a config is published, how many candidates it rejects, or whether a config that passed once is re-tested later. ## Adding the subscription to a client There is nothing to compile. You choose a URL and hand it to a client. For a desktop or Android client that accepts a subscription link, the combined plain-text file is the simplest starting point: ```text https://github.com/Epodonios/v2ray-configs/raw/main/All_Configs_Sub.txt ``` If your client expects a base64 body instead of a plain list, use the encoded variant, which the README lists alongside the first: ```text https://github.com/Epodonios/v2ray-configs/raw/main/All_Configs_base64_Sub.txt ``` If you want only one protocol, the split files are shorter and easier to inspect. The README gives the vless file as: ```text https://github.com/Epodonios/v2ray-configs/raw/main/Splitted-By-Protocol/vless.txt ``` The README's four-step instructions are: copy a subscription link, open the client, paste it under Subscription Settings, and press Update. It also suggests enabling auto-update in the client so the list refreshes. On Windows the README points at Hiddify Next, Nekoray and v2rayN; on Android it recommends v2rayNG; on iOS it lists Fair VPN and Streisand. The same README promotes MEMENTO, a separate Windows application with xray-core bundled, for importing subscription links and exporting to Clash, Surge and Sing-Box formats. MEMENTO lives in its own repository and is not part of this one. ## Every endpoint in the pool belongs to someone you cannot identify This is the limitation that decides whether the project is usable for you. A subscription file is a list of servers run by unknown parties. The README does not state who operates them, what jurisdiction they sit in, whether they log traffic, or how long any individual endpoint has been alive. A client that rotates through the pool will eventually route your traffic through a machine chosen by a scanner script you have not read. The five-minute update cadence cuts both ways. It means dead entries get replaced quickly, and it also means the set of servers you trust changes constantly without your involvement. If you enable auto-update, you are accepting new operators on a schedule. The repository also documents no verification step, no signing of the published files, and no way to confirm that a config in All_Configs_Sub.txt was tested at the moment you downloaded it. The README does not document rollback to a previous snapshot either, so there is no supported path back to yesterday's list. It is the wrong tool for anything that needs a stable exit address: a server you administer remotely, an account that flags new login locations, or a session that must survive a mid-transfer reconnect. For those, a self-hosted endpoint is the only configuration where you control the variable that matters. ## The alternative you are actually choosing between The realistic alternative is running your own Xray or V2Ray server on a VPS and generating a single config you own. The difference in approach is not the protocol, since both ends speak vless or vmess. It is the source of the endpoint and the update model. A self-hosted setup has one config, no subscription refresh, no scanner deciding what you connect to, and a monthly bill. This repository has thousands of configs, no bill, and a rotating cast of operators. A second alternative is a commercial subscription service, which the search data shows people look for under the phrase "V2ray config buy". That model replaces unknown operators with a vendor you can at least name, and replaces the free price with a recurring one. It is a different trade, not a better one automatically, but it is the trade most people are making when they decide this repository is not enough. What this project does better than either is breadth for testing. If you are checking whether a client parses a given protocol, or you want a large sample of real-world config strings to feed a parser, the pool is convenient. That is a development use, not a daily-connection use. ## Licence, maintenance and the cost of staying current The repository carries GPL-3.0. That governs the code in the repository, not the endpoints the files point at, and it says nothing about the terms under which any listed server may be used. The README's own badge links to an MIT licence page, which conflicts with the GPL-3.0 identifier attached to the repository. Treat the discrepancy as unresolved rather than picking the one you prefer. If you plan to redistribute the files or wrap the scanner in your own product, resolve that question first; this is a description of the conflict, not legal advice. The maintenance picture is concrete. The last push was on 2025-07-16, and the only release listed, scanner1.011, carries the same timestamp. The README's claim of a five-minute cycle describes the workflow configuration, and the repository does not document whether that workflow is still running or has been disabled. Anyone depending on fresh entries should verify the file's contents rather than the claim. Upgrade cost is close to zero in the usual sense, because there is no package to bump. The ongoing cost is attention: a client pointed at a subscription URL will silently change the servers it uses, and the only way to notice is to look at what it connected to. ## Conclusion Adopt it if you need a bulk pool of endpoints for a client that supports subscriptions and you accept that every entry is a stranger's server. Do not adopt it if you need a guarantee of uptime, a known operator, or a config you can attribute to someone accountable. Before pointing a client at it, fetch All_Configs_Sub.txt and confirm the file still parses, because the last push to this repository was on 2025-07-16 and the five-minute update claim describes the workflow, not a promise about today's file. ## FAQ ### How do I get a config for V2Ray from Epodonios/v2ray-configs? Copy one of the subscription links from the README, such as All_Configs_Sub.txt or the base64 variant, then paste it into your client's Subscription Settings and press Update. The README lists v2rayNG for Android and Hiddify Next, Nekoray or v2rayN for Windows and Linux. ### Is the V2Ray config from Epodonios/v2ray-configs safe? The README does not identify who operates the servers in the pool, what they log, or where they are located, so the safety of any individual endpoint cannot be established from the repository. The files are published without a documented verification or signing step. ### Is there a free V2Ray config available in this repository? Yes. The README describes the collection as free and states that no registration is required, and the subscription links are served as plain files from the repository. ### Can V2Ray be detected when using configs from Epodonios/v2ray-configs? The README does not discuss detection or traffic analysis for the published configs, so the repository offers no answer here. The only related mechanism it mentions is Iran Mode (Domain Fronting) in the separate MEMENTO application, which the README says hides traffic behind trusted domains. ### how to use v2ray configs on pc The README's steps are the same on desktop: copy a subscription link, open the client, paste it under Subscription Settings, and press Update. For Windows it points at Hiddify Next, Nekoray and v2rayN, and it suggests enabling auto-update in the client. ### is v2ray configs safe The repository publishes endpoints run by unidentified operators and does not document logging, jurisdiction or a verification step, so it cannot support a safety claim about the pool. The README also does not document rollback to an earlier version of the list. ## Sources - [Official README](https://github.com/Epodonios/v2ray-configs#readme) - [Project repository](https://github.com/Epodonios/v2ray-configs) - [Release notes](https://github.com/Epodonios/v2ray-configs/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/epodonios-v2ray-configs