Support

Something is blocked

If a site is detecting the browser, or a fingerprint signal looks wrong, email support@rayobyte.com with the target URL, the session id (br_ plus 16 hex characters) and the time it ran.

Turn on debug logging first and include the output:

import logging
logging.basicConfig(level=logging.DEBUG)

Anti-detection specifics are handled privately, not in public threads.

Bugs and requests

Email support@rayobyte.com. Include the endpoint, the exact request, the status code and the response body.

More browsers or more hours

Email sales@rayobyte.com or use the contact form. Both the 5 concurrent browsers and the 48 browser hours are raised per account and take effect without a key change.

Common questions

Chromium, not Chrome. Chrome is closed source and can’t be patched at the engine level, which is where rayobrowse does its work. Chromium-based browsers (Edge, Brave, Samsung Internet) are a large share of real traffic, and rayobrowse presents as Chrome: the user agent and client hints say Google Chrome.

SDK versions. The Python SDK needs Python 3.10 or newer. The Node.js SDK needs Node.js 18 or newer.

A session that ended on its own either ran out its maxLifetime, in which case the status is EXPIRED, or the browser went away without being asked to, which is DEAD. A CDP disconnect is not one of the causes: the session keeps running when your client detaches. Read GET /api/browser/:id/status to tell them apart.

A 404 on reconnect usually means the id came from the CDP URL. Reconnect takes the x-session-id value. Close and status accept either id.

The browser runs on Rayobyte infrastructure and is reached over CDP. There is no browser to install.