> 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/securing-behind-proxy.md).

# Securing behind a proxy

It is recommended to run SonarQube Server 2026.4 behind a proxy, if it should be accessible from outside.

As a Data Center Edition subscriber, Sonar will assist with the setup and configuration of your cluster. Get in touch with your account manager to receive appropriate onboarding resources.

With the Data Center Edition, you’ll need a load balancer to balance HTTP requests (load) between the application nodes configured in the cluster (see also [Installation requirements](/sonarqube-server/2026.4/server-installation/data-center-edition/installation-requirements.md#load-balancer)). You can configure the load balancer as a reverse proxy. See [Reverse proxy and network security](/sonarqube-server/2026.4/server-installation/network-security/securing-behind-proxy.md).

If you deploy SonarQube on Kubernetes, you’ll need an ingress controller. An ingress controller is a specialized load balancer for Kubernetes that acts as a reverse proxy and manages traffic routing to services within the Kubernetes cluster. See [Customizing Helm chart](/sonarqube-server/2026.4/server-installation/on-kubernetes-or-openshift/customizing-helm-chart.md#ingress).

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

* [Elasticsearch security features](/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/elasticsearch-security-features.md)
* [Network rules](/sonarqube-server/2026.4/server-installation/data-center-edition/network-security/network-rules.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/securing-behind-proxy.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.