Understanding Nodes
A Node is a customer-owned Raspberry Pi that provides an Internet exit for proxy traffic. It runs the MyOwnProxy Node software, connects to one Gateway, and can be included in Pools.
Where a Node fits
The normal traffic path is:
Application -> Gateway -> Pool -> eligible Node -> Internet
The Node makes the outbound Internet connection, so websites and services normally see the Node's public IP as the source address.
Pool access is the recommended operating model. It lets a Proxy select from the Nodes that are both members of its Pool and available to serve traffic. Direct Node access is a secondary option for applications that must use one specific exit Node.
See How MyOwnProxy Works for the full system model and Using the Proxy for connection guidance.
Gateway assignment and Pool membership
Every operational Node is assigned to one Gateway. The Gateway provides the entry point and coordinates the connection to the Node.
Gateway assignment and customer-managed Pool membership are separate:
- Assigning a Node to a Gateway does not add it to customer-created Pools.
- The system-managed
pool-allis the exception: MyOwnProxy automatically maintains it with the Nodes assigned to that Gateway. - Adding a Node to a customer-created Pool does not change its Gateway assignment.
- A Node serves Pool traffic only when it is an eligible member of that Pool and its required path is available.
MyOwnProxy automatically reconfigures a Node when an ADMIN moves it to another Gateway. No manual Node changes are required. MyOwnProxy also updates pool-all automatically; review customer-created Pool memberships after the move. Expect a temporary interruption. See Managing Nodes.
Supported hardware
MyOwnProxy currently supports Raspberry Pi 4 Model B and Raspberry Pi 5 Nodes. Each Node requires at least 2 GB of RAM, a 32 GB or larger High Endurance microSD card, the appropriate official Raspberry Pi power supply, wired Ethernet, and stable Internet connectivity.
A passive case with good heat dissipation is recommended. A Flirc-style case is a suitable fanless option.
See System Requirements for the complete readiness checklist and Preparing and Adding a Node for the installation workflow.
Node states
The Node state summarizes its current lifecycle or health:
| State | Meaning |
|---|---|
| PENDING_ENROLLMENT | The Node record exists, but its first enrollment has not completed. Its one-time provisioning material remains usable while the Node stays in this state; elapsed time alone does not make the material expire. |
| ENROLLED | The Node has enrolled and is completing configuration or beginning normal health reporting. |
| ACTIVE | The Node is reporting healthy operation. Pool membership still determines which Proxies may select it. |
| DEGRADED | The Node is reporting a health problem. Review its health details before relying on it for traffic. |
| OFFLINE | The Node has stopped reporting within the expected period and is unavailable. |
| ORPHAN | The Node has no operational Gateway assignment and cannot serve proxy traffic until reassigned. |
| DECOMMISSIONED | The Node has been removed from proxy service. It remains as a managed record and can be explicitly reactivated. |
A state does not replace Pool membership information. For example, an ACTIVE Node is not eligible for a particular Proxy unless it is also included in that Proxy's Pool.
The first successful enrollment consumes the Node's provisioning material, so it cannot be reused for another enrollment. DECOMMISSIONED is a reversible lifecycle state: the Node retains its managed identity and can later be reactivated and reassigned. Permanently remove is a separate, irreversible action rather than a lifecycle state. It removes the logical Node identity and requires creation and provisioning of a new Node before the physical device can be used with MyOwnProxy again. See Managing Nodes.
Ownership and maintenance
You provide and maintain the Raspberry Pi, microSD card, power, Ethernet connection, and local Internet service. Required bandwidth depends on the amount and type of traffic the Node serves; MyOwnProxy does not publish a fixed minimum bandwidth.
MyOwnProxy manages the MyOwnProxy application software on the Node. Node software updates, supported operating-system security patches, and remote reboot actions are performed by MyOwnProxy administrators and coordinated with you when customer action or a maintenance window is required. See Node Software Updates and Node Security Patches and Reboots.
See the Shared Responsibility Model for the Node hardware, software, network, and physical-security boundary.
When a Node is unavailable
Pool-based applications may continue through other eligible, available Nodes. Direct access to the unavailable Node fails. If it is the only eligible Node in a Pool, that Pool cannot provide proxy service until a Node becomes available.
Review the Node's last heartbeat and health information in Health Explorer, then check its power, Ethernet connection, and local Internet service. See Node Problems if it does not recover.