> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/network-rules.md).

# Network rules

Defining network rules to enhance the security in SonarQube Server 2026.4.

To further lock down the communication in between the nodes in your SonarQube Server cluster, you can define the network rules. The setup depends on the installation type.

<table><thead><tr><th width="95">Protocol</th><th width="134">Source</th><th width="132">Destination</th><th width="288">Port</th><th>Default</th></tr></thead><tbody><tr><td>TCP</td><td>Reverse Proxy</td><td>App Node</td><td><code>sonar.web.port</code></td><td>9000</td></tr><tr><td>TCP</td><td>App Node</td><td>Search Node</td><td><code>sonar.cluster.node.search.port</code></td><td>9001</td></tr><tr><td>TCP</td><td>Search Node</td><td>Search Node</td><td><code>sonar.cluster.node.es.port</code></td><td>9002</td></tr><tr><td>TCP</td><td>App Node</td><td>App Node</td><td><code>sonar.cluster.node.port</code></td><td>9003</td></tr></tbody></table>

You can further segment your network configuration if you specify a frontend, a backend and a search network:

<table><thead><tr><th width="112">Network</th><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Frontend</td><td><code>sonar.web.host</code></td><td>Frontend HTTP Network</td></tr><tr><td>Backend</td><td><code>sonar.cluster.node.host</code></td><td>Backend App to App Network</td></tr><tr><td>Backend</td><td><code>sonar.cluster.search.hosts</code></td><td>Backend App to Search Network</td></tr><tr><td>Search</td><td><code>sonar.cluster.node.search.host</code></td><td>Backend Search to Search Network</td></tr></tbody></table>

For information about the parameters, see [List of DCE-specific properties](/sonarqube-server/2026.4/server-installation/system-properties/dce-specific.md).

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Securing behind a proxy](/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/securing-behind-proxy.md)
* [Elasticsearch security features](/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/elasticsearch-security-features.md)


---

# 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://docs.sonarsource.com/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/network-rules.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.