Nodes

A node is a proxy server running Xray. The panel stores its settings, serves the configuration, and monitors its state. Starting the container is described in Node installation.

Adding a node

Nodes → Create node. At minimum you need a name, an address, and a config profile.

Field	Required	Description
name	yes	3–30 characters
address	yes	IP or domain of the server
port	no	management port (NODE_PORT, defaults to 2222)
configProfile	yes	profile and active inbounds
proxyUrl	no	socks5://[user:pass@]host:port to manage through a proxy
countryCode	no	two-letter country code, defaults to XX
tags	no	up to 10 tags
isTrafficTrackingActive, trafficLimitBytes, trafficResetDay	no	node traffic accounting
consumptionMultiplier, nodeConsumptionMultiplier	no	traffic consumption multipliers
activePluginUuid, integrationUuids, note	no	plugin, integrations, note

After saving, the panel shows SECRET_KEY once — the node container needs it. The key is one-time and unique to each node.

Statuses

Indicator	Meaning
green, Connected	the node responds, Xray is running
yellow, Connecting	the panel is establishing a connection
gray, Disabled	the node is turned off by an administrator
red, Disconnected	the node does not respond

If a node stays Disconnected for a long time, check that NODE_PORT is reachable from the panel server and that SECRET_KEY is intact.

Xray version and load

The node card shows:

• versions.xray and versions.node — the core and agent versions;
• system.stats — free and used memory, loadAvg, uptime, and traffic volumes by network interface;
• xrayUptime — Xray uptime;
• usersOnline — the number of users online.

Node load and traffic history are stored separately (the nodes_usage_history table) and cleaned up according to NODES_USAGE_HISTORY_RETENTION_DAYS.

Restart

Restart node restarts Xray on the node. The panel compares the user set and restarts the core only when it changes; the forceRestart flag forces a core restart even if the configuration has not changed. For all nodes at once — Restart all nodes.

warning

Restarting Xray briefly interrupts active connections on that node. Do it outside peak load.

Logs

Xray logs live on the node in /var/log/xray, are capped at 10 MB, and are not archived. From the panel they are available on the Logs page, in the "Node system logs" section. To clear them, use the Clear logs button: the node rotates the file, Xray is not restarted, and traffic is not interrupted. Manually:

docker exec -it xpanel-node cli --clear-logs

Enabling and disabling

Disable node moves the node to Disabled: Xray stops on it, and users do not land on it. Enable node brings the node back into service. The node traffic counter can be reset separately — Reset node traffic; this does not affect user limits.

Bulk actions (enable, disable, restart, change the configuration for several nodes at once) are collected on the Bulk actions page.

tip

The profile and the inbound list of several nodes are changed with a single operation. This is handy when migrating from one profile to another — see Config profiles.

What's next

• Node installation — starting the container and SECRET_KEY.
• Hosts — how nodes become available to clients.
• Config profiles — what exactly Xray starts with.
• Common errors — if the node does not connect.