SoliSpirit v2ray-configs is a rolling list of proxy endpoints, not a client

A repository of configuration files and nothing else

The repository contains V2Ray configurations for several protocols, VMess, VLESS, SS and Trojan, and several countries, and the config links are updated every fifteen minutes. That is the entire product, and it is worth being precise about what that means. There is no client code, no proxy, no server and no build system in the tree. The top level listing shows directories for the protocols and for the countries, a directory for subscriptions, a file holding all configurations together, and five README files, one per language. What you download is a configuration document that describes a remote endpoint, and you then import that document into a V2Ray application of your choice. The value proposition in the repository's own framing is convenience, since a user who wants a working configuration does not have to run a server, generate credentials or negotiate a protocol, and the fifteen minute refresh means the links do not go stale the way a hand maintained list does.

Protocol files, country directories and one aggregate file

The organisation is simple and it is driven by the two decisions a user has to make. The first is the protocol, and there is one text file per protocol, each a raw file served directly from the repository, so a client can be pointed at the VMess, VLESS, SS or Trojan list directly. The second is the country, and the countries are organised as a directory with a subdirectory per country, where the configurations for that location live. On top of those two axes sits the aggregate file, a single text file with all available configurations, which is the simplest thing to fetch if you do not care about the filters. The trade-off in this layout is that the country dimension is nested inside the protocol dimension rather than the other way around, so a client that wants every endpoint in one country has to read the country directory rather than filter the aggregate. For a small number of users that does not matter. For anyone automating it, the directory naming is the part you have to understand before writing anything against it.

Subscription feeds exist for clients that prefer them

Alongside the raw files, the repository publishes subscriptions, described as updated V2Ray subscription links, kept in their own directory. The difference between the two is about who does the work. A raw text file is a snapshot that your client reads once, and if the entries in it have expired, the client has a list of dead endpoints. A subscription link is a URL that the client polls, so a refreshed list arrives on its own, which is why the repository pushes a fifteen minute cycle and why a subscription is the more useful form for a long lived client. The README's usage steps are correspondingly simple: choose a protocol, choose a country, download the config, and import it into your V2Ray application. The document that gets imported is what your client consumes, and the same file that a subscription serves is what you would otherwise download by hand, so the two routes produce the same artefact. If you are using a client that supports subscriptions, the subscription route is the one that keeps working.

Nothing here tells you who runs the other end

The repository is explicit that it is regularly updated with new proxies so that users always have access to current servers, and it does not claim anything else. There is no information about who operates the endpoints, where the servers are physically located beyond the country grouping, what a given endpoint logs, whether a configuration has been reviewed before publication, or what the uptime is. Those omissions are not necessarily a criticism of the maintainer, since the configurations are collected rather than operated, but they are the facts a user has to reason with. Using a configuration from this list means routing your traffic through a machine operated by someone else, with credentials and payload in the hands of whoever configured it, and the practical advice follows from that. Treat each entry as a single use test endpoint, keep real traffic on infrastructure you control, and never reuse a set of identifiers you have already used for anything that matters. The repository is at its most useful as a way to find a working endpoint for a client you are evaluating, and at its least useful as the foundation of a service.

Five README translations, no licence and no releases

The presentation details are minimal and worth noting for anyone who wants to contribute or reuse the files. The README is published in five languages, with separate files for Persian, Russian, Turkish, Chinese and the English original, which is an unusual level of localisation for a repository of this kind and tells you something about who the audience is. The tree has no build tooling, no package manifest and no test suite, which is consistent with a repository whose output is generated text rather than a program. The repository listing reports the licence as unknown, and there is no LICENSE file at the top level, so the terms for reusing the collected configurations are unclear and you would need to ask the maintainer. There are no GitHub releases either, so there is no version history of a given list, and the last push was on 2026-10-20, which given the fifteen minute refresh cycle means the branch itself is churning constantly. A repository whose history is a log of refreshes is also a repository where you cannot audit what changed, which is another reason to treat the contents as disposable.

Editorial conclusion

v2ray-configs suits someone who wants a ready made endpoint to test a V2Ray client against, or who wants a subscription feed that keeps itself current without any local tooling, since the refresh happens in the repository and the client does the rest. It is the wrong choice for a deployment that needs a known operator, a stable address, a service level or a privacy commitment, because the repository is a list of configurations collected from elsewhere and says nothing about who hosts them or what they log. Verify three things before you rely on any of these endpoints: who operates the server behind the address you picked, since the repository publishes no ownership or provenance information, whether the transport and protocol settings in the file match what your client supports, since the files are machine generated and the client is the final arbiter, and what the terms are, because the repository listing reports no licence identifier and the raw files are the only thing being published. The last push was on 2026-10-20 and the links are refreshed every fifteen minutes.

Frequently asked questions

Official sources

1. Issues
2. README
3. SoliSpirit/v2ray-configs on GitHub