> 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-for-visual-studio/connect-your-ide/advanced-configuration.md).

# Advanced configuration

## HTTP configuration <a href="#http-configuration" id="http-configuration"></a>

To operate, SonarQube for Visual Studio needs to perform HTTP requests, especially in [Connected mode](/sonarqube-for-visual-studio/connect-your-ide/connected-mode.md). While SonarQube for Visual Studio will work out-of-the-box in most situations, some network infrastructure may require a custom configuration.

## Proxy configuration

When connecting to a SonarQube instance running behind a proxy, SonarQube for Visual Studio will use the your Windows-defined proxy settings. See the [Microsoft documentation](https://support.microsoft.com/en-us/windows/use-a-proxy-server-in-windows-03096c53-0554-4ffe-b6ab-8b1deee8dae1) for more information about setting up a proxy server connection.

## Manage your configuration <a href="#manage-your-configuration" id="manage-your-configuration"></a>

### Server SSL certificates <a href="#server-ssl-certificates" id="server-ssl-certificates"></a>

When encountering an untrusted certificate, SonarQube for Visual Studio will inform the user with a notification that *the server certificate can not be verified*.

<div align="left"><img src="/files/V9I9eXjyh75NnjiATavP" alt="SonarQube for Visual Studio will provide a gold bar notification if your certificate cannot be verified." width="563"></div>

The `truststore.p12` is expected to be found in the default location as listed below; add it manually if it doesn’t exist. Here is an example command that might work for your configuration:

```bash
keytool -import -trustcacerts -keystore ~/.sonarlint/ssl/truststore.p12 -storepass sonarlint -noprompt -file <YOUR_CERTIFICATE_NAME.cer>
```

**TrustStore**

**sonarlint.ssl.trustStorePath**

Path to the keystore used by SonarLint to store custom trusted server certificates

**default**: `~/.sonarlint/ssl/truststore.p12`

**sonarlint.ssl.trustStorePassword**

Password of the truststore.

**default**: `sonarlint`

**sonarlint.ssl.trustStoreType**

The format of the keystore file is found in the Oracle documentation.

**default**: `PKCS12`

If you're having troubles connecting to the server due to SSL/TLS errors, see the [Troubleshooting](/sonarqube-for-visual-studio/resources/troubleshooting.md#ssl-tls-errors) troubleshooting article.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-for-visual-studio/connect-your-ide/advanced-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.