Proxy Management and Multi-Hop Routes Proxies · Guide

Set up Oxylabs proxies

Generate Oxylabs location and session endpoints, then add, bulk import, check, and assign the connections to profiles in MaskPilot.

Updated Aug 25, 2026

MaskPilot does not use a dedicated Oxylabs integration. Residential, ISP, and datacenter products can be saved as standard proxies whenever Oxylabs supplies an HTTP, HTTPS, or SOCKS5 host, port, username, and password.

Get an Oxylabs endpoint

Sign in to the Oxylabs dashboard and open the relevant product. For rotating residential proxies, use the endpoint generator to select a location, authentication method, and session type before exporting connections. For a static product, obtain the connection details from the assigned IP or endpoint list.

Common hosts and ports

Product or entryServerPortProtocol and use
General residential entrypr.oxylabs.io7777HTTP / HTTPS / SOCKS5; location and session are normally encoded in the username
US random entry exampleus-pr.oxylabs.io10000HTTP / HTTPS; returns a random US exit for new requests
US sticky entry exampleus-pr.oxylabs.io10001HTTP / HTTPS; used for a US sticky session
Other country entriesCorresponding *-pr.oxylabs.io hostCountry-specific portCopy from the official entry list or dashboard; do not reuse the US port
Dedicated datacenter or ISP proxyAssigned IP or hostnameAssigned portValues can differ by product and node

pr.oxylabs.io:7777 is the general residential entry. Oxylabs currently does not support SOCKS5 through country-specific entry nodes. For SOCKS5 location targeting, use the general entry and preserve the country or city parameter in the username. Do not mix entry details from different products.

Prepare:

  • The protocol supported by the current Oxylabs product.
  • The entry hostname or static IP and its port.
  • The complete proxy-user username and password.
  • Any generated location, city, and sticky-session parameters.

Location and session settings may be encoded in the username or entry address. Do not shorten those values. See the official Oxylabs endpoint generator guide for the current controls and export formats.

Add one Oxylabs proxy

  1. Open Proxies in MaskPilot and select “Add proxy.”
  2. Select “Standard proxy.”
  3. Choose HTTP, HTTPS, or SOCKS5 according to the generated Oxylabs endpoint.
  4. Enter the entry host, port, proxy username, and password separately.
  5. Set Provider to Oxylabs and optionally record the region, expiry date, and a note.
  6. Save, select “Check connection,” and verify the exit details.

Do not use a dashboard email address or account sign-in password as proxy-user credentials. When IP allowlist authentication is enabled, the username and password can be empty, but the current device’s public source IP must already be allowed by Oxylabs.

Import an endpoint list

Export TXT from the endpoint generator, or convert the connection columns from CSV into one proxy per line, then use Bulk import:

host:port:username:password
http://username:password@host:port
https://username:password@host:port
socks5://username:password@host:port

A host:port:username:password line without a scheme is imported as HTTP; keep the corresponding scheme for HTTPS or SOCKS5 endpoints. Do not paste an entire CSV or JSON document with headers into the standard-proxy importer. Remove headers and unrelated columns first, verify the recognized count, and review every imported protocol and port.

Assign it and choose session behavior

  1. Create or edit a browser profile.
  2. Under Network connection, select “Use proxy.”
  3. Choose a saved and successfully checked Oxylabs node.
  4. Save and launch the profile, then verify the actual exit location.

Rotating residential proxies can allocate a new IP for each request. When one profile must keep the same exit during a working session, choose a sticky session in the Oxylabs endpoint generator or use the provider-defined session parameter. MaskPilot region labels and notes do not control rotation.

Common failure causes

  • The proxy username is missing a required product prefix, location, or session parameter.
  • The host or port belongs to a different Oxylabs product.
  • SOCKS5 enablement, DNS, or port requirements differ from the HTTP connection.
  • Source-IP allowlist, traffic allowance, or product status has changed.
  • Hyphens, underscores, or capitalization in the username changed during copying.

Correct one item at a time and check again. Follow the current Oxylabs protocol guide for product-specific restrictions, and see Why does a proxy check fail? for general diagnosis.