Community
Q&A
Bitbucket
Questions
CHANGE-3222 - Functionality has been deprecated

CHANGE-3222 - Functionality has been deprecated

remote: CHANGE-3222 - Functionality has been deprecated
remote: App passwords are deprecated and must be replaced with API tokens.
remote: https://developer.atlassian.com/cloud/bitbucket/changelog#CHANGE-3222

Tokens are not working, how to fix this?

2 answers

1 accepted

1 vote

Answer accepted

That 410 error means Bitbucket is rejecting your old app password during scheduled brownout.

On July 11, Bitbucket is running scheduled app-password brownouts. During these windows, Git-over-HTTPS requests authenticated with an app password return HTTP 410 and the CHANGE-3222 message.

Switch SourceTree to a User API Token with user, workspace, and repository scopes.

Update your account in SourceTree using your Atlassian email, then clear any old bitbucket.org entries from Windows Credential Manager or macOS Keychain and restart the app. If you skip clearing that credential cache, Git will just keep pushing the dead password in the background.

Cheers,

Arek 🤠

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

We have never used app passwords, and are getting this error using Access tokens, API tokens, and also getting "user 112 not known" errors using ssh auth during the brownout periods. There does not seem to be any form of git authentication that is working reliably any more.

Bitbucket is unusable, and we are on the verge of switching away to another provider due to this issue, as we are losing productivity because of it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

The user 112 not known message is not the normal Bitbucket SSH authentication response. Check whether an SSH configuration, proxy, wrapper, or URL rewrite is replacing git with another username.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Sorry, you are right, it seems to be a Docker container issue we are running into using ssh URLs from jenkins, the message is the same as: https://unix.stackexchange.com/questions/524268/running-git-or-ssh-client-in-docker-as-user-no-user-exists-for-uid

For now, API tokens seem to be working, and I did some experiments to show we are in fact inside a brownout period now, so whatever we have been experiencing over the past week seems to be fixed for now (fingers crossed).

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

Super :) Glad to hear that.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Reply

0 votes

Monosnap Image 2026-07-11 16.12.32.png

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

Suggest an answer

Log in or Sign up to answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

CLOUD

TAGS