> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/setup/prerequisites/firewall-ports.md).

# Firewall ports

This page provides an overview of the network ports required by **StifleR**, **DeployR**, and related components, including **ActionHub**, **Beacon**, **CacheR**, and **StifleR MOM**. It describes the ports used by each component, including the communication direction, protocol, and whether the port can be customized.

For **BranchCache-specific firewall requirements**, see the tables at the end of this page.

## StifleR Service (Server)

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description                                         |
| -------- | ---------- | ----------- | ------------ | --------------------------------------------------- |
| TCP      | 1414       | Any         | No           | SignalR endpoint — client and service communication |
| TCP      | 9000       | Any         | Yes          | Web Service REST API                                |

{% hint style="info" %}
Rules for ports 1414 and 9000 are created automatically when **"Configure SignalR firewall rules automatically"** and **"Configure Web Service firewall rules automatically"** are enabled (default: enabled).
{% endhint %}

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description                                        |
| -------- | ---------- | ----------- | ------------ | -------------------------------------------------- |
| TCP      | Any        | 3268        | No           | Global catalog LDAP                                |
| TCP      | Any        | 443         | No           | HTTPS dashboard                                    |
| TCP      | Any        | 4022        | Yes          | SQL Server Service Broker (only if SQL is enabled) |
| TCP      | Any        | 1433        | Yes          | SQL Server service (only if SQL is enabled)        |

{% hint style="info" %}
Port 443 is only required if the Dashboard is hosted in **IIS** and bound to port 443. If you're using the **built-in web server** (available from StifleR 3.1 onward), the Dashboard is reachable over port 9000 instead, and opening 443 is optional.
{% endhint %}

***

## StifleR Client

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description              |
| -------- | ---------- | ----------- | ------------ | ------------------------ |
| TCP      | 1337       | Any         | Yes          | Peer data                |
| TCP      | 1338       | Any         | Yes          | Proxy data               |
| TCP      | 1337, 1339 | Any         | Yes          | Peer data (Green leader) |
| UDP      | 3702       | Any         | Yes          | Peer probes              |
| UDP      | 3703       | 3703        | Yes          | Blue leader probe port   |
| UDP      | 5353       | 5353        | No           | mDNS                     |

{% hint style="info" %}
**Port 9000 should not be opened for incoming traffic on the client** — there is no StifleR Server API listener running on the client.
{% endhint %}

### Outgoing

<table data-search="false"><thead><tr><th>Protocol</th><th>Local Port</th><th>Remote Port</th><th>Customizable</th><th>Description</th></tr></thead><tbody><tr><td>TCP</td><td>Any</td><td>1337</td><td>Yes</td><td>Request peer data</td></tr><tr><td>TCP</td><td>Any</td><td>1338</td><td>Yes</td><td>Proxy data</td></tr><tr><td>TCP</td><td>Any</td><td>1337, 1338, 1339</td><td>Yes</td><td>Peer data</td></tr><tr><td>UDP</td><td>3702</td><td>Any</td><td>Yes</td><td>Peer probes</td></tr><tr><td>UDP</td><td>5353</td><td>Any</td><td>No</td><td>mDNS</td></tr><tr><td>TCP</td><td>Any</td><td>1414</td><td>No</td><td>StifleR Service communication</td></tr><tr><td>TCP</td><td>Any</td><td>1415</td><td>No</td><td>Action Hub communication</td></tr><tr><td>TCP</td><td>Any</td><td>9000</td><td>No</td><td>StifleR Server access via browser</td></tr><tr><td>TCP</td><td>Any</td><td>5200</td><td>Yes</td><td>Beacon — Fast TCP ping</td></tr><tr><td>UDP</td><td>Any</td><td>5201</td><td>Yes</td><td>Beacon — iPerf3</td></tr></tbody></table>

***

## Action Hub

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description |
| -------- | ---------- | ----------- | ------------ | ----------- |
| TCP      | 1415       | Any         | Yes          | Action Hub  |

***

## Beacon

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description   |
| -------- | ---------- | ----------- | ------------ | ------------- |
| TCP      | 5200       | Any         | Yes          | Fast TCP ping |
| TCP      | 5201       | Any         | Yes          | iPerf3        |
| UDP      | 5201       | Any         | Yes          | iPerf3        |

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description                                           |
| -------- | ---------- | ----------- | ------------ | ----------------------------------------------------- |
| TCP      | Any        | 9000        | Yes          | StifleR Server API — required for Beacon registration |

***

## WMI Agent

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description                                    |
| -------- | ---------- | ----------- | ------------ | ---------------------------------------------- |
| TCP      | Any        | 9000        | Yes          | StifleR Server API — required for registration |

***

## CacheR

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description |
| -------- | ---------- | ----------- | ------------ | ----------- |
| TCP      | 9050       | Any         | Yes          | CacheR API  |

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description                                                                                    |
| -------- | ---------- | ----------- | ------------ | ---------------------------------------------------------------------------------------------- |
| TCP      | Any        | 9050        | Yes          | CacheR WebAPI — only required if the CacheR Worker runs on a separate host from the CacheR API |

***

## DeployR Server

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description     |
| -------- | ---------- | ----------- | ------------ | --------------- |
| TCP      | 7281, 7282 | Any         | Yes          | DeployR service |

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description        |
| -------- | ---------- | ----------- | ------------ | ------------------ |
| TCP      | Any        | 9000        | Yes          | StifleR Server API |

***

## StifleR MOM

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description     |
| -------- | ---------- | ----------- | ------------ | --------------- |
| TCP      | 8088       | Any         | Yes          | Explicit proxy  |
| TCP      | 8089       | Any         | Yes          | HTTP downloader |

***

## BranchCache

### Incoming

| Protocol | Local Port | Remote Port | Customizable | Description        |
| -------- | ---------- | ----------- | ------------ | ------------------ |
| TCP      | 1337       | Any         | Yes          | Content retrieval  |
| TCP      | 1339       | Any         | Yes          | Hosted cache       |
| TCP      | 443        | Any         | Yes          | Hosted cache HTTPS |
| UDP      | 3702       | Any         | No           | Peer discovery     |

### Outgoing

| Protocol | Local Port | Remote Port | Customizable | Description       |
| -------- | ---------- | ----------- | ------------ | ----------------- |
| TCP      | Any        | 1337        | Yes          | Content retrieval |
| TCP      | Any        | 1339, 443   | Yes          | Hosted cache      |
| UDP      | Any        | 3702        | No           | Peer discovery    |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/stifler/setup/prerequisites/firewall-ports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.