Nodes
A node is a machine you’ve linked to your org. Its page has tabs for its Overview, Health, Backups, Disks, Databases, Networks, System, Activity, and Settings (all but Overview for admins and owners).
Overview
Section titled “Overview”- What it’s using: CPU, memory, server storage, and network, with charts over the last hour, day, or week.
- Its servers, with what each is using now.
- Details: its address, public IPs (hidden until revealed), architecture, cores, memory, Wings version, uptime, and when it was linked.
Health
Section titled “Health”The Health tab is the machine up close: load, memory and swap, every disk Raptor uses and how full it is, network interfaces, and what each server uses. Its checks are raptor doctor’s, run on the machine: each says what’s wrong, why it matters, and how to fix it. Check again runs them now. Raptor runs the checks every hour too, and the overview shows when something needs attention.
Its address
Section titled “Its address”Every node gets an address like 1cdd002cd9a3.raptornodes.net that follows its IP, even on a home connection whose IP changes. Players can connect to it with the server’s port, and SFTP uses it.
The address points at the machine’s public IPv4 address, since servers take players over IPv4. A machine with IPv6 too gets its IPv4 address here as well: Raptor checks both each time the node connects. If the node has no public IPv4 address at all, the address points at its IPv6 one, and the node’s page says “The Panel has only seen this node over IPv6”: players can’t reach its servers until it has a public IPv4 address.
Since it leads to your machine’s IP, the app hides it (and the IPs) until you reveal it, so it isn’t on screen while you stream; you can copy it without revealing it. Members never see the node’s IPs. For players, you can give a server its own shown address (a domain, or a proxy) on its Network tab.
Renaming
Section titled “Renaming”Rename a node on its Settings tab. The machine’s own hostname follows the name (“Basement Box #2” becomes basement-box-2) unless you give it one of its own on the System tab. The raptornodes.net address doesn’t change.
Removing a node
Section titled “Removing a node”Remove node on its Settings tab (admins and owners) unlinks it from your org:
- Its servers keep running on the machine; you just can’t manage them from Raptor.
- It stops counting towards your plan.
- Its address, Raptor Backup Storage (kept 30 days), and members’ access to its servers go.
To bring it back, make a join token and run sudo raptor relink -token rpt_join_… on the machine. To take Raptor off the machine entirely, see Leaving Raptor.
More than one node
Section titled “More than one node”Link as many machines as you like: each is $12 a month. In the app, choose Connect node again and run its command on the new machine. Servers are made on one node and stay there; to move one, back it up and restore it, or copy its files over with an SFTP import.
Details
Section titled “Details”The node’s Settings tab has a Details card with its ID, for support, and when it was linked.
Support access
Section titled “Support access”If you ask Raptor’s support for help, they may request access to a node: diagnostics only, operating its servers, or managing their files too, for a set time, with a reason and a ticket. Owners and admins are emailed, and the node’s pages show the request.
- Approve it with an owner’s passkey (you can give less than was asked, never more), or Deny it.
- While it lasts, the node’s pages show who has what until when, with End now.
- Everything staff do is in the node’s activity, marked as staff.
- Staff never get a shell, and can’t do anything that needs your passkey.
Turn support access off for a node entirely on its Settings tab, or with sudo raptor support off on the machine.
© 2026 Xena Studios. Pterodactyl is a trademark of its owners; Raptor isn't affiliated with it.