x-ui-yg: a patched x-ui panel with Hysteria2, Xhttp, Argo tunnels and Psiphon routing

What x-ui-yg adds on top of vaxilu's x-ui

x-ui-yg is a one-click Shell script that installs a modified x-ui panel. The README states the goal plainly: keep panel settings as close as possible to the original author vaxilu's x-ui, while adding features the upstream panel does not carry. Those additions are Hysteria2, the Xhttp transport, ENC encryption, MLDSA65 encryption, Argo fixed and temporary tunnels that can coexist, Psiphon routing across 30 countries, and subscription output in aggregated node, sing-box and clash-meta formats.

The intended user is someone running a single VPS who wants several proxy protocols and a subscription feed without assembling the stack by hand. The README lists support for pure IPv4, pure IPv6, AMD64 and ARM64 hosts, and Alpine alongside a recommendation to use the latest Ubuntu. Subscription nodes are generated locally rather than through a third-party conversion service, which the README frames as avoiding exposure of subscription contents to an external link author. That is a real architectural choice, not marketing: the panel produces the subscription itself.

How the panel, tunnels and subscription generation fit together

The repository layout is small: README.md, config.json, install.sh, ssh.yml, a version file, and two prebuilt binaries named xuiwpph_amd64 and xuiwpph_arm64. The installer is a Shell script, and the panel it deploys is a compiled binary rather than something built from source on your machine. That is the central fact about this project. The README's closing note says the binary files are not open source and asks anyone uncomfortable with that not to install.

The Argo integration uses Cloudflare's cloudflared, which appears in the repository topics alongside argo and cloudflared. The README describes fixed and temporary tunnels that can coexist, meaning the panel can hold both a named tunnel and a quick throwaway tunnel at once. Psiphon and WARP routing appear as local split-routing options, with the README describing a local WARP plus Psiphon switch covering 30 country IPs. Subscription output is generated locally, so the panel writes sing-box and clash-meta configuration from its own node list. The README does not document how the routing rules are evaluated or in what order, which matters if you plan to combine Psiphon country selection with Argo tunnels.

Installing x-ui-yg and reaching the panel for the first time

The README gives two equivalent one-line installers. Both download install.sh from the main branch and run it. Run one of them as root on the VPS, not on your laptop. The wget form is:

bash <(wget -qO- https://raw.githubusercontent.com/yonggekkk/x-ui-yg/main/install.sh)

The curl form does the same thing if wget is not present:

bash <(curl -Ls https://raw.githubusercontent.com/yonggekkk/x-ui-yg/main/install.sh)

After the script finishes, the panel is reachable in the browser and you log in with the credentials the installer sets. Everything beyond that point, including Hysteria2 certificate handling and multi-port hopping, is covered in the blog post and video series the README links to rather than in the repository.

The binaries are closed, and that is the decision that matters

The README states directly that the binary files are not open source and that people who mind should not install. For a proxy panel that terminates your traffic and holds your node credentials, that is the single most consequential fact on the page. You can read install.sh, because it is Shell and it lives in the repository. You cannot read xuiwpph_amd64 or xuiwpph_arm64. The panel you log into after installation is the part you cannot inspect.

This is not a hidden flaw, it is a stated boundary, and the project is honest about it. But it rules the project out for anyone whose threat model includes supply-chain review of the panel itself. A second limitation is documentation depth. The README repeatedly defers to a blog post and a series of YouTube videos for setup detail, including certificate handling for Hysteria2 and multi-port hopping. If you prefer written reference documentation over video, you will be working from the panel UI and trial and error for anything the README does not spell out. The README also does not document rollback, so plan a snapshot before you run the installer over an existing x-ui installation.

x-ui-yg versus MHSanaei's 3x-ui

The README names 3x-ui by MHSanaei as one of the reference projects, alongside vaxilu's x-ui, qist's xray-ui and bepass-org's warp-plus. The practical difference is packaging and scope. 3x-ui is the widely used fork that keeps its panel code in the repository, so you can build it yourself and audit what runs. x-ui-yg ships a compiled binary and concentrates on bundling extras: Argo tunnels, Psiphon country routing, Xhttp presets and local subscription generation for clash-meta and sing-box.

If your priority is a panel whose source you can read and build, 3x-ui is the closer fit and x-ui-yg is the wrong tool. If your priority is having Argo, Psiphon and Hysteria2 wired into one panel without assembling them, x-ui-yg is doing work that 3x-ui does not do out of the box. That is the trade: convenience against auditability. Note also that the README points to a separate Docker build maintained by ShaoG-R at ShaoG-R/x-ui-yg-docker, which is a different repository from this one and carries its own maintenance.

Maintenance, licence and what upgrading costs you

The repository is not archived and the last push was on 2026-09-02, so the project is being touched. The release history is thinner than the push activity suggests: the recent releases listed are xui_ygb from 2025-06-10 and xui_yg from 2025-03-12. If you track releases, expect gaps, and check the version file in the repository against the release tag before assuming the installer pulls a tagged build.

Licensing is unresolved. The repository has no licence identifier, and the README does not state terms. The README does name the projects the code draws on (vaxilu's x-ui, MHSanaei's 3x-ui, qist's xray-ui, bepass-org's warp-plus), and those upstream projects carry their own licences. Since the panel binary is distributed without source, you cannot verify which licence obligations attach to which component. If you need a clear licence position for internal or commercial deployment, treat that as an open question to resolve before installing rather than after. None of this is legal advice; it is a statement of what the repository does and does not tell you.

Editorial conclusion

Adopt x-ui-yg if you run a single VPS and want Hysteria2, Xhttp, Argo tunnels and Psiphon country routing generated from one panel, and you accept that the binaries ship without source. Do not adopt it if your policy requires auditable code, a documented licence, or vendor support. Before installing, read the blog post the README links to, confirm whether your VPS is amd64 or arm64, and check the repository's version file against the release tags so you know which build the installer will pull.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. yonggekkk/x-ui-yg on GitHub