# Certificate error when running SonarQubePrepare in azure devops

**URL:** <https://community.sonarsource.com/t/certificate-error-when-running-sonarqubeprepare-in-azure-devops/131658>\
**Category:** SonarQube Server / Community Build\
**Tags:** azuredevops-services\
**Created:** [December 5, 2024, 11:38am UTC](https://community.sonarsource.com/t/certificate-error-when-running-sonarqubeprepare-in-azure-devops/131658 "2024-12-05T11:38:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robin\_Clark](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/robin_clark/32/64789_2.png) [@Robin\_Clark](https://community.sonarsource.com/u/Robin_Clark)\
**Post date:** [December 5, 2024, 11:38am UTC](https://community.sonarsource.com/t/certificate-error-when-running-sonarqubeprepare-in-azure-devops/131658/1 "2024-12-05T11:38:52Z")

</div>

We have a number of sonarqube projects that use azure devops and the SonarQubePrepare step. Most of these work fine.  
However I added a new project, generated a project key and re-used an existing working service connection, but the pipeline fails with this error:

```auto
##[error][ERROR] SonarQube Server: Error while executing task Prepare: API GET '/api/server/version' failed. Error message: unable to get local issuer certificate.
##[error]API GET '/api/server/version' failed. Error message: unable to get local issuer certificate.

```

Anyone have any ideas? Its strange that this new project fails when all others are working

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [December 6, 2024, 5:42pm UTC](https://community.sonarsource.com/t/certificate-error-when-running-sonarqubeprepare-in-azure-devops/131658/2 "2024-12-06T17:42:39Z")

</div>

Hi,

Welcome to the community!

To confirm, you’re using an exact copy of a working pipeline, with just things like the project key & name changed?

Is this project’s job running on a build agent that hasn’t handled analysis before?

To be clear, this is an SSL error that has to do with the JRE analysis is running with not trusting your (self-signed?) certificates. Have you explicitly provided Java on your build agents, or are you allowing the scanner to provide its own version? If the former, here are [the docs](https://docs.sonarsource.com/sonarqube-server/10.6/analyzing-source-code/various-setups/manage-tls-certificates/) on setting up analysis with the certificate.

&nbsp;  
HTH,  
Ann