Skip to content

Node Problems

Use this page when a Node is OFFLINE or DEGRADED, its heartbeat is stale, its dataplane health fails, direct Node access fails, or a Pool loses an eligible Node.

Checks

  1. Open Health Explorer and review the Node's lifecycle state, dataplane health, last heartbeat, and last reported public IP.
  2. Review Alerts for the Node and its assigned Gateway.
  3. Check the Node's power, Ethernet connection, and local Internet service.
  4. Confirm that its assigned Gateway is ACTIVE and healthy.
  5. If a Pool is affected, verify the Node's Pool membership and use Candidate Diagnostics to check whether it is present and eligible.
  6. Determine whether the application uses the Pool endpoint or the Node's Direct Access value.

Both ADMIN and VIEWER users can inspect these portal views. An ADMIN is required to change Gateway assignment, Pool membership, or Node lifecycle state.

What the result means

  • OFFLINE or a stale heartbeat means the Node is not providing current operation information. Direct access through it is unavailable, and it cannot be relied on for Pool traffic.
  • DEGRADED or failed dataplane health means the Node is reporting but has a condition that can exclude it from selection or disrupt traffic.
  • If the assigned Gateway is unavailable, the Node cannot serve proxy traffic through that Gateway even if the Node itself has power and Internet access.
  • A Pool can use another currently eligible member for a subsequent connection. An established connection does not move to another Node automatically.
  • A direct connection has no alternate Node; it fails while that Node or its Gateway path is unavailable.

Supported recovery

Restore power, Ethernet, or local Internet service, then wait for a current heartbeat and healthy dataplane result. Verify affected traffic with a new connection.

If the assignment or Pool membership is wrong, an ADMIN can use Managing Nodes and Managing Proxies and Pool Nodes to correct it. After a Gateway reassignment, recheck Pool membership and copy the Node's entire current Direct Access value because its connection values can change.

Temporary SSH access is an optional, privileged escalation path, not the first recovery step. Use Remote Access Problems if an ADMIN cannot use issued access material. A Node that cannot be reached through the normal workflow requires MyOwnProxy Support for Emergency Node Rescue.

Contact Support

Contact MyOwnProxy Support when physical connectivity and the assigned Gateway are healthy but the Node does not return to ACTIVE and healthy operation, or when its dataplane health or proxy traffic does not recover. Include the information in Contacting Support.