Could not get projects from GitLab instance - GitLab project onboarding

SonarQube Cloud
, , ,
1

Good day,

What is failing?

I am trying to onboard a new project form Gitlab. But it keeps failing even when the Gitlab Access token that I use has all the permissions available.

What is expected?

To successfully onboard the project from Gitlab.

Observations

So far I have made sure of the following.

  1. My Gitlab legacy token has all the permissions selected during creation. And it is not expired.
  2. I am a Developer role bearer in the project, so I hope that it is sufficient.
  3. My SonarQube instance version is `Developer Edition v2026.3.1 (123439)` and it is currently a supported version.
  4. The error is a 500 error from Gitlab.
  5. I went through related issues but no help. Marked as resolved/closed but seems like it still is there.
    1. Importing GitLab projects fails to connect - #7 by Joe
    2. Internal Server Error 500 when a request with pagination size under 12 on Gitlab.com (#334667) · Issues · GitLab.org / GitLab · GitLab

I have attached relevant screenshots, logs below. Do let me know if there is anything that I am doing wrong, or we just have to wait until this is fixed. Thanks in advance.

Screenshot from the SonarQube UI

Screenshot 2026-07-15 at 13.20.01
Screenshot 2026-07-15 at 13.20.011920×928 93.3 KB

SonarQube web log

2026.07.14 22:10:21 DEBUG web[e2b57d58-bde5-4840-b516-f4c9a7185bd1][o.s.w.c.OkHttpClientBuilder] <-- 500 https://gitlab.com/api/v4/projects?archived=false&simple=true&membership=true&order_by=name&sort=asc&search= (15573ms, 39-byte body)
2026.07.14 22:10:21 ERROR web[e2b57d58-bde5-4840-b516-f4c9a7185bd1][o.s.a.c.g.GitlabApplicationClient] Gitlab API call to [https://gitlab.com/api/v4/projects?archived=false&simple=true&membership=true&order_by=name&sort=asc&search=] failed with 500 http code. gitlab response content : [{"message":"500 Internal Server Error"}]

Edit:

Observed that this fails by debugging in the SonarQube instance.

curl -i   --header "PRIVATE-TOKEN: <TOKEN>"   "https://gitlab.com/api/v4/projects?archived=false&simple=true&membership=true&order_by=name&sort=asc&search="

while this passes.

curl -i   --header "PRIVATE-TOKEN: <TOKEN>"   "https://gitlab.com/api/v4/projects?archived=false&simple=true&membership=true&sort=asc
&search="

The difference is order_by=name query parameter.

2

Hey @Buddhi_Vikasitha, welcome to Community! I was able to reproduce the issue. I think this is a problem on GitLab’s side, and in fact I found an issue about this in GitLab’s issue tracker. I have joined the thread, hopefully they will react soon.

10

Hey @Buddhi_Vikasitha, so far GitLab still hasn’t addressed this issue, but one of my colleagues came up with a workaround and posted it on the GitLab thread. I suggest you give it a try if you want to unblock your project creation, as it doesn’t seem like GitLab is very responsive with this issue.