Cannot create VCS Root using Bitbucket cloud - 2026.1.2

Additional Investigation

We have spent considerable time investigating this before raising the ticket and have been able to narrow the issue down.

Environment

• TeamCity Professional 2026.1.2
• Java 21
• Bitbucket Cloud
• Native Git 2.39.2
• OAuth client configured in Atlassian
• Bitbucket Cloud Connection configured in the TeamCity Root Project
• Refreshable Access Token created from the Root Project connection
• New VCS Roots created from the Bitbucket Cloud repository picker

Initial issue

During the initial Bitbucket Cloud OAuth setup we discovered that the callback URL presented by TeamCity did not match the callback URL actually used during the OAuth flow.

TeamCity instructed us to register:

https://teamcity.altius-exigo.com/oauth/bitbucket/

However, during authentication TeamCity redirected to:

https://teamcity.altius-exigo.com/oauth/bitbucket/accessToken.html

Registering the /accessToken.html endpoint resolved the OAuth callback issue and repository browsing began working correctly.

Current issue

The Bitbucket Cloud connection authenticates successfully.

We can:

• Authorise successfully with Atlassian.
• Browse repositories using the Bitbucket repository picker.
• See all repositories in the workspace.
• Create Refreshable Access Tokens.
• Create new Git VCS Roots using the Bitbucket Cloud connection.

However, every newly-created VCS Root fails on Test Connection with:

Failed to authorize using the specified token.

followed by:

The batch file cannot be found.
...
fatal: Authentication failed for
https://bitbucket.org/fortius-network/exigo.db.git/

Things we have verified

We have ruled out the following:

• Java 21 correctly installed and in use.
• HTTPS certificate issues (agents and server communicate correctly).
• Native Git installation (2.39.2).
• OAuth callback configuration.
• OAuth client recreation.
• Refreshable Access Token recreation.
• New Bitbucket Cloud connection.
• New VCS Auth Token.
• New VCS Root.
• Token created in the Root Project.
• Refreshable Access Token authentication selected.
• Repository URL manually entered and generated via repository picker.
• Username both with and without fortius-liam@ in the URL.
• Windows permissions on C:\TeamCity.
• Temporary credential batch files are successfully created.
• ProcMon confirms the temporary pass*.bat and cred*.bat files are opened successfully by cmd.exe and sh.exe.
• We do not see evidence that the files are being deleted or blocked before use.

Important observation

Our existing (legacy) Bitbucket VCS Roots continue to work correctly.

Only newly-created Bitbucket Cloud OAuth / Refreshable Access Token VCS Roots fail.

Because the existing VCS Roots still perform Git operations successfully, this does not appear to be a general TeamCity Git or temporary-file issue.

We suspect this may be a regression in the Bitbucket Cloud OAuth / Refreshable Access Token implementation in TeamCity 2026.1.2.

Hi,

Could you please help us with the following?

1. Please provide the full exception/stack trace from teamcity-vcs.log and teamcity-server.log around the time you click Test connection on the failing VCS root.

2. Please share the configuration of:

   • one existing Bitbucket Cloud VCS root that works, and
   • one newly created VCS root that fails.

   Screenshots or an XML export are both fine. We'd like to compare the repository URL, authentication method, connection settings, and any other differences.

3. Could you also confirm:
   • whether the issue occurs for every newly created Bitbucket Cloud OAuth VCS root or only for a specific repository.

Large files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.

Uploaded at 2026_07_23_NKJTE4bvbKXWmAokq9xts

The existing VCS roots that work are using the username / password method of connecting.

The ones that arent working are attempting to use the Oauth VCS Root.- The error occurs for every repo we try to set up using this configuration.

Note: We didnt create the new VCS's fully as ‘test connection’ didnt work - The timestamps for us testing connections will be around 1pm UTC+1 on the 22nd of July.

Thanks!

Hi,
Thank you for the additional information.
Unfortunately, I'm unable to access the files you mentioned( 2026_07_23_NKJTE4bvbKXWmAokq9xts) from my side.
Could you please re-upload the server logs and share the upload ID again?
• teamcity-vcs.log    
• teamcity-server.log 

uploaded new versions after making a new VSC connection and clicking ‘test’ a couple of times so the logs would be fresh

Upload id: 2026_07_24_2BNCHGFdux7Hc5tK9UVWmM (files: teamcity-vcs.log, teamcity-server.log)

Thanks for providing the logs.

After reviewing them, I found two separate issues.

1. Test Connection for the new OAuth VCS Root

From the logs, all three failed Test Connection attempts were performed against a VCS root that had not yet been saved:

instance id=-26
parent internal id=-1
parent id=dummy_jetbrains.git

At the same time, TeamCity reports that the OAuth token cannot be found in TeamCity storage, followed by the secondary error:

The batch file cannot be found.

Based on the logs alone, it's not yet clear whether these symptoms are directly related or whether they indicate a separate issue.

As a first step, could you please try the following?

1. Save the VCS root.
2. Open the saved VCS root again.
3. Run Test Connection once more.

Please let us know whether the test succeeds after the VCS root has been saved. This will help us determine whether the issue is limited to testing an unsaved VCS root or whether further investigation is needed.

2. Existing Bitbucket VCS Roots

The logs also show a separate issue affecting your existing Bitbucket VCS roots.

There are a lot of entries similar to:

App passwords are deprecated and must be replaced with API tokens.
...
The requested URL returned error: 410

for VCS roots using URLs such as:

https://forxx-xxx@bitbucket.org/...

This indicates that these VCS roots are still authenticating with Bitbucket App Passwords, which Bitbucket Cloud has now deprecated. As a result, Bitbucket returns HTTP 410 when TeamCity attempts to access those repositories.

If these VCS roots are still in use, they will need to be migrated to a supported authentication method, such as Bitbucket API Tokens or OAuth.

For Bitbucket API Token authentication, Bitbucket recommends using:

• Username: x-bitbucket-api-token-auth
• Password: your Bitbucket API token

Please let us know the outcome after testing the saved OAuth VCS root. If the issue persists, we'll continue investigating further.

I have now saved the new VCS root. However I didnt save it because it wasnt working. The same response still occurs.

On the old ones set up with the old style username / passwords. The 410 happens intermittently because of the bitbucket old credential brown outs.