Download Log in Sign up

Help center / Engines

Installed Chrome needs a logged-in desktop session

Why Installed Chrome profiles refuse to start over SSH, in the background or headless.

Google Chrome encrypts saved cookies with the operating system's keychain (macOS Keychain, or Windows data protection). That is only available inside a logged-in desktop session. Started from SSH or a background service, Chrome could not read or save logins, so Browz refuses instead.

  1. The message is: Installed Chrome requires a macOS desktop session. Open Browz from the logged-in desktop. The Windows message ends with Windows data protection is unavailable.
  2. Open Browz from the desktop of the user who owns the profiles, on that computer, and start the profile there.
  3. A headless start is refused with: Installed Chrome backend currently requires a visible desktop session. Use a visible window, or use the Browz engine for headless automation.

Still stuck? Export diagnostics and contact support.