> 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/networking-requirements.md). # Networking requirements This page contains relevant information related to SonarQube Server's networking requirements. This page is for SonarQube Server 2026.4. ## Network topology The diagram below shows the network topology for SonarQube Server: * The DevOps platform, the SonarScanner, the user (Web browser), the IDE in connected mode, and any other external system, will connect to SonarQube through the Web API. You must use a reverse proxy if you want to use HTTS. * An external Identity Provider (other than GitHub, Bitbucket Cloud, or GitLab) can be used with one of the following authentication methods: OAuth, LDAP, SAML, or OpenID. * SonarQube connects to its database through JDBC. * SonarQube authenticates to the DevOps platform via OAuth and sends the quality gate status report via HTTP(S). * SonarQube sends quality gate webhooks to the CI/CD platform via HTTP(S).
SonarQube Server topology network
{% hint style="info" %} The CI platform may be integrated into the DevOps platform. {% endhint %} ## SonarQube base URL The SonarQube base URL needs to be a public URL if SonarQube expects to receive information from an external system. This is relevant if: * You use SCIM (since it requires SonarQube to be reachable by the Identity Provider). * You use Cloud-hosted CI pipelines. ## HTTPS For most production instances, traffic encryption (and therefore HTTPS) is required. As SonarQube only supports plain HTTP for inbound traffic, a reverse proxy is necessary to terminate SSL/TLS encryption before SonarQube. For more information, see [Reverse proxy and network security](/sonarqube-server/2026.4/server-installation/network-security/securing-behind-proxy.md). ## Network rules You can define network rules to enhance the network security. For more information, see [Network rules](/sonarqube-server/2026.4/server-installation/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/networking-requirements.md?ask=&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.