# 233boy/v2ray: a V2Ray install and management script for Linux servers

> The 233boy/v2ray script installs V2Ray on a server and manages multiple configurations through short commands like v2ray add and v2ray change. It is a server-side tool, not a Windows, Android or macOS client.

**233boy/v2ray** — Project brief: V2Ray & . 1 V2Ray V2Ray : v2ray help.

- Repository: https://github.com/233boy/v2ray
- Website: https://233boy.com/v2ray/v2ray-script/
- Stars: 29,685 · Forks: 16,594
- Language: Shell
- License: GPL-3.0
- Published: 2026-08-08 · Updated: 2026-08-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/233boy-v2ray

## What 233boy/v2ray actually solves, and for whom

V2Ray itself is configured through JSON files. Editing those files by hand to add a protocol, change a port or issue a new UUID is slow and easy to get wrong, especially once several configurations have to run side by side. The 233boy/v2ray script exists to remove that editing step. The README describes it as a one-click install and management script, and states that the design goal is efficiency, speed and ease of use, built around running multiple configurations at the same time. The author says the script was written for his own usage needs and that the four everyday operations, add, change, view and delete, were specifically optimized. The README claims adding one configuration takes under a second. That is the author's claim, not a measurement anyone can verify from the repository, and it depends on the machine it runs on. The audience is narrow and specific: someone with a Linux server who wants to run V2Ray on it and does not want to hand-write JSON. It is not a client. Nothing in the README describes a Windows, Android or macOS application, and the repository layout is a shell script plus an install.sh and a src directory.

## How the script is put together

The repository has five top-level entries that matter here: install.sh, v2ray.sh, src/, README.md and LICENSE. install.sh is the entry point a new user runs; v2ray.sh is the command that stays on the machine afterwards. The README shows the help output for v4.21, and it lists the commands in two groups. The basic group covers version, ip and get-port, where get-port returns an available port. The general group covers add, change, del, info, qr and url, each taking an optional name argument. That command surface is the whole interface: the script writes V2Ray configuration, and the user drives it through these short verbs rather than through a config file. The README also lists capabilities that go beyond adding a config, including automated TLS, blocking BitTorrent, blocking Chinese IPs, one-click BBR, changing the camouflage website, and changing a port, UUID, password, domain, path, encryption method, SNI or dynamic port. It states the script is compatible with the V2Ray command and supports all common protocols, with one-click add for Shadowsocks, VMess over TCP, mKCP or QUIC, VMess over WS, H2 or gRPC with TLS, VLESS over WS, H2 or gRPC with TLS, and Trojan over WS, H2 or gRPC with TLS. The README does not document how the script stores its own state, and it does not describe a rollback path for a change.

## Installing it and adding a first configuration

The README points to two wiki pages rather than embedding the commands: one titled as a V2Ray one-click install script and one as a detailed illustrated setup tutorial. The repository also ships install.sh at the top level, which is the file a new user is expected to run. The README does not print the exact install command, so the honest starting point is the install.sh file in the repository and the wiki page the README links to.

Once the script is on the machine, the README gives this help output as the reference for what to type. Running the command with no useful arguments prints the usage block, which is the fastest way to confirm the script installed correctly and to see the version string.

```bash
v2ray help
```

The README shows the header line of that output as `V2Ray script v4.21 by 233boy`, followed by the basic and general command groups. If you see that block, the command is on your PATH and working.

Adding a configuration is the operation the README spends the most space on. The add command takes a protocol and then arguments, or the keyword auto. The auto keyword is the part worth knowing about, because it lets the script fill in the details instead of you supplying them.

```bash
v2ray add vless auto
```

After that, the info and url commands are how you read back what was created. The url command prints the URL form of a configuration, which is what you paste into a client.

```bash
v2ray info
v2ray url
```

The README does not state what the script prints on a failed add, so treat the absence of a configuration in the info output as the signal that something did not work.

## Where the script stops being the right tool

The most common mismatch is treating this as a client. The search terms around this project include V2Ray Windows, v2ray android, v2ray apk, v2ray for mac and v2ray for pc. None of those are served by this repository. The README describes a server-side installer and manager in Shell, and the repository contains no client code. Someone who wants to connect a laptop or phone needs a separate client application and a configuration produced by this script, not the script itself.

A second limit is that the script owns the configuration files. Because add, change and del rewrite configuration through the script, hand edits to the generated JSON sit outside that model, and the README does not document how the script behaves when the files have been edited manually. The README also does not document rollback for a change, or what happens to existing configurations when the script updates. The README lists one-click BBR and Chinese IP blocking as features, but blocking Chinese IPs on a server you intend to reach from China is a configuration choice that can lock you out of your own service; the README presents it as a feature without discussing that consequence. Finally, the last push to the repository was on 2026-01-15, with release v4.27 on the same date. That is roughly eight months before today, so this is not a project with recent activity, and anyone adopting it should read the source before depending on it.

## How it compares with installing V2Ray by hand

The real alternative is the upstream V2Ray project and its own configuration files, installed manually. The difference is not features, since the script drives the same V2Ray underneath and the README states it is compatible with the V2Ray command. The difference is who owns the configuration. With upstream V2Ray, you write the JSON, you decide the file layout, and any tool that reads JSON can inspect or generate it. With 233boy/v2ray, the script generates and rewrites that JSON for you, and the interface becomes the verbs in the help output. That trade is favorable when you add and remove configurations often and want each operation to be a single command. It is unfavorable when you need configuration that the script's options do not express, because you are then working against the tool rather than with it. A second alternative is to keep V2Ray but manage it with a configuration management system you already run, which keeps the JSON in version control. The script does not appear to target that workflow; the README presents the command line as the interface, and does not mention configuration management integration.

## Maintenance, updates and the licence

The repository is not archived, but the last push was on 2026-01-15, and the most recent release listed is v4.27 on that same date. The two releases before it were v4.26 on 2025-07-30 and v4.25 on 2025-06-25. That is a gap of several months between releases, with nothing since January. The practical consequence is that fixes and new protocol support arrive slowly, and a user who needs a change should expect to read the Shell source rather than wait. Upgrade cost is hard to judge from the README, which does not document an upgrade command or describe how an upgrade treats existing configurations. Before upgrading, the safe assumption is that configurations created by the script live in files the script manages, so back up whatever the script wrote before running anything that replaces it.

The project is licensed GPL-3.0, and the LICENSE file is at the top level. GPL-3.0 is a copyleft licence: if you distribute a modified version of this script, the licence's terms apply to that distribution. Running the script on your own server is not distribution, so the licence does not change how you use it privately. This is a description of the licence identifier in the repository, not legal advice; if you plan to redistribute a modified copy, read the LICENSE file and get proper advice.

## Conclusion

Adopt 233boy/v2ray if you run a Linux server and want V2Ray configs added, changed and removed with one command per operation. Do not adopt it if what you actually need is a Windows, Android or macOS client, since this project is a server-side installer and manager. Before relying on it, read v2ray.sh and install.sh in the repository to see what the script writes to the system, and check the wiki pages the README links to for the install and setup steps.

## FAQ

### Is 233boy/v2ray a client for Windows, Android or macOS?

No. The repository is a Shell script that installs and manages V2Ray on a server, with install.sh and v2ray.sh at the top level. Clients for Windows, Android or macOS are separate applications that consume the configuration this script produces.

### How do I install 233boy/v2ray?

The README does not print the install command itself. It links to a wiki page titled as a V2Ray one-click install script and points to install.sh in the repository as the entry point.

### How do I add a configuration with 233boy/v2ray?

Use the add command with a protocol and either arguments or the keyword auto, for example v2ray add vless auto. The README states that adding a configuration takes under a second, though that is the author's claim.

### How do I use 233boy/v2ray on Linux?

Run install.sh to install the script, then drive it through the commands in the help output: add, change, del, info, qr and url, plus version, ip and get-port. The README links to a wiki page with the detailed setup steps.

## Sources

- [Official documentation](https://233boy.com/v2ray/v2ray-script/)
- [Official README](https://github.com/233boy/v2ray#readme)
- [Project repository](https://github.com/233boy/v2ray)
- [Release notes](https://github.com/233boy/v2ray/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/233boy-v2ray