Skip to main content
Custom proxies allow you to use your own proxy servers with Kernel browsers. This is useful when you have existing proxy infrastructure or specific proxy requirements not covered by Kernel’s managed options.

Configuration

HTTP and HTTPS proxies are supported for custom proxy configurations. If no protocol is specified, HTTPS is used by default.
Specify the host, port, and optional authentication credentials for your proxy server:

Configuration Parameters

  • host (required) - Proxy server hostname or IP address
  • port (required) - Proxy server port (1-65535)
  • username - Username for proxy authentication
  • password - Password for proxy authentication (minimum 5 characters)
  • ca_bundle (optional) - PEM-encoded CA certificate bundle to trust when the proxy terminates and re-signs upstream TLS (MITM). May contain multiple certificates and is limited to 64 KiB.
  • bypass_hosts (optional) - Array of hostnames that bypass the proxy and connect directly (max 100 entries)
When creating a proxy with authentication, provide the password. The API response will only indicate if a password exists (has_password: true) but won’t return the actual password for security reasons.

MITM TLS

If your custom proxy terminates TLS and re-signs upstream connections, provide its CA certificate bundle in config.ca_bundle when you create the proxy. Kernel validates the bundle and installs it in the browser’s trust store when you create a browser with that proxy. The bundle must contain one or more PEM-encoded CA certificates. It is write-only: proxy responses return has_ca_bundle: true instead of the certificate contents. You must bind a proxy with a CA bundle when creating the browser; you can’t hot-swap it onto a running browser.

Bypass hosts

Configure specific hostnames to bypass your custom proxy:
This is useful for accessing internal services or metadata endpoints without routing through your proxy. See the overview for full bypass host rules.