Octo Browser Proxy Integration

This runbook maps Databay's authenticated gateway to the proxy controls documented by Octo Browser. Use it for a profile and destination you own or are authorized to operate. A proxy changes the network route; it does not create permission, prove a browser identity, guarantee account acceptance, or bypass a site's controls. Databay is not affiliated with, endorsed by, or sponsored by Octo Browser. The name is used only to identify the software and its settings.

Pick the network origin the authorized workflow actually requires, then use that product's username zone. Do not choose from an advertised pool size or assume one network is universally more accepted.

Octo documents HTTP, HTTPS, SOCKS5, and SSH proxy types. Databay's managed gateway supports HTTP proxying, HTTPS CONNECT tunnelling, and SOCKS5. Select HTTP in Octo for Databay's HTTP route, including HTTPS websites reached through CONNECT; select SOCKS5 only when the profile needs that protocol. Do not select Octo's HTTPS-to-proxy or SSH types for this Databay endpoint.

Use a temporary proxy when one profile needs the route and the team does not need a reusable Proxy Manager record. Octo's current temporary-proxy documentation gives this quick path:

1. In the profile list, click Direct in that profile's Proxy column.
2. Choose Set new proxy at the bottom of the list.
3. Select HTTP or SOCKS5 according to the Databay route above.
4. Enter gw.databay.co, port 8888, the product-specific Login, and the dashboard Password in their separate fields.
5. Leave URL for IP Change empty. Databay does not publish an Octo change-IP URL; route and requested session behavior belong in the username.
6. Click Check Proxy. Continue only after Octo reports Available and the observed country is plausible for the request.
7. Keep Save to proxy list off, confirm the temporary proxy, save the profile, and then start it.

Use Proxy Manager when several authorized profiles need a reviewed entry or a team needs one named source of truth. Open Octo's Proxies tab, use its add-proxy control, and enter a non-secret title plus the Type, Host, Port, Login, and Password from the field map. Run Check Proxy, then confirm only a passing entry. Alternatively, set up a temporary proxy, enable Save proxy, add a non-secret name, and confirm; Octo documents that this moves the entry into Proxy Manager for later selection. Assign the saved entry from a profile's Proxy field.

Name the entry by product and authorized purpose, such as residential-us-catalog-qa, without a password or customer identifier. Octo's Proxy Manager can display and copy login and password data, so grant team proxy permissions narrowly. A shared entry also shares its username's country and session request: create separate saved entries when profiles need different product zones, countries, or session labels.

Octo's current temporary-proxy documentation accepts quick-fill strings such as protocol://login:password@host:port. These two fixtures reproduce that grammar without a real credential:

http://USER-zone-residential-countryCode-us-sessionId-octo_qa_01:PASS@gw.databay.co:8888
socks5://USER-zone-residential-countryCode-us-sessionId-octo_qa_01:PASS@gw.databay.co:8888

Append one -countryCode-us flag only when the chosen product currently supports the requested country; the flag requests a route and does not prove supply or observed geography. Add a unique, non-personal -sessionId-octo_qa_01 only when one bounded multi-step flow needs temporary continuity. Premium Residential, Shared Datacenter, and Shared Mobile accept requested sticky windows up to 120 minutes; Residential Flex accepts up to 30 minutes. The exit can change earlier if upstream availability changes, and no Databay product provides a permanent or dedicated IP.

Without a session ID, a new proxy connection may select an available exit, but Octo and the destination can reuse a connection. A different IP on every page load is therefore not guaranteed. Do not change a session label or reopen connections to route around a 403, 429, CAPTCHA, suspension, or other access control. Stop and use an authorized access path.

Validation has three separate decisions:

1. Configuration check: Octo's Check Proxy should show green Available. Its current proxy-status documentation says yellow means unchecked or last checked more than five minutes ago, while red means the route could not be checked. A successful check can show a country flag and ISO code.
2. Observed route: start the profile and open Databay's IP checker. Record the observed IP, country, protocol choice, redacted username, profile label, and UTC time. If the direct machine or VPN address appears, stop before opening an authenticated destination.
3. Authorized destination: make one low-impact request to a page you own or are permitted to test. A green proxy check proves neither target acceptance nor repeat reliability.

Close the running profile before changing its proxy; Octo says edits apply after saving and restarting. Then work through this order:

• Parser: confirm Host is exactly gw.databay.co, Port is 8888, and Login and Password are in separate fields. Re-enter them if quick fill split a credential at : or @.
• Protocol: use Octo HTTP for Databay HTTP proxying and CONNECT, or Octo SOCKS5 for Databay SOCKS5. Do not infer a protocol from port 8888.
• Authentication: a proxy-authentication failure points to the dashboard Login or Password, not the destination account. Re-copy the values without publishing them.
• Gateway path: follow Octo's proxy FAQ to test the same route with system cURL against Octo's health endpoint. Use the tested Databay cURL guide to keep credentials out of shell history and process arguments.
• Octo checker: the default check timeout is five seconds. If the same credential works outside Octo but the checker fails, investigate the local network, VPN layering, firewall, and Octo configuration before changing products.
• Country mismatch: re-check the product zone and country code, then compare Octo's observed flag with the launched profile and another permitted IP diagnostic. Geo databases can disagree; one result does not prove country-wide supply.
• Destination response: a site denial is not a proxy-format error. Respect the response, request budget, account rules, and source terms instead of rotating around it.

Keep proxy credentials in an approved password manager, restrict Octo Proxy Manager permissions, and rotate a credential after suspected disclosure. Avoid screen recordings while Login, Password, or Copy Proxy output is visible. Use profile names and session IDs that describe an approved workflow without personal data. Maintain one owner, destination authorization, request budget, and stop condition per profile, and follow Databay's Acceptable Use Policy plus the destination's terms.

This guide was reviewed against Octo Browser's official profile-settings, temporary-proxy, Proxy Manager, proxy-status, bulk-add, and proxy-FAQ documentation on August 29, 2026. The field order and quick-fill grammar were reproduced with the non-secret fixtures above. Databay did not sign in to an Octo account or execute a paid Databay route through Octo for this publication, so the page does not display a live-test badge, screenshots, performance result, or compatibility guarantee. Re-check Octo's linked documentation if its labels move.