Jenkins Bitbucket HTTPs Problem with bitbucket plugin

[CI User]

I set global credential in Jenkins with client id and secret from bitbucket. I'm running 

Multibranch Pipeline.
till yesterday things works fine by running clone from my build process.
Starting from today I'm getting error 128 

returned status code 128:
stdout: 
stderr: remote: You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.
fatal: Authentication failed for 'https://bitbucket.org

nothing changed from my side, any input ?  thanks

[Viswanathan Ramachandran]

This is an authentication problem, the likely cause is Bitbucket Cloud’s migration away from App Passwords: existing App Passwords stopped working on June 9, 2026. 

Also, a Bitbucket OAuth client ID + client secret is not automatically valid as Git HTTPS clone credentials. For Multibranch Pipeline, make sure the credentials used for the actual checkout are configured separately and are valid for Git.

Try these

1. Create a Bitbucket API token (or repository/workspace access token) with repository read permission.
2. In Jenkins credentials, update the new details
3. In the Multibranch Pipeline’s branch source configuration, select that credential for checkout/discovery.
4. Save and run Scan Multibranch Pipeline. If needed, discard the affected workspace once so an old cached credential cannot interfere.

For a repository access token, use username x-token-auth instead. Do not use the token label, client ID, or client secret as the Git username/password pair.

Bitbucket’s current guidance confirms API tokens are the replacement for App Passwords and require repository read scope for cloning: Atlassian API-token guidance, App Password retirement notice.