Running m-ui without a domain
Plenty of people run a proxy on a VPS they will replace next month and never buy a domain for it. m-ui treats that as a normal setup, not a degraded one.
What actually needs a domain
Only two things: a certificate issued by a public CA (Let's Encrypt validates a name, not an address), and a stable address in subscriptions that survives changing the server. Everything else — TLS itself, Hysteria2, AnyTLS, Trojan, the panel, the landing page — works on an IP.
Step 1: self-sign
Certificate → Self-sign creates a long-lived certificate for the server's IP (and any names you type) and installs it for the data plane. It is one click. The Quick Start card on the dashboard counts it as "certificate ready"; a domain is listed under optional steps.
Step 2: what the subscription tells clients
When the certificate is self-signed, m-ui marks every TLS-bearing node in the subscription so clients do not reject it: skip-cert-verify: true in Clash / Mihomo YAML, "insecure": true in sing-box JSON, and the insecure flag each universal-link scheme uses. Users import the link and connect; nothing to toggle by hand.
The trade-off is real and worth stating: with certificate verification off, a client cannot detect a man-in-the-middle presenting another self-signed certificate. For most personal setups this is acceptable; for a service you sell, a domain and a real certificate are the better default.
Step 3 (optional): Reality needs no certificate
VLESS + Reality borrows a real website's TLS handshake and never presents your certificate at all, so it is the cleanest no-domain protocol: no self-signed warning, no insecure flag. Quick add → VLESS + Reality, generate the key pair, pick a handshake target, done. Many operators run Reality on IP-only servers and keep Hysteria2 with a self-signed certificate alongside it.
Step 4: the address in subscriptions
Without a domain, nodes are advertised by the server's public IP (auto-detected, or the address you set per server). If you later move to a new IP, edit the server's address once and every subscription updates on the client's next refresh — that is the one place a domain would have saved a step.
Adding a domain later
- Point the domain at the server.
- Certificate → Issue with HTTP-01 (port 80 reachable) or Cloudflare DNS-01 (API token, no port 80). m-ui pre-checks DNS and the port before it starts.
- Set the server's domain on the Servers page. Subscriptions switch from IP to name and drop the insecure flag on the next refresh; existing clients are not disconnected, because a certificate change is a hot reload.
Nodes without domains
Each node issues its own certificate. A self-signed one is fine: the master pushes lines with your TLS settings, and each node's subscription entries carry the insecure flag or not according to that node's certificate. Mixed fleets — a domain on the master, IPs on nodes — are normal.