Skip to content

Networks

Every server on a node starts on the default network, where servers can reach each other. A proxy like Velocity relies on that to reach its backends. When two communities share one machine, give each its own network. Servers on different networks can’t reach each other, even on ports bound to 127.0.0.1.

Players reach every server’s ports whatever network it’s on.

The node’s Networks tab (admins and owners) lists its networks and the servers on each. It also lists the machine’s other Docker networks, read-only. Raptor never changes networks it didn’t make.

  1. On the node’s Networks tab, click New network and give it a name, like “Community A”.
  2. Open each server that belongs to it, go to its Network tab, and pick the network under Networks.
  3. Restart the server. It moves to the new network at its next start.

When you deploy a server on a node that has networks, you pick its network then.

Servers find each other on a network by name: “Survival SMP” is survival-smp.raptor. Each server also gets a name from its short ID, like 3e4f5a6b7c8d.raptor, which stays the same if it’s renamed. A server’s Network tab shows both.

A server can be on more than one network: its own, plus others under Also on. A Velocity or BungeeCord proxy on Community A’s and Community B’s networks reaches the backends on both, while the backends still can’t reach each other.

Sometimes one thing should cross: Community A’s servers joining a shared lobby, or one server reaching another community’s database. Rules between networks on the Networks tab let exactly that through:

  1. Click Add rule.
  2. Pick where connections come from: a network, or one server on it.
  3. Pick where they go to: a network, or one server on it.
  4. Pick the protocol and ports, like TCP 25565. Leave the ports empty to allow every port.

A rule works one way: replies get back, but the other side can’t start connections of its own. Removing a rule stops new connections; ones already open carry on until they close.

Each server has a fixed address on each of its networks, shown next to its name on the Networks tab. A rule that names a server applies once that server has started on the network. Rules work over IPv4, between networks you made; to include servers on the default network, put them on a network of their own first.

Open Advanced when making or editing a network:

Setting What it does
Internet access Off keeps its servers from connecting out, for backends that should only talk to their proxy. Players still reach their ports.
Reach the machine Off keeps its servers from connecting to services on the node itself. On some machines that includes other servers’ ports through the node’s address; a proxy should join its backends’ network instead.
IPv6 Gives the network an IPv6 range too.
Subnet Its address range. Raptor picks a free one unless you set a private range, like 10.210.0.0/24.
MTU Lower it if the machine is behind a VPN or a provider that needs it.

Changing the subnet, internet access, IPv6, or MTU recreates the network, so stop its servers first. Renaming it and changing Reach the machine work at any time.

Move its servers to another network first, then click the bin next to it. A network with servers on it can’t be deleted.

© 2026 Xena Studios. Pterodactyl is a trademark of its owners; Raptor isn't affiliated with it.