Couldn't add a repo or see existing repo after upgrading to a new plan

SonarQube Cloud
1
  • ALM used GitHub
  • CI system used Github Actions
  • Scanner command used when applicable - using sonarqube/actions
  • Languages of the repository - Any language

In the sonarcloud console we are even getting a 403 error and in the Github Apps if we select All Repositories it is loading for sometime and getting timeout error
Note: Our repository count is huge say 2 lakhs almost.

2

I recently upgraded my SonarCloud account from an older plan to the Team Plan. After this change, the SonarCloud integration in my GitHub Actions workflow stopped working.

Error in GitHub Actions:

Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) 
on project iamneo-production_xxx: Project not found. 
Please check the 'sonar.projectKey' and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, 
or contact the project administrator to check the permissions of the user the token belongs to

Current setup:

  • The sonar.projectKey, sonar.organization, and SONAR_TOKEN values are all correct and unchanged.
  • This same configuration worked fine before the plan upgrade.
  • The GitHub Action uses a token from secrets and passes it into Maven correctly.

What I’m seeing now:

  1. Previously accessible project reports are no longer available.
    Attempting to open them shows this message:

The requested project does not exist, or you have not authenticated with SonarQube Cloud.

  1. API errors when accessing organization info:
  • https://sonarcloud.io/api/organizations/search?organizations=iamneo-production → returns 500
  • https://sonarcloud.io/api/navigation/organization?organization=iamneo-production → returns 403 Forbidden
  1. Issues in SonarCloud GitHub App settings:
    The GitHub App config page on SonarCloud hangs when saving changes. On refresh, it sometimes looks like the setting was applied, but the page often crashes or freezes.

Need help with:

  • Regaining access to the iamneo-production organization
  • Restoring visibility to the existing projects
  • Or confirmation that the org/project needs to be recreated under the new plan
3

Hello,

We’ve noticed some activity from your organization that was flagged as excessive and potentially abusive, resulting in a block on your organization. Please contact us to discuss the situation.

Thank you.

1 Like