bytevirt-reality-node

Provision and audit ByteVirt VPS servers as no-panel Xray VLESS Reality nodes on port 443.

4|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/sukbearai/king-ai --skill bytevirt-reality-node-sukbearai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bytevirt-reality-node
Source: https://github.com/sukbearai/king-ai/tree/main/packages/skills/skills/bytevirt-reality-node
Command: npx skills add https://github.com/sukbearai/king-ai --skill bytevirt-reality-node-sukbearai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up a fresh ByteVirt VPS as a secure Xray proxy node involves many error-prone manual steps: installing Xray-core, generating Reality keypairs, writing systemd units with correct capabilities, and producing client import links. This Skill standardizes the entire no-panel deployment and audit workflow. ## Core Features & Use Cases - No-Panel Xray Deployment: Installs official Xray-core directly as a hardened systemd service running as a dedicated xray user, avoiding exposed x-ui management panels. - Credential Generation & Client Output: Generates UUIDs, Reality x25519 keypairs, and short IDs, then produces vless:// import links or client JSON for teammates. - Verification & Audit: Checks service status, port 443 reachability, and log health before handoff, with troubleshooting guidance for common SSH and permission failures. - Use Case: You just purchased a ByteVirt Japan VPS and need a working VLESS + Reality + Vision node on port 443 with per-teammate credentials, without exposing any web panel. ## Quick Start Use the bytevirt-reality-node skill to provision my new ByteVirt VPS at the given IP and SSH port as a no-panel Xray VLESS Reality node on port 443 and give me the client import link.

Frequently Asked Questions about bytevirt-reality-node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an Xray VLESS Reality node on a fresh VPS?▼

Install official Xray-core on Debian 12, generate a UUID and x25519 Reality keypair, write a VLESS inbound config with Reality stream settings on port 443, and run it as a systemd service. This Skill automates each step including verification and client link generation.

Should I use x-ui panel or install Xray directly?▼

Installing Xray directly as a systemd service avoids exposing a public management panel, reducing attack surface. This Skill defaults to no-panel deployment and only installs x-ui if you explicitly request it.

Why does SSH to my new ByteVirt VPS time out during banner exchange?▼

ByteVirt may expose the TCP port before sshd is fully ready. Retry with PubkeyAuthentication=no and password-only authentication, or wait and retry if nc confirms the port is open.

Why does the Xray service fail with config permission denied?▼

The xray system user cannot read /etc/xray/config.json when ownership is wrong. Fix it with chown xray:xray on the config file and mode 600, and ensure log files in /var/log/xray are also owned by xray.

How do I add multiple teammates to one Xray Reality node?▼

Add one UUID per teammate in the clients array of the Xray config, each with a distinct email label. This lets you disable or rotate a single person's access without affecting others.