Endpoint Configuration (manual)

Prev Next

This guide outlines the required steps to configure a Windows or macOS device to work with Verax Protect.

Verax requires:

  1. Installation of the Verax CA certificate

  2. Configuration of traffic redirection

  3. (macOS only) Additional configuration for certain development tools

Detailed OS-specific instructions are linked below.


Before You Begin

From your Verax Protect console, retrieve:

  • The Verax CA certificate (verax_ca.crt)

  • The traffic redirect entries

You can find both under:

Settings → Traffic Redirect → Web Proxy


Windows Configuration

To configure a Windows device:

1. Install the Verax CA Certificate

Follow the instructions here:
👉 How do I install the Verax CA certificate?


2. Configure Traffic Redirection

Follow the instructions here:
👉 How do I edit the hosts file for Verax Protect?


After updating the hosts file, flush DNS:

ipconfig /flushdns


Windows setup is complete.


macOS Configuration

To configure a macOS device:

1. Install the Verax CA Certificate

Follow the instructions here:
👉 How do I install the Verax CA certificate?


2. Configure Traffic Redirection

Follow the instructions here:
👉 How do I edit the hosts file for Verax Protect?


3. Flush DNS Cache

After updating the hosts file:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

4. Claude Code (macOS Only)

If you are using Claude Code on macOS, Node.js must be configured to trust the Verax CA certificate.

After placing verax_ca.crt locally on your Mac, run:

export NODE_EXTRA_CA_CERTS=/path/to/verax_ca.crt

Replace /path/to/verax_ca.crt with the full path to the certificate file.

To make this persistent, add the export line to your shell profile (for example ~/.zshrc).


Verification

After completing configuration:

  1. Open an AI tool (ChatGPT, Claude, Copilot).

  2. Send a test request.

  3. Confirm the activity appears in the Interactions dashboard in your Verax Protect console.

If activity does not appear, verify:

  • The CA certificate is trusted

  • The hosts file entries are correct

  • DNS cache has been flushed