You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository contains a collection of V2Ray configurations, aggregated from various public sources. The configs are automatically categorized by protocol and port using a Python script.
Note
If you find this repository helpful, please consider giving it a star ⭐. Your support is greatly appreciated!
For a complete list of all protocols and ports, browse the sub and detailed directories.
📚 Sources & Summary
Sources
Source
Fetched Lines
ConfigForge-V2Ray
1007
Epodonios
6872
Hamedp-71
1470
Rayan-Config
47
barry-far
6871
kobabi
350
mahdibland
4032
yebekhe
305
Summary
Metric
Value
Total Fetched
20954
Unique Configs
18518
Duplicates Removed
2436
Published (passed TCP check)
12344
🟢 Live Configs (Tested)
Every run, configs go through a liveness pipeline before top100/clash.yaml are built:
TCP check (3 rounds, directly from the runner) — drops configs whose port isn't even open.
Real proxy test (via a WireGuard tunnel, so the target servers see a VPN exit IP instead of GitHub's — multiple WireGuard configs are supported with automatic failover) — actually connects through each config with xray-knife and confirms it can reach the internet.
The fastest configs that passed both stages become top100.txt (up to 100), and a ready-to-import clash.yaml is built from the same set.
If the WireGuard tunnel is unavailable for a run, the pipeline falls back to TCP-only ranking automatically (noted in the table below) instead of failing the whole workflow.
Method: Real proxy test via WireGuard tunnel proton-mx8 (xray-knife)