Teamcity, sonarqube error - javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.secu

Must-share information (formatted with Markdown):

  • I am using Developer Version: 10.0.0.68432
  • SonarQube hosted on Azure Cloud using Linux App Service plan via docker container
  • I am trying to Run SonarScanner in teamcity suing Dotnet SonarScanner
  • I have tried all the options but its not working



Hi,

Welcome to the community!

This is an SSL certificate problem. Are you using a self-signed certificate? It’s really not recommended. If you’re not, this thread may help.

 
Ann

Thanks for the reply G Ann Campbell- my issue is littlebit different than you sahred, I am not using Azure devops but i am hosting my sonarqube instance along with its postgreys backend in Azure

my Ci tool is teamcity from where I am trying to run following 2 steps in teamcity which both are failing with diferent error

Step which i prefered for my ci is as follows with following code

dotnet tool install --global dotnet-sonarscanner
dotnet sonarscanner begin /k:"test" /d:sonar.host.url="https://int-bbc-studios-sonarqube-appservice.azurewebsites.net/"  /d:sonar.login="<my token>" /d:sonar.cs.opencover.reportsPaths=coverage.xml  /v:%dep.ContentCortexSubscriber_BuildUnitTestReleaseAcceptanceTests.build.number%
dotnet build 
& C:\Users\teamcitybuildagent\.dotnet\tools\.store\opencover\OpenCover.Console.exe -target:"dotnet.exe"  -targetargs:"test --no-build" -returntargetcode   -output:coverage.xml    -register:user
dotnet sonarscanner end /d:sonar.login="<my token>"

if I try runing above steps I get error as below



Another step which i am trying with below code

dotnet tool install --global dotnet-sonarscanner
dotnet sonarscanner begin /k:"test" /d:sonar.host.url="https://int-bbc-studios-sonarqube-appservice.azurewebsites.net"  /d:sonar.token="<my token>"
dotnet build
dotnet sonarscanner end /d:sonar.token="<my token>"

If I try above step, I get error message as

Hi,

There’s a lot going on here; you’ve now reported 3 different errors. The first is an SSL problem. The second looks like DNS or proxy configuration on your side. The third indicates a problem with the analysis token. You should double-check that it’s valid and consider re-generating it.

 
HTH,
Ann