v2ray-core 配置模板

Benyamin Jafari 4cc09a4977 Update nginx.conf (#90) 2 years ago
Shadowsocks-TCP 6658e375ca style: fix formation (#75) 4 years ago
Shadowsocks-Websocket-Web-TLS 084bb78a2f Add Shadowsocks gRPC Web TLS and Update Shadowsocks WSS Web TLS (#74) 4 years ago
Shadowsocks-gRPC-Web-TLS 084bb78a2f Add Shadowsocks gRPC Web TLS and Update Shadowsocks WSS Web TLS (#74) 4 years ago
Socks5-TLS 04017a8c67 refine options 4 years ago
Trojan-TCP-TLS (minimal) 67aa8587a5 rename for clone success 5 years ago
VLESS-H2C-Caddy2 c0e88098f6 Update client.json 5 years ago
VLESS-TCP 4cc09a4977 Update nginx.conf (#90) 2 years ago
VLESS-TCP-TLS 01e2b0eab7 fix direct outboundTag 5 years ago
VLESS-TCP-TLS (maximal by rprx) 36c819489b Use relative links 5 years ago
VLESS-TCP-TLS (minimal by rprx) 36c819489b Use relative links 5 years ago
VLESS-TCP-TLS-WS (recommended) 36c819489b Use relative links 5 years ago
VLESS-TCP-TLS-proxy protocol 01e2b0eab7 fix direct outboundTag 5 years ago
VLESS-gRPC-TLS 14662e8461 re-format and fix vless settings (#69) 4 years ago
VLESS-mKCPSeed 04017a8c67 refine options 4 years ago
VMess-HTTP d71ca2f42a fix rules outboundTag 5 years ago
VMess-HTTP2 d71ca2f42a fix rules outboundTag 5 years ago
VMess-TCP d71ca2f42a fix rules outboundTag 5 years ago
VMess-TCP-TLS d71ca2f42a fix rules outboundTag 5 years ago
VMess-Websocket d71ca2f42a fix rules outboundTag 5 years ago
VMess-Websocket-TLS d71ca2f42a fix rules outboundTag 5 years ago
VMess-mKCPSeed 37e6fc3dc2 update vmess mkcp 4 years ago
how-to-choose 691db54d11 add English version how to choose a v2ray plan 2 years ago
.editorconfig 7ad88b8f38 add editconfig and use 4 space 5 years ago
.gitignore b265293db5 update readme 5 years ago
README.ENG.md cd1bc29a96 add English translate Readme.md (#87) 2 years ago
README.md 5d2309feb5 Update README.md (#89) 2 years ago

README.ENG.md

#v2ray-examples

Here are some V2Ray configuration examples for reference, the content keeps pace with the times, automation scripts, etc. Please do not pull the configuration from here.

Thanks to KiriKira, the author of vTemplate, Yuluowusheng and all the developers of Project V.

Contribution Guidelines

You are welcome to make a template for your own configuration and submit a PR.

Templates should adhere to the following standards:

  • use 4 spaces for indentation
  • Square (curly) brackets do not wrap
  • Unneeded fields should be removed
  • log section only leaves loglevel
  • For outbounds, client side should have proxy and direct, server side should have direct and block
  • Unless it is a template for a specific scenario, geoip:private should be routed to direct outbound (server configuration routes to block outbound)
  • DNS should not appear in config files unless it is a template for a specific scenario
  • uuid should be left blank and filled by the user.
  • domainStrategy in routing remains the default, which is AsIs.

Examples

{
    "log": {
        "loglevel": "warning"
    },
    "routing": {},
    "inbounds": [],
    "outbounds": []
}

client

{
    "log": {
        "loglevel": "warning"
    },
    "routing": {
        "domainStrategy": "AsIs",
        "rules": [
            {
                "ip": [
                    "geoip:private"
                ],
                "outboundTag": "direct",
                "type": "field"
            }
        ]
    },
    "inbounds": [
        {
            "port": 1080,
            "protocol": "socks",
            "settings": {
                "auth": "noauth",
                "udp": true
            },
            "tag": "socks"
        }
    ],
    "outbounds": [
        {
            "protocol": "vmess",
            "settings": {
                "vnext": [
                    {
                        "users": [
                            {
                                "id": ""
                            }
                        ],
                        "port": 1234,
                        "address": "Your_IP_Address"
                    }
                ]
            }
        },
        {
            "protocol": "freedom",
            "tag": "direct"
        }
    ]
}

Server

{
    "log": {
        "loglevel": "warning"
    },
    "routing": {
        "domainStrategy": "AsIs",
        "rules": [
            {
                "ip": [
                    "geoip:private"
                ],
                "outboundTag": "blocked",
                "type": "field"
            }
        ]
    },
    "inbounds": [
        {
            "port": 1234,
            "protocol": "vmess",
            "settings": {
                "clients": [
                    {
                        "id": "",
                    }
                ]
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "freedom"
        },
        {
            "protocol": "blackhole",
            "tag": "blocked"
        }
    ]
}

How to choose the configuration that suits you:

Additional Notes:
Although Websocket+TLS+Web may be regarded as the best solution at this stage, it is definitely not a solution recommended for novices to try as soon as they come up, let alone the only usage of V2Ray.
At the same time, you should understand that the network conditions in each region are different (mainly referring to the QoS level of different protocols), you can try all the configurations to find the most suitable one for you, try to ask as little as possible, and it is best not to ask "why do I V2Ray so slow?" Questions like that.

at last

have fun!