Skip to main content

Troubleshooting E1 Series Nodes

E1 nodes behave differently from C3, M3, SDC3, and WSDC4 nodes in three important ways: they can be Stopped (released and re-allocated on demand), they do not include a default public IP, and they have specific storage and plan rules. This guide covers the issues that arise from those differences.

Common Issues​

IssueWhat to check
Stop is not visibleConfirm that the node is an E1-series node, is in a valid state, and is not blocked by another operation.
Node is Stopped and actions are disabledStart the node first. Stopped E1 nodes allow only start and stop actions.
Public IP is missing after launchThis is expected for E1. Attach a primary public IP if direct public access is required. Add-on IPs can be attached only after the primary public IP exists.
Root storage upgrade is unavailableCheck Action Availability, then confirm E1 size rules.
New root storage size is rejectedUse a larger size within 75 GB to 2400 GB. Below 150 GB, use 25 GB increments; from 150 GB and above, use 50 GB increments.
Root storage upgrade fails because snapshots existDelete active snapshots for the root disk and retry after deletion completes.
Update Node Plan is unavailableCheck Action Availability, then confirm compatible target plans.
Starting from Stopped takes timeStarting a Stopped E1 node can take longer because the node must be allocated again.

Details​

Stop Action is Not Visible​

The Stop action is exclusive to E1 nodes — other families do not expose it because they cannot release resources back to the pool. If you do not see the Stop action:

  • Confirm the node is an E1-series node.
  • Confirm the node is in a valid state (typically Running and unlocked).
  • Confirm no other operation is in progress on the node.

Node is Stopped and Actions are Disabled​

A Stopped E1 node has been deallocated and is not running. Only start and stopw actions are available in this state. To restore the full action set, Start the node. Starting a Stopped E1 may take longer than a normal boot because the platform must allocate compute back to the node before it can run.

Public IP is Missing After Launch​

E1 nodes intentionally do not include a default primary public IP. If your workload needs to be reachable over the public internet, attach a primary public IP from the node action menu after launch. Add-on IPs require a primary public IP first — you cannot attach an Add-on IP to an E1 that has no primary.

Root Storage Upgrade is Unavailable​

The Root Storage upgrade action depends on plan, state, and family gates. Check Plan, Storage and Billing Actions first to confirm the action should be visible, then confirm the new size satisfies the E1 size rules below.

New Root Storage Size is Rejected​

E1 root storage has explicit size rules:

  • Minimum: 75 GB
  • Maximum: 2400 GB
  • Below 150 GB: sizes must be in 25 GB increments (75, 100, 125)
  • At or above 150 GB: sizes must be in 50 GB increments (150, 200, 250, …)

The new size must always be larger than the current size — root storage cannot be shrunk.

Root Storage Upgrade Fails Because Snapshots Exist​

Root storage cannot be upgraded while there are active snapshots of the root disk. Delete the existing root-disk snapshots and wait for the delete to complete, then retry the upgrade. Snapshots on attached data volumes do not block a root storage upgrade.

Update Node Plan is Unavailable​

Plan updates are gated by Action Availability and by plan compatibility. The target plan must be in the same family and offer compatible specifications — the portal only lists plans you are allowed to switch to. If the list is empty, no compatible plan exists for the current node.

Starting from Stopped Takes Longer​

A Stopped E1 node has been deallocated from the compute pool. Starting it requires the platform to allocate compute back to the node before the OS boots — this is expected and is the trade-off for the lower price of the Stopped state. Allow a few extra minutes compared to a normal reboot.

Last updated on May 19, 2026.