---
title: "Endpoint Configuration (manual)"
slug: "configure-an-endpoint-to-work-with-verax-protect"
updated: 2026-05-19T10:34:32Z
published: 2026-05-19T10:34:32Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.verax.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Endpoint Configuration (manual)

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?**](/v1/docs/installing-verax-ca-certificate#windows-–-install-the-verax-ca-certificate)

---

### 2. Configure Traffic Redirection

Follow the instructions here: 👉 [**How do I edit the hosts file for Verax Protect?**](/v1/docs/editing-the-hosts-file-for-verax-protect#windows)

---

### 3. Flush DNS Cache (Recommended)

After updating the hosts file, flush DNS:

```plaintext
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?**](/v1/docs/installing-verax-ca-certificate#macos-–-install-the-verax-ca-certificate)

---

### 2. Configure Traffic Redirection

Follow the instructions here: 👉 [**How do I edit the hosts file for Verax Protect?**](/v1/docs/editing-the-hosts-file-for-verax-protect#macos)

---

### 3. Flush DNS Cache

After updating the hosts file:

```plaintext
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:

```plaintext
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