Repository navigation
Home
A Mihomo management panel for Linux proxy servers
m-ui is an open-source web control panel for Mihomo. Its layout and workflow are inspired by 3x-ui, but its configuration model follows Mihomo's native YAML format rather than Xray JSON.
The panel lets you manage listeners, clients, Mihomo outbounds, routing rules, subscriptions and subscription templates, WARP and VPNGate egress, traffic statistics, and multiple peer panels from one browser interface.
Important
Use m-ui only on servers and networks that you own or are authorized to administer. Proxy software must be used in accordance with local law, provider terms, and the policies of the services you access.
- Responsive web panel with an Apple-style Liquid Glass interface
- Interface in 11 languages: English, Simplified Chinese, Traditional Chinese, Japanese, Russian, Persian, Vietnamese, Spanish, Turkish, Ukrainian and Brazilian Portuguese
- Dashboard with CPU, memory, disk, uptime, traffic, connection, and Mihomo status information
- Native Mihomo YAML generation and validation
- Mihomo starts automatically with the panel; start, stop, restart, test, and inspect it from the dashboard
- Mihomo release switching from the official MetaCubeX GitHub releases
- GeoIP, GeoSite, and MetaDB updates
- Configuration preview and download
- Full backup and restore: settings, inbounds, Multi-control identity (opt-in), cross-panel cache, and subscription templates
- Mixed, HTTP, SOCKS, Shadowsocks, Snell, VMess, VLESS, Trojan, Hysteria2, TUIC, AnyTLS, Mieru, Sudoku, ShadowQuic, TrustTunnel, and Hysteria2 Realm listeners
- Per-client credentials, traffic quotas, expiry dates, reset schedules, enable/disable state, and online information
- Client share links, QR codes, and subscription tokens
- Protocol-aware TLS, Reality, ShadowTLS, RestTLS, TLSMirror, XHTTP, KCP, and obfuscation fields
- Import inbounds from Mihomo listener YAML, and export individual inbounds
- Inbound-level and client-level traffic limits and expiry, shown in the Inbounds table
- Basics page for routing mode, IP preference, IPv6, concurrent TCP dialing, unified delay, traffic sampling, and logs
- Outbound proxy nodes (including Snell, WireGuard, and OpenVPN) and policy groups
- YAML editor and Mihomo sharing-link conversion for outbound import
- Ordered Routing Rules with Mihomo rule types and targets
- Cloudflare WARP account registration and WireGuard outbound generation
- VPNGate residential egress by country and ISP
- Browser subscription page at a tokenized URL
- Subscription templates: every subscription is a complete client profile built from the built-in China / Russia / Iran template or your own imported Mihomo template
- Base64 node lists and Mihomo / Clash YAML subscriptions
- Full profiles for Sing-box, Surge, Surfboard, Loon, Quantumult X, Stash, and Egern; node lists for V2Box, V2RayNG, Shadowrocket, and other share-link clients
- Per-Username subscription tokens
- Optional dedicated subscription service port
- Cross-panel subscription aggregation through the peer network
- Peer-to-peer panel network with no master panel
- 16–32 character lowercase alphanumeric pairing tokens
- Signed Ed25519 node identities and automatic member discovery
- Encrypted inbound synchronization between trusted panels
- Cached cross-panel subscription aggregation
The one-line installer targets Linux systems using systemd or OpenRC. It has package-manager support for the following families:
| Family | Examples | Service manager |
|---|---|---|
| Debian | Debian, Ubuntu, Linux Mint, Armbian | systemd |
| Red Hat | Fedora, RHEL, CentOS, AlmaLinux, Rocky, Oracle Linux, Amazon Linux | systemd |
| Arch | Arch Linux, Manjaro, Parch Linux | systemd |
| SUSE | openSUSE, SLES | systemd |
| Alpine | Alpine Linux | OpenRC |
Each release also publishes a Windows amd64 build and a Docker image for Linux amd64 (see Installation). The one-line installer, the m-ui management command, and VPNGate are Linux-only.
| Architecture | Release asset |
|---|---|
| Intel/AMD 32-bit | m-ui-linux-386.tar.gz |
| Intel/AMD 64-bit | m-ui-linux-amd64.tar.gz |
| ARM 64-bit | m-ui-linux-arm64.tar.gz |
| ARMv5 | m-ui-linux-armv5.tar.gz |
| ARMv6 | m-ui-linux-armv6.tar.gz |
| ARMv7 | m-ui-linux-armv7.tar.gz |
| IBM Z | m-ui-linux-s390x.tar.gz |
| Windows 64-bit | m-ui-windows-amd64.zip |
| Docker (Linux amd64) | ghcr.io/romanovcaesar/m-ui:<tag> |
- Installation
- Panel Configuration
- Inbounds and Clients
- Mihomo Settings
- Subscriptions
- Subscription Templates
- Multi-control and Cross-panel Features
- Cloudflare WARP
- VPNGate
- Maintenance and Management
- API Overview
- Development and Releases
- Common Questions and Problems
m-ui intentionally follows Mihomo instead of attempting to reproduce Xray behavior:
- The generated core configuration is YAML.
- Mihomo's
proxies,proxy-groups, andrulesare managed as separate concepts. - Mihomo does not expose every Xray routing primitive; for example, BitTorrent protocol matching is not available and its UI control is disabled.
- WARP is represented as a Mihomo WireGuard outbound. It does not install a system-wide WARP client or change the server's default route.
- NordVPN integration is not included.
Before exposing a panel publicly, change generated credentials if necessary, use a non-obvious panel path, configure HTTPS, restrict firewall access to the required panel/subscription/inbound ports, and keep m-ui and Mihomo updated. Never publish data/state.json, data/multi-control.json, panel backups, certificates, private keys, subscription tokens, or pairing tokens.