Seems like hotfix is on the way!
Where did you hear that?
+1, our CI/CD is blocked by this
Same issue
Thank you again for the reports.
We are currently rolling back a change that we believe is causing the issue. We will keep you updated.
https://status.sonarqube.com/ has also been updated (and will be updated as the situation progresses)
4 Likes
I want to note that this seems to affect the website as well as the CI. Changing the status of an issue kicks me back to the login page, no matter how many times I try.
Same issue on the bitbucket as well.
Same here, our CI/CD is blocked because of this.
Might be the same as this issue?
SonarQube Cloud Authentication Issues - SonarQube Cloud - Sonar Community
We have confirmed that the rollback fixes the issue and are proceeding with deploying to production. Thank you for your patience.
4 Likes
The deployment has been completed on our EU instance. Deployment for our US-based instance should complete within the next 10 minutes. We are continuing to monitor the situation, but token generation and analysis now appear to be successful again.
1 Like
I can confirm it works now.
Not resolved for us…. How long does it take?
@AGo It should all be fixed now. What symptoms are you experiencing?
sonar-scanner
13s
+ sonar-scanner
11:07:57.301 INFO Scanner configuration file: /opt/sonar-scanner/conf/sonar-scanner.properties
11:07:57.306 INFO Project root configuration file: /opt/atlassian/pipelines/agent/build/sonar-project.properties
11:07:57.323 INFO SonarScanner CLI 7.1.0.4889
11:07:57.324 INFO Java 17.0.14 Amazon.com Inc. (64-bit)
11:07:57.325 INFO Linux 6.1.79 amd64
11:07:57.371 INFO User cache: /opt/sonar-scanner/.sonar/cache
11:07:58.402 INFO Communicating with SonarQube Cloud
11:07:58.403 INFO JRE provisioning: os[linux], arch[x86_64]
11:08:01.531 INFO Starting SonarScanner Engine...
11:08:01.532 INFO Java 17.0.11 Eclipse Adoptium (64-bit)
11:08:02.596 INFO Load global settings
11:08:03.090 INFO Load global settings (done) | time=494ms
11:08:03.093 INFO Server id: 1BD809FA-AWHW8ct9-T_TB3XqouNu
11:08:03.310 INFO Loading required plugins
11:08:03.311 INFO Load plugins index
11:08:03.476 INFO Load plugins index (done) | time=165ms
11:08:03.477 INFO Load/download plugins
11:08:04.185 INFO Load/download plugins (done) | time=709ms
11:08:04.581 INFO Found an active CI vendor: 'Bitbucket Pipelines'
11:08:05.034 INFO No project and organization key detected from Bitbucket Cloud Pipelines.
11:08:05.037 INFO Load project settings for component key: '#####undisclosed######-service'
11:08:05.418 INFO Process project properties
11:08:05.424 INFO Execute project builders
11:08:05.425 INFO Execute project builders (done) | time=1ms
11:08:05.427 INFO Project key: #####undisclosed######-service
11:08:05.428 INFO Base dir: /opt/atlassian/pipelines/agent/build
11:08:05.428 INFO Working dir: /opt/atlassian/pipelines/agent/build/.scannerwork
11:08:05.432 INFO Load project branches
11:08:05.896 INFO Load project branches (done) | time=463ms
11:08:05.898 INFO Check ALM binding of project '#####undisclosed######-service'
11:08:06.096 INFO Detected project binding: NONEXISTENT
11:08:06.096 INFO Check ALM binding of project '#####undisclosed######-service' (done) | time=198ms
11:08:06.097 INFO Load project pull requests
11:08:06.410 INFO Load project pull requests (done) | time=312ms
11:08:06.411 INFO Load branch configuration
11:08:06.412 INFO Detected analysis for pull request '24' targeting 'main'
11:08:06.413 INFO Auto-configuring pull request 24
11:08:06.435 ERROR Could not find a default branch for project with key '#######undisclosed#######-service'. Make sure project exists.
11:08:06.758 INFO EXECUTION FAILURE
11:08:06.760 INFO Total time: 9.464s
of course, the project exists. Also, the project has a main branch (‘main’)
This started in all our repos. Which were working fine before.
Do you have an example from just now? 11:08am was when the incident was in progress.
That’s an interesting hint..
The pipelines I’m running just right now (over and over).
I’m checking, why logs are not updating.
Yes, our tokens are working again, in west-europe region.
Thanks for you quick action on this tough blocker!
No, still no luck.
Timestamps are UTC, but I’m in UTC+2. So, the logs are always up-to-date. But I’m still seeing this error.
And there were no failures prior to about 2 hours ago? I’m trying to judge if this is the same issue, or simply a different issue that produces the same error message.
The first time we were seeing this (in all our pipelines) was today 10:33 am (UTC+2). Approx 30 min before this post. All our repos/pipelines have the same error. Before that, no pipeline has ran. the last (proven) successful pipeline ran Sep 30, 2025 01:03 am (UTC+2).