Skip to main content

​
Bot checks

Computers run in data centers. Websites may challenge or restrict traffic from these addresses. A browser proxy can change the exit IP; it does not guarantee that a website will accept automated traffic.

​
Bring your own proxy

For a running Linux computer, POST /api/computers/{id}/egress/upstream selects a customer-provided HTTP CONNECT proxy:
Authenticate with your Orgo API key and use your provider’s actual settings. tls describes the connection to the proxy and defaults to false when omitted. The password is encrypted when stored and omitted from GET /api/computers/{id}/egress/upstream responses. Selecting a custom upstream enables the computer’s browser relay if it is off. Initial enablement restarts Chrome; save browser work first. When the relay is already on, changing its upstream restarts the relay without restarting Chrome. This setting controls browser traffic, not every program in the computer. Availability depends on computer readiness and proxy eligibility. A computer with a dedicated IP returns 409 until you turn the dedicated IP off. If applying the upstream fails, Orgo restores the previous selection.