Skip to main content

Node Network

Use this page to review and manage networking for an existing node in MyAccount.

Node networking can include a primary public IPv4 address, private IPv4, Add-on IPs, IPv6, floating IPs, and VPC attachments. The options shown in the portal depend on node state, node family, project, region, and available network resources.

note

Network actions are validated before they run. If an option is disabled, check the node state, project, region, VPC status, and whether another node operation is already in progress.

Open Network Details​

  1. Log in to MyAccount.
  2. Go to Compute > Nodes.
  3. Select the node.
  4. Open the Network tab or network section on the node details page.

The network area can show:

  • Public IPv4 address
  • Private IPv4 address
  • Add-on IPs
  • IPv6 addresses
  • Floating IPs
  • VPCs and Subnets

The flows below assume you have already selected the node and opened its Network tab.

Public IPv4 Address​

A public IPv4 address is the primary public IP for the node. It is reachable from the internet. Depending on the node family and launch options, a node may have a primary public IP by default or may require you to attach one later.

Use a public IP only when the node must be reachable from the internet. Restrict inbound traffic with security groups and operating system firewall rules.

Best Practice

Do not expose SSH, RDP, database, or admin ports to the public internet unless the source ranges are restricted and the workload requires it.

E1 Public IP Behavior​

E1-series nodes do not include a default public IPv4 address. If an E1 node must be reachable from the internet, attach a primary public IP where supported before adding extra public IPs.

For E1-specific behavior, see E1 Series Nodes.

Detach all Add-on IPs before detaching the primary public IP. For other public IP availability checks, see Action Availability.

Attach a Primary Public IPv4​

Use this flow when the Network tab shows that no public IPv4 is attached:

  1. In Public IPv4, select Click here to add a public IP.
  2. In the Attach Public IP dialog, select an available reserved IP from the list.
  3. If no suitable IP is available, use Click here to reserve new IP and reserve a new public IP first.
  4. Select Attach IP.
  5. Wait for the Network tab to refresh and confirm that the public IPv4 is shown.

The attach dialog disables IPs that are already attached, unavailable, or reserved as floating IPs. A locked node must be unlocked before attaching a public IPv4.

Reserve the Current Public IPv4​

Use this flow when the node already has a public IPv4 and the portal shows the reserve option:

  1. In Public IPv4, select Click here next to the reserve prompt.
  2. In the Reserve IP Address dialog, review the monthly reserved-IP charge and the node IP address.
  3. Select Reserve IP.
  4. Confirm that the Network tab marks the IP as reserved.

A reserved public IP remains with your MyAccount even after the node is terminated, until you release it from the reserved IP service.

Detach a Primary Public IPv4​

Use this flow when you no longer want the node to have a primary public IPv4:

  1. Confirm that no Add-on IPs are attached to the node.
  2. In Public IPv4, select Detach IP.
  3. Review the Detach Public IP dialog. The node will no longer be publicly reachable through that IP.
  4. Select Detach IP.
  5. Wait for the Network tab to refresh and confirm that the public IPv4 is removed.

If Add-on IPs are still attached, the portal shows a message asking you to detach all Add-on IPs before detaching the primary public IP.

Add-on IPs​

Add-on IPs are additional public IPs attached to a node after the node already has a primary public IP. Use them when one node needs more than one public address, while keeping the first public IP as the primary address.

Use Add-on IPs when:

  • The node needs a stable public address.
  • DNS records must point to additional persistent IPs.
  • You want to move traffic between nodes without changing external DNS records.
  • The workload hosts multiple services that need separate public IPs.

Attach an Add-on IP​

Add-on IPs can be attached only after the node has a primary public IP.

To attach an Add-on IP:

  1. Confirm that the node already has a primary public IP.
  2. In Addon IPv4, select Click here to add more IPs.
  3. The portal opens the reserved IP area where Add-on IPs are managed.
  4. Reserve or select an available IP that can be attached as an Add-on IP for the node.
  5. Return to the node Network tab and confirm that the Add-on IP appears in the Addon IPv4 list.

The Network tab shows Currently no Addon IP attached when the node has no Add-on IPs.

Detach an Add-on IP​

Use this flow when you want to remove an Add-on IP from the node:

  1. In Addon IPv4, find the IP address you want to remove.
  2. Select Detach IP beside that Add-on IP.
  3. Review and confirm the detach dialog.
  4. Wait for the Network tab to refresh and confirm that the Add-on IP is no longer listed.

A locked node must be unlocked before Add-on IP attach or detach actions can run.

For the dedicated static public IP guide, see Static Public IPs.

Private IPv4 Address​

A private IPv4 address is used for communication that does not need direct internet exposure, such as traffic between resources in the same private network.

Use private IP access when:

  • Application tiers communicate internally.
  • A bastion, VPN, or private gateway controls access.
  • The node should not expose application ports publicly.

Private access still requires correct security group rules, route configuration, and operating system firewall rules.

IPv6​

If IPv6 is available for the selected node and location, the portal can show an IPv6 attach or detach action.

After attaching IPv6, update security group rules and the operating system firewall before publishing services over IPv6.

For IPv6 availability checks, see Action Availability.

Attach an IPv6 Address​

Use this flow when the Network tab shows that no Add-on IPv6 is attached, or when IPv6 allows additional addresses:

  1. In Addon IPv6, select Click here to add an IPv6 address.
  2. In the Attach IPv6 dialog, review the confirmation message.
  3. Select Attach.
  4. Wait for the Network tab to refresh and confirm that the IPv6 address appears in the list.

Detach an IPv6 Address​

Use this flow when you want to remove an IPv6 address:

  1. In Addon IPv6, find the IPv6 address you want to remove.
  2. Select Detach IP beside that address.
  3. In the Detach IPv6 dialog, confirm the IPv6 address.
  4. Select Detach IP.
  5. Wait for the IPv6 address to be removed from the list.

A locked node must be unlocked before IPv6 attach or detach actions can run.

Floating IP​

A floating IP is a public IP address that can be moved between nodes. Use it for failover patterns where traffic should move from one node to another.

Floating IPs are useful when:

  • You need a stable endpoint for a primary/standby setup.
  • You want to move traffic during maintenance.
  • You want an IP that can follow a replacement node.

For the dedicated guide, see Floating IP.

Attach a Floating IP​

Use this flow when the node needs a floating IP:

  1. In Floating IP, select Click here to add a floating IP.
  2. In the Attach Floating IP dialog, select an available floating IP.
  3. Review whether the selected floating IP is already attached to other nodes.
  4. If the portal says the floating IP has reached its attachment limit, detach it from another resource before continuing.
  5. Select Attach IP.
  6. Wait for the Network tab to refresh and confirm that the floating IP is listed.

If no floating IP is available, use the reserved IP area linked from the dialog to manage floating IP resources.

Detach a Floating IP​

Use this flow when you want to remove a floating IP from the node:

  1. In Floating IP, find the floating IP you want to remove.
  2. Select Detach Floating IP.
  3. In the Detach Floating IP dialog, confirm the IP and node name.
  4. Select Detach IP.
  5. Wait for the Network tab to refresh and confirm that the floating IP is removed.

A locked node must be unlocked before floating IP attach or detach actions can run.

Attach VPC​

Use VPC attachment when the node needs private networking. After a VPC is attached, the node receives a private IP from that VPC or from a selected subnet inside that VPC.

To attach a VPC:

  1. In Associated VPC, select Click here to attach a VPC. If VPCs are already attached and the node has not reached its attachment limit, select the add icon to attach another VPC.
  2. In the Attach VPC dialog, choose an active VPC from Select VPC.
  3. If needed, use the add icon to create a new VPC, or use the refresh icon after creating or updating VPCs.
  4. If the selected VPC supports subnets, choose a subnet from Select Subnet (Optional).
  5. If you choose a subnet, optionally enter a Preferred IP from that subnet.
  6. If the dialog shows a backup-impact acknowledgement for a custom VPC, read it and select the acknowledgement checkbox only if you want to proceed.
  7. Select Attach VPC.
  8. Wait for the Network tab to refresh and confirm the VPC name, subnet name, private IP, DNS, and network mask.

The associated VPC list shows the VPC name, subnet name where applicable, private IP, DNS, network mask, and detach action.

Detach a VPC​

Use this flow when you want to remove a VPC attachment:

  1. In Associated VPC, open the action menu for the VPC row.
  2. Select Detach.
  3. In the Detach VPC dialog, review the private IPv4 that will be removed from the node.
  4. If the dialog warns that CDP Backup is associated with the VPC, restore or retain any required data first, then select the acknowledgement checkbox if you still want to proceed.
  5. Select Detach VPC.
  6. Wait for the Network tab to refresh and confirm that the VPC row is removed.

After detaching a VPC, check CDP Backup, Monitoring, Alerts, security group rules, routes, and application configuration if they depended on the removed private IP.

VPC and Subnet Limits​

For node VPC attachments:

  • A node can have up to 3 VPC attachments.
  • A node can use at most 2 private IP attachments from the same VPC or the same subnet.
  • For custom VPCs, this means at most 2 subnet-backed attachments can come from the same VPC.

These limits apply to the node attachment view. Other products or services can have different VPC limits.

Network and Resource Transfer​

Some network attachments affect whether a node can be moved to another project.

Before moving a node to another project, review the network tab and detach or simplify resources that the portal marks as transfer blockers. For the full transfer checklist, see Action Availability.

ResourceUse it for
Manage NodesReturn to the node management overview.
Node SecurityConfigure access rules and protection settings.
Node ActionsUnderstand action availability and lifecycle operations.
Action AvailabilityCheck why network actions are hidden, disabled, or rejected.
Static Public IPsManage static public IPs that can be used as primary public IPs or Add-on IPs where supported.
Floating IPUse movable public IPs for failover.
VPCManage private networking.
Security GroupsControl inbound and outbound traffic.
Last updated on May 19, 2026.