Skip to content

Detach a node's public IP

View as Markdown

Detaching a node’s primary public IP disconnects it from the node; what happens to the address after that depends on whether it is reserved. A reserved IP stays yours: it is free to attach to another node once you detach it. A node’s own default address, the one it was given at creation that you never reserved, is returned to the pool for good when you detach it. Reserve an IP first if you want to move it between nodes rather than lose it. See Attach a reserved IP to a node for that.

If the node has an Add-on IP, detach that before the primary public IP. An Add-on IP is an extra public IPv4 address on top of the node’s primary one. Also clear or transfer any cPanel, BitNinja, FortiGate, or Webuzo license bound to the primary IP. The node itself must be Running or Powered off, and unlocked.

The node loses its public access the moment you confirm, so make sure you can still reach it another way, or have a reserved IP ready to attach.

  1. Open the node’s Network tab.
  2. Click Detach IP next to the public IPv4 address.
  3. Confirm the warning that you will lose public access to the node until you attach another IP, which costs extra.

The Network tab now reads Currently no public IPv4 is attached. The node keeps its private IP, so it stays reachable from other nodes on the same private network. To give it a public address again, see Attach a reserved IP to a node. If the detach link is missing or refused, see Troubleshooting node networking and connectivity.