Managing Gateways
Use Gateway information and lifecycle operations to keep proxy entry points healthy, move Nodes safely, and retire or replace Gateway hosts.
An ADMIN can update Gateway information, reassign Nodes, and decommission a Gateway. A VIEWER can review Gateway information and status but cannot make these changes.
View Gateway information and status
The Gateway list provides a summary of each Gateway, including its identity, region, state, public IP, assigned-Node counts, recent operational reporting, and resource information.
Gateway details provide additional information about:
- Gateway identity, software version, and lifecycle state.
- The most recent operational report and current health.
- Host resource observations reported by the Gateway.
- Proxies served through the Gateway.
- Nodes currently assigned to the Gateway.
Use Understanding Gateways to interpret lifecycle states. Use Observability when investigating a health or availability problem.
Update Gateway information
An ADMIN can update a Gateway's display name and region. Changing these descriptive values does not move Nodes or change Pool membership.
After saving a change, verify that the updated values appear in Gateway details. If the Gateway host or public IP must change, confirm the supported approach with MyOwnProxy Support rather than assuming that a descriptive edit replaces the infrastructure.
Understand assigned Nodes
The assigned-Node list shows which Nodes currently use the Gateway for connectivity and management. It does not show whether each Node belongs to a particular Pool.
Before changing Gateway assignments, review both:
- The Node-to-Gateway assignment.
- The Node's membership in Pools used by production Proxies.
See Nodes and Proxies for the related resource views.
Move a Node to another Gateway
Purpose
Move a Node when changing its serving location, draining a Gateway, or validating a replacement Gateway.
Required role
You must be an ADMIN.
Before you begin
- Make sure the destination Gateway belongs to the same Customer.
- Use an ACTIVE destination Gateway that you have already validated. If no suitable ACTIVE Gateway is available, resolve the Gateway health issue before moving the Node.
- A Node in PENDING_ENROLLMENT cannot be moved. Complete Node enrollment first.
- Expect a temporary interruption while the Node changes Gateway assignment.
Move and verify the Node
- Open the Node that you want to move and start the Gateway reassignment.
- Select the destination Gateway and provide a reason when useful.
- Confirm the reassignment.
- Wait for the Node to receive and apply the new assignment.
- Verify that the Node shows the destination Gateway and returns to an operational state.
- Review Pool membership and test affected Proxy connections.
MyOwnProxy applies the change automatically. Do not manually reconfigure the Node.
Gateway assignment and Pool membership are separate. Do not assume that moving a Node preserves or establishes its eligibility for every Proxy. Confirm the intended Pool membership after each move.
Respond to an unavailable Gateway
When a Gateway is DEGRADED or OFFLINE:
- Review its last operational report, health information, and assigned Nodes.
- Determine which Proxy connections and Pools depend on it.
- Use Gateway Problems or contact MyOwnProxy Support if the Gateway should be recovered.
- If replacement is required, establish and validate a replacement before moving production Nodes.
Do not decommission a Gateway merely to clear an availability alert. Decommissioning is a retirement action and has additional effects on Nodes and Proxies.
Replace a Gateway
A replacement is normally created as a new Gateway in MyOwnProxy.
Use this safe sequence:
- Prepare a supported replacement host or virtual machine.
- Create and install a new Gateway.
- Verify that the new Gateway is ACTIVE and reporting healthy operation.
- When appropriate, move one low-impact Node to the new Gateway and validate its health, Pool membership, SOCKS5 operation, and exit IP.
- Move the remaining Nodes, reviewing Pool membership and Proxy behavior after each stage.
- Update application connection details when the replacement Gateway's details differ.
- Confirm that no production Nodes, Pools, Proxies, or applications still depend on the old Gateway.
- Decommission the old Gateway.
This staged approach limits the impact of a replacement and provides a verification point before the old Gateway is retired.
Decommission a Gateway
Decommissioning is the customer-facing removal operation currently available in MyOwnProxy. The UI does not provide permanent deletion of the Gateway record.
Before you begin
- Move all Nodes that must remain in service to another validated Gateway.
- Reconfigure or retire Pools and Proxies that depend on the Gateway.
- Update applications that use its connection details.
- Confirm that the Gateway no longer carries required proxy traffic.
The operation does not move remaining Nodes to another Gateway. Any Nodes still assigned to it become unassigned, and Proxy configurations that depend on the Gateway may stop working.
Decommission and verify
- Review the Gateway identity and impact summary.
- Start decommissioning, enter a reason, and type the exact Gateway ID to confirm the action.
- Confirm that the Gateway reaches DECOMMISSIONED state.
- Confirm that no Nodes that must remain in service are still assigned and that affected Proxies have been handled.
- Verify production traffic through the replacement path before deprovisioning the old host.
A decommissioned Gateway is stopped for normal operation and cannot be selected as a Node assignment target. Create a new Gateway if service is needed again.
Gateway software updates
MyOwnProxy manages MyOwnProxy application software on Gateways. Gateway software updates are currently performed by MyOwnProxy administrators; ADMIN users should not expect a customer self-service upgrade workflow.
You remain responsible for Gateway OS upgrades and OS security packages. See Gateway Software Updates.