sing-box-yg: five proxy protocols from one piped install, and the Serv00 gamble hiding behind the second script

Two scripts, two hosts, two different protocol counts

This repository is not the sing-box core. It is a pair of one-command shell scripts. sb.sh covers a VPS you own and installs five coexisting protocols: Vless-reality-vision, Vmess-ws(tls)/Argo, Hysteria-2, Tuic-v5 and Anytls. serv00.sh covers a different kind of host, Serv00 or Hostuno, and installs three: vless-reality, vmess-ws(argo) and hysteria2. The two are not interchangeable, and the gap between them is not only the protocol count. On the VPS side the script accepts pure IPV6, pure IPV4 and dual stack servers, runs on amd and arm, works on alpine, and the README pushes the newest Ubuntu as the base to use. Node output differs too: the Serv00 build aggregates 22 nodes, while the VPS build writes a config file that a tutorial title says works across SFA, SFI and SFW clients.

The menu can be pre-answered by piping digits into a shell function

On a VPS the install is a single command, and either transport reaches the same file on the main branch:

bash <(wget -qO- https://raw.githubusercontent.com/yonggekkk/sing-box-yg/main/sb.sh)

bash <(curl -Ls https://raw.githubusercontent.com/yonggekkk/sing-box-yg/main/sb.sh)

That first run registers a shell shortcut named sb, and four pre-answered menu paths come with it, for the local IP subscription, a temporary Argo tunnel, a fixed Argo tunnel and domain routing:

printf '3\n8\n1\n订阅密码' | sb

printf '3\n3\n1\n1' | sb

printf '3\n3\n2\n1\n固定密钥\n固定域名' | sb

printf '5\n2\n1\n后缀域名1 后缀域名2' | sb

The digits are positional, and the fixed Argo path consumes two more values, a fixed key and a fixed domain. The subscription password arrives on a command line rather than at a hidden prompt, so it stays in your shell history.

Dropping the certificate leaves domain routing with nothing to attach to

The beginner path removes the certificate from setup entirely: no domain, no certificate, three Enters and the install is finished. The repository summary still advertises dual certificate switching between self-signed and acme as one of three headline capabilities, so the certificate step exists, it is simply optional. Domain routing is driven by suffix domains, supplied on stdin as '后缀域名1 后缀域名2'.

Argo tunnels come in states, and none of them can be listed

Argo tunnels arrive in two shapes across the two scripts. On the VPS side the quick path opens a temporary tunnel with nothing but digit choices after it, while the fixed variant demands a key and a domain, which is the difference between a tunnel that dies with the process and one that keeps a stable address. The Serv00 side states the options more precisely in a single line: reset the temporary tunnel, keep using the fixed tunnel from the previous run, or change the fixed tunnel's domain or token. What none of that gives you is an inventory. No documented command lists the tunnels currently bound to the account, or shows which node points at which one..

The free Serv00 account is where the risk sits, and the README says so

The Serv00 half carries its own account risk, stated plainly: using a proxy script on free Serv00 runs the risk of the account being banned, while the paid Hostuno is not affected. The same block warns against mixing this script with other Serv00 scripts, which matters because the implementation is assembled from two named sources, 老王eooce's sing-box script and frankiejun's serv00-play. A second script writing the same account is exactly where that collision happens, and the cost lands on your login rather than on your config. Install is one command:

bash <(curl -Ls https://raw.githubusercontent.com/yonggekkk/sing-box-yg/main/serv00.sh)

Outside the SSH session, the repository keeps its keepalive logic in files: serv00keep.sh, workers_keep.js, kp.sh and serv00.yml all sit in the top-level tree, and the tutorial titles refer to cron-based and webpage-based keepalive that you pick between. Treat every one of those as a second writer to the same account.

The 22 shared nodes point at edge addresses nobody here verifies

Shared nodes are where the convenience ends and the ceiling starts. The Serv00 build advertises aggregated universal sharing up to 22 nodes: three IPs for each of the three protocols, Argo covering 13 port nodes, with a non-expiring preferred IP added, and reality there also carrying proxyip support for CF vless and trojan nodes plus preferred reverse proxy IPs on non-standard ports. The top of the README states that shared subscription nodes are generated locally, with no node conversion and no third-party external subscription link. That is a privacy claim: nodes are generated locally rather than through a third-party converter.

No uninstall, no rollback, and a release tag that trails main by seven months

This is the thin part of the project. The README covers the happy path in detail, down to four pre-answered menu sequences, and says nothing about undoing any of it. There is no uninstall command, no rollback for a half-finished install, no note on what a second run of sb.sh does to an existing configuration, and no explanation of the version and sversion files sitting in the top-level tree, so the repository gives you no way to tell in advance which sing-box build a fresh run will fetch. The version trail is uneven too. The only release is tagged singbox on 2025-02-19, while the last push to the repository is 2026-10-05, well over a year later, so a checkout of the release is not the code you are reading about. The project is GPL-3.0 and the closing declaration credits GitHub community sources and ChatGPT, which means whatever configuration ends up on your box is not something the sing-box maintainers will debug for you.

Editorial conclusion

Use sb.sh if you own a VPS, are willing to paste a command into a root shell, and accept that nothing is written down about uninstalling or downgrading what it installs. The Serv00 script only fits a paid Hostuno account, or a free Serv00 account you can afford to lose. Before either run, work out which sing-box build main currently pulls, and read the blog post the README keeps linking, because the repository itself carries almost none of that detail.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. README
4. Releases
5. yonggekkk/sing-box-yg on GitHub