Issue when change PAT for gitlab "Update token"

SonarQube Cloud
1

I try to update my gitlab personal access token to sonarqube.

When I click on “Update token”, I have this error message: “Failed to get Gitlab namespace 404“…

My namespace exists in gitlab, and it works well until 10/01/2026.

What can I do to fix this issue ?

2

Hi,

Welcome to the community and thanks for this report!

Are you still experiencing this?

Are there any errors in your browser console or is it just a repeat of the error you’ve already reported?

Could you provide a screenshot, redacted as necessary?

 
Thx,
Ann

3

Hi Ann,

Thanks for your answer.

Yes, we are still facing the issue.

In my console browser, I have:

I attach a screen shot.

Notes:

  • I try outside of my enterprise network but I have same issue.
  • I try call directly with curl without success (same response).

Capture d’écran 2026-01-21 à 11.27.12
Capture d’écran 2026-01-21 à 11.27.121920×891 265 KB

4

Hi,

Going back to your original message, you say the problem started on 10 January, right? (Sorry, I’m American; I have to confirm your date isn’t 1 Oct. :sweat_smile:)

So you tried to update your token on the 10th and that’s when the problems started? What prompted you to update your token? Because it seems that at root you have a permissions problem on the GitLab side. Can you check with your GitLab admins to make sure your permissions haven’t changed from what you expect?

 
Ann

5

Hey,

You are right the problem started from 10th january 2026 (not 1st october 2026 :smiley:).

The sonar scanner in gitlab pipeline stop working for branch and MR (but works on main branch).

We have this kind of error:

$ sonar-scanner
09:15:02.830 INFO  Load branch configuration
09:15:02.841 INFO  Auto-configuring pull request 1231
....
09:15:03.288 ERROR 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
09:15:03.666 INFO  EXECUTION FAILURE
09:15:03.668 INFO  Total time: 12.868s

I just contact my admin gitlab and you are right, I’m not admin of the root group of our organization. It explains the 404 namespace not found. With the admin right it works as expected.

Thanks a lot four your help and have a nice days :wink:

Xavier

1 Like