nexcore-s-ui Installation & Configuration Tutorial (sing-box Panel)
Complete guide to Astrenix/nexcore-s-ui: one-click sing-box install, musl static builds, Cloudflare DNS-01 automatic SSL certificates, /api/v1 API and CLI.
- A rewritten Vue 3 + Element Plus frontend for managing sing-box inbounds, outbounds, routing rules and multi-user accounts.
- musl static binaries covering amd64, arm64 and more Linux architectures with zero host GLIBC coupling.
- A complete /api/v1 REST API with audit logging, compatible with nexcore-x-ui controller workflows.
- Built-in Cloudflare API Token support for automatic DNS-01 SSL certificate issuance and renewal without port 80 conflicts.
Architecture and key features
Redesigned from alireza0/s-ui for sing-box deployments and API-first automation, nexcore-s-ui provides:
- A rewritten Vue 3 + Element Plus frontend for managing sing-box inbounds, outbounds, routing rules and multi-user accounts.
- musl static binaries covering amd64, arm64 and more Linux architectures with zero host GLIBC coupling.
- A complete /api/v1 REST API with audit logging, compatible with nexcore-x-ui controller workflows.
- Built-in Cloudflare API Token support for automatic DNS-01 SSL certificate issuance and renewal without port 80 conflicts.
System and architecture requirements
- Supported OS — Ubuntu 24.04 LTS (end-to-end verified); also compatible with Ubuntu 20.04+, Debian 11+ and CentOS Stream 8+ with systemd.
- CPU architectures — Static binaries available for amd64, arm64, 386, armv5, armv6, armv7 and s390x.
- Privileges — Requires root access to bind ports 80 / 443, write ACME certificates and create tun devices when configured.
- Coexistence — Uses isolated paths, systemd unit and random port, allowing side-by-side coexistence with upstream s-ui.
One-click install, pinned version & force reinstall
Connect over SSH as root and run the official installer. First-time setup generates a random username, password and panel port:
bash <(curl -fsSL https://raw.githubusercontent.com/Astrenix/nexcore-s-ui/main/install.sh)
To pin a specific release tag or overwrite binaries without losing your existing database, pass a version tag or --force:
bash <(curl -fsSL https://raw.githubusercontent.com/Astrenix/nexcore-s-ui/main/install.sh) --force
# bash <(curl -fsSL https://raw.githubusercontent.com/Astrenix/nexcore-s-ui/main/install.sh) v1.0.0
Initial random credentials and the panel URI are printed once at the end of installation; copy and store them immediately before closing the terminal.
Configuring Cloudflare DNS-01 automatic SSL certificates
For Hysteria2, Trojan, AnyTLS or any TLS-enabled inbound, configure Cloudflare DNS-01 for hands-free certificate issuance and renewal:
- Point a Cloudflare-managed domain to your server: Register a domain in Tovanix Cloud (or use your own) and point an A / AAAA record for your node subdomain to the server public IP.
- Create a scoped Cloudflare API Token: In Cloudflare, create an API Token restricted to your target zone with only Zone:DNS:Edit permission instead of using a global API key.
- Enter the domain and Token in the panel: Open the certificate settings in nexcore-s-ui, pick DNS-01 mode, paste your domain and API Token and save to trigger automatic issuance and renewal.
DNS-01 proves ownership through DNS TXT records, so certificates issue and renew even if port 80 is busy or closed.
nexcore-s-ui CLI quick reference
Use the installed nexcore-s-ui command for service control, log checks, upgrades and removal:
- nexcore-s-ui — Open the interactive CLI menu for panel administration.
- nexcore-s-ui start | stop | restart | status — Start, stop, restart or check the status of the nexcore-s-ui service.
- nexcore-s-ui log — Inspect recent panel and core logs to diagnose inbound or ACME issues.
- nexcore-s-ui update — Upgrade to the latest GitHub Releases build while keeping your existing database.
- nexcore-s-ui uninstall — Uninstall binaries, systemd unit and local data completely (back up before running).
Troubleshooting
- Panel URL does not respond after installation — The random panel port is not open in the firewall, or the generated URI path is missing. — Check the port and full URI from the install output, allow the port in the firewall and confirm with nexcore-s-ui status.
- Cloudflare DNS-01 certificate issuance fails — The API Token lacks Zone:DNS:Edit permission for that zone, or DNS records have not propagated. — Verify the token scope and zone permissions, then inspect the exact ACME message via nexcore-s-ui log.
- Hysteria2 or UDP protocols fail to connect — Only TCP was opened in the firewall while UDP remained blocked, or the TLS certificate domain / ALPN mismatches. — Allow UDP traffic on the inbound port and ensure the client SNI matches your issued certificate domain.
- Need to repair binaries without losing data — Running uninstall wipes both binaries and the database. — Do not run uninstall; execute install.sh --force to overwrite binaries while keeping your existing database intact.
Frequently Asked Questions
Does nexcore-s-ui depend on a specific host GLIBC version?
No. Release binaries are statically compiled with musl across multiple Linux architectures, with Ubuntu 24.04 LTS recommended.
Can nexcore-s-ui run alongside upstream alireza0/s-ui?
Yes. Install paths, systemd service name and ports are isolated, so both can coexist as long as listening ports do not clash.
Why use Cloudflare DNS-01 instead of HTTP-01 for certificates?
DNS-01 does not require port 80, supports wildcard certificates and avoids conflicts with existing web servers.
Related pages: nexcore-x-ui Installation & Operations Tutorial (Xray Panel) · Self-Hosted Node Panel Guide: nexcore-x-ui, nexcore-s-ui & Dedicated Proxy · Private network deployment solution · Dedicated Proxy
Loading…