More than a year later, I finally found the source of the problem. It did indeed come from Sonar and not Jenkins (a configuration in Sonar, more precisely), as I explained several times. A proxy was configured in Sonar. And access to Jenkins was blocked by the proxy. I set “https.nonProxyHosts” in sonar.properties and it’s OK now.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Troubleshooting SonarQube unsuccessful webhook POSTs to Jenkins | 3 | 3491 | August 4, 2020 | |
| SonarQube webhook to Jenkins not working | 2 | 4584 | October 7, 2019 | |
| Getting 403 status code when webhook is triggered from sonarcloud to jenkins | 2 | 657 | August 25, 2023 | |
| Sonarqube webhook response 404 | 5 | 857 | June 27, 2022 | |
| SonarQube connection issue | 2 | 318 | March 22, 2023 |