Self-Hosted Node Panel Guide: nexcore-x-ui, nexcore-s-ui & Dedicated Proxy
Compare Astrenix open-source nexcore-x-ui (Xray) and nexcore-s-ui (sing-box) against Tovanix Dedicated Proxy, plus server pairing and IP Quality Check steps.
- Built on Xray-core with a static Go backend, Vue 3 SPA, systemd hardening and a full /api/v1 REST API; supports VLESS Reality, VMess, Trojan and Shadowsocks 2022.
- Built on sing-box with musl static binaries, Cloudflare DNS-01 automatic SSL certificates, random first-run credentials and a compatible /api/v1 API; coexists with upstream s-ui.
- The platform installs protocols, opens firewall ports and issues per-member subscriptions automatically, with one-click relay and no platform traffic or device limits.
- Listed as carrier ISP or home broadband in IP databases; suited to storefront management and social operations sensitive to IP type.
Comparing the three deployment options
Once you have an overseas server, there are three main ways to turn it into a private network exit: install one of our open-source node panels over SSH (nexcore-x-ui or nexcore-s-ui), or let Tovanix Dedicated Proxy automate installation and ongoing management.
- nexcore-x-ui (Xray panel) — Built on Xray-core with a static Go backend, Vue 3 SPA, systemd hardening and a full /api/v1 REST API; supports VLESS Reality, VMess, Trojan and Shadowsocks 2022. — Developers and operators familiar with Xray who want full control over node configs and API automation.
- nexcore-s-ui (sing-box panel) — Built on sing-box with musl static binaries, Cloudflare DNS-01 automatic SSL certificates, random first-run credentials and a compatible /api/v1 API; coexists with upstream s-ui. — Technical teams preferring the sing-box protocol stack, multi-architecture Linux support and automated DNS certificates.
- Tovanix Dedicated Proxy (managed) — The platform installs protocols, opens firewall ports and issues per-member subscriptions automatically, with one-click relay and no platform traffic or device limits. — Individuals and teams who want zero SSH maintenance and unified management inside the Tovanix app.
You can mix approaches on the same account: run your main exits on Dedicated Proxy with one-click relay while self-hosting nexcore-x-ui or nexcore-s-ui on custom nodes.
Pairing panels with server and IP types
Whichever panel you deploy, the underlying server IP classification and route quality determine connectivity and environment cleanliness:
- Native IP VPS — Registered in the same country as the data center; ideal for general local services and clean standalone exit nodes.
- Dual-ISP / Residential IP VPS — Listed as carrier ISP or home broadband in IP databases; suited to storefront management and social operations sensitive to IP type.
- Lightweight Server (optimized route) — Provisioned automatically after payment; works well as a relay entry server forwarding traffic into a residential or dual-ISP exit.
- Dual ISP DIA / Premium CN2 Dedicated Server — Whole-machine hardware and bandwidth with optional extra Dual ISP IPs or full IP blocks for studios and fixed IP allowlists.
Standard workflow from server to verification
- Pick a server by country and IP type: Order a VPS, lightweight server or dedicated server in Tovanix Cloud; choose a clean Ubuntu 24.04 LTS image when available.
- Deploy a self-hosted panel or Dedicated Proxy: Follow the nexcore-x-ui or nexcore-s-ui tutorial when you want custom inbound and routing control, or activate Dedicated Proxy for zero-SSH automation and one-click relay.
- Open ports and configure TLS certificates: Allow the panel and protocol ports in your firewall; for TLS-based protocols, point a domain and add a Cloudflare API Token for automatic renewals.
- Verify the exit with IP Quality Check: Run the free IP Quality Check on this site to inspect network classification, native vs broadcast status and blacklist signals before connecting clients.
Deploying multiple nodes at once? IP Quality Check supports batch lookup for multiple public IPv4 and IPv6 addresses without signing in.
Frequently Asked Questions
What is the main difference between nexcore-x-ui and nexcore-s-ui?
The core proxy engine: nexcore-x-ui targets Xray-core with familiar inbound management and strict systemd sandboxing, while nexcore-s-ui targets sing-box with musl static builds and built-in Cloudflare DNS-01 certificates. Both expose a compatible /api/v1 REST API.
Can I switch a self-hosted server to Tovanix Dedicated Proxy later?
Yes. Reinstall a clean supported Linux image from the console before activating Dedicated Proxy so old ports and services do not conflict.
Which option works best on a physical dedicated server?
On Ubuntu 24.04 LTS or another supported Linux OS, nexcore-x-ui, nexcore-s-ui and external Dedicated Proxy onboarding all work. If you attach multiple extra IPs, a self-hosted panel gives finer control over per-IP outbound routing.
Related pages: nexcore-x-ui Installation & Operations Tutorial (Xray Panel) · nexcore-s-ui Installation & Configuration Tutorial (sing-box Panel) · Private network deployment solution · VPS with native and residential IPs
Loading…