Unable to configure DevOps Platform Integration for GitHub in projects

Hi Everyone,

SonarQube server (Developer license). The Devops Platform Integration for GitHub fails to contact GitHub when in Project Settings → General Settings → DevOps Platform Integration. At the SonarQube Administration level configuration, the check configuration succeeds. The credentials have been repeatedly checked and are all correct.

SonarQube server log excerpt:
“”
2026.10.28 13:58:19 DEBUG web[4c6ebb1f-13c0-48d4-ad92-0b11b2f8ecc0][o.s.w.c.OkHttpClientBuilder] → GET https://api.github.com/repos/<co. name>/ACloud

2026.10.28 13:58:20 WARN web[4c6ebb1f-13c0-48d4-ad92-0b11b2f8ecc0][o.s.a.c.GenericApplicationHttpClient] GET response did not have expected HTTP code (was 401): {\r\n “message”: “Bad credentials”,\r\n “documentation_url”: "https://docs.github.com/rest",\r\n “status”: “401”\r\n}
“”

  • SonarQube Server V2026.5.3

  • The GitHub code repositories are all of type “private”.

  • Repositories added in the past are still working for PR decoration - indicating again that the credentials are correct. But removing an already added repository and then trying to readd it fails.

  • Successful global configuration validation in “Administration”.

  • In project configuration of “DevOps Platform Integration”, it fails when “Save” is clicked with:
    GitHub response: GET /repos/<co. name>/ACloud but response (401 Bad credentials)
    All credentials confirmed correct. When invalid credentials input, it fails global configuration validation in “Administration”.

The Git Hub app has the following permissions:

Repository permissions:
Checks: Read/Write
Commit statuses: Read
Contents: Read
Metadata: Read
Pull requests: Read/Write

Organisation permissions:
Members: Read
Projects: Read

Account permissions:
Email Addresses: Read

Must-share information (formatted with Markdown):

  • which versions are you using ( Versionv2026.5.3 (133540)
  • how is SonarQube deployed: As a container under AWS Fargate

Thanks

Hey @PabPsion, it sound very similar to this other issue. Could you try the workaround I described there and let me know if that solves it?

Hi @andres that workaround worked. Thanks for the help!